Behind the firewall experiencies
Well, I just finished the work I have been involved during the last month. The task consisted mainly to assemble a RFP document to renew all of our modeling and automatic code generation toolset. Next Monday, we will introduce to some selected providers which are the project objectives and which are the requirements.
Advancing some details, I will tell you that in a first stage we will start designing and developing an infrastructure where all the development tools will rely on. We will also ask to design and develop a tool to model the business logic flow and to automatically generate the code that will execute on a IMS/PL/I/DB2 mainframe environment under a property framework (we call this framework “Application Services Integration”).
The architecture of this framework could be compared to a service oriented architecture (SOA), thought in this case services are coupled, mainly because performance (we have constant peaks of 1.500 tx/s and one requirement is that the response time must be lower than 1 second).
This RFP is our second attempt to renew our development toolset. First attempt, developed under something similar to the MDA paradigm (or should I say DSL as we didn’t use UML?) and based on Eclipse PDE framework plus a metamodel that relies on a central repository database, was a complete failure. I will explain the reasons (a forensic analysis) in another post, although it’s about performance and scalability in a geographically disperse environment.
Why I’m telling you this? Well, because I want to share with you similar experiences. Unfortunately, this kind of experiences are usually hidden “behind the firewall”, and, in my opinion, it’s positive to share these details with others as we can learn about success and failures (as my manager usually says to me, “you always must assume that the rest of the people are cleverer than you”).