John LaLone is currently SOA Technical Executive on the Worldwide Technical Sales team with specific responsibility for SOA Strategy and Roadmap. Within this role he has specific responsibility for Business Oriented Applications and SOA Governance. He has held a wide variety of technical and management positions in Emerging Technologies, Services, Sales, and Marketing; primarily focused on complex systems integration solutions with over 8 years experience with business process management. John's previous role, prior to the WW Technical Sales team, was with SOA product management team as SOA Platform Manager with responsibility for the SOA Foundation Portfolio.
Service Oriented Applications – Yesterday’s Applications are Today’s Middleware
Raising the water line for the upper middleware layer
From the early days of our industry, the middleware layer (or if you prefer – the infrastructure layer), has grown as technology provided for more function to be moved out of the core function of applications into a centralized infrastructure or middleware layer. This has been accompanied by a higher level of abstraction within the programming model which has also raised the level of functionality and productivity for the application layer. This allowed for the middleware layer to expand, or extend, while still providing for growth of the application layer.
Many customers today are seeking a platform which will provide for Business Services which can be delivered dynamically at the time of execution (runtime). The line between industry based components (services common to many business processes) and business applications is often vague. While in practice, the decision of which services are components (high reuse, low change) versus business processes with dynamic composite services (low reuse, high flexibility/change) is critical to success.
There will be many SOA sessions at IMPACT 2007 which will use the terminology of Business Services, Component Business Services, Composite Business Services, Service Oriented Applications, and other similar terms along with new programming models with associated runtimes for these services. Are we really at another stage in the industry where the ‘water line’ between middleware and applications is being raised significantly? Is there really a new programming model, a higher level of abstraction for composition of dynamic business services?