Build, protect and deploy apps across any platform and mobile device
Leverage a complete UI toolbox for web, mobile and desktop development
Automate UI, load and performance testing for web, desktop and mobile
Rapidly develop, manage and deploy business apps, delivered as SaaS in the cloud
Automate decision processes with a no-code business rules engine
Build mobile apps for iOS, Android and Windows Phone
Deploy automated machine learning to accurately predict machine failures with technology optimized for Industrial IoT.
Optimize data integration with high-performance connectivity
Connect to any cloud or on-premise data source using a standard interface
Build engaging multi-channel web and digital experiences with intuitive web content management
Although I missed the first day of the The ServerSide Symposium as I was en route to Las Vegas from London, many of the talks have been interesting. I am currently listening to Ted Farrell from Oracle who is discussing Oracle's core J2EE interests that focus primarily on EJB 3.0 and Java Server Faces. JSF has many interesting correlations between style sheet manipulation and more course faces components employed in web application developments.
John Crupi's discussion on Sun Microsystems position on SOA was also of interest, although focused more on the wider integration challenges. The movement of SOA as 'Moving from monolithic, closed applications to shared, network-based layered services' is a very useful basis for a lot of the SOA chatter active today. The SOA definition is also worth a look: 'An integration architectural style for XML document-based exchanges using shared, loosely coupled network based software services.'
In many respects I agree with this; however in other respects it is one of many definitions of SOA depending on your perspective. His discussion as to where SOA is today was insightful, and certainly throws up the opportunity for XQuery to play it's role in evolution. The following is a snap shot of this slide:
Cruppi's view that we need fast success in SOA projects is important. Any approach to SOA has to be use a fine grained piece-wise approach.
Looking athe SOA big rules, it is interesting to list the core architectural rules that govern an inclusive SOA framework.
The JBI JSR looks very interesting, so I'll blog about this soon. Particularly interesting is how it binds SOAP, FTP, REST and abMS using a message router and then engages BPEL Routing, Transformations and Correlations to service Service Engines. This JSR is due to be published next week, so I'll discuss it then. More blogging from the ServerSide Symposium later today.
View all posts from Jonathan Bruce on the Progress blog. Connect with us about all things application development and deployment, data integration and digital business.
Copyright © 2017 Progress Software Corporation and/or its subsidiaries or affiliates.
All Rights Reserved.
Progress, Telerik, and certain product names used herein are trademarks or registered trademarks of Progress Software Corporation and/or one of its subsidiaries or affiliates in the U.S. and/or other countries. See Trademarks for appropriate markings.