Create and deliver personalized experiences across digital properties at scale
Build engaging websites with intuitive web content management
Leverage a complete UI toolbox for web, mobile and desktop development
Build, protect and deploy apps across any platform and mobile device
Build mobile apps for iOS, Android and Windows Phone
Rapidly develop, manage and deploy business apps, delivered as SaaS in the cloud
Automate UI, load and performance testing for web, desktop and mobile
Host, deploy and scale Node.js, Java and .NET Core apps on premise or in the cloud
Optimize data integration with high-performance connectivity
Automate decision processes with a no-code business rules engine
Transform your businesses in order to survive in a completely digitized and connected world driven by software innovation.
Globally scale websites with innovative content management and infrastructure approaches
Content-focused web and mobile solution for empowering marketers
Faster, tailored mobile experiences for any device and data source
UX and app modernization to powerfully navigate today's digital landscape
Fuel agility with ever-ready applications, built in the cloud
When discussing an ESB, many people keep it simple, sticking to the generalities of SOA and sharing services to build composite business applications. Certainly, these are incredibly important benefits of an ESB but what do these dicussions really mean at the architecture level?
Another word for integration when it comes to ESBs is mediation. After all, that is truly what an ESB does - mediates the differences between application components (services) that were not intended to work together. So then, in context of mediation, how should an ESB be examined? Here at Progress, we view there to be seven points of mediation that serve as a set of key principles that apply to any integration infrastructure. They are critical because adherence to all seven is necessary to achieve the ultimate goals of SOA: reuse and agility.
Any one point that is not mediated becomes a point of brittleness. Put another way, interoperability needs to be tested along seven key points, which, briefly, are:
7 POINTS OF MEDIATIONTransport/ProtocolLocation/DestinationSemantic/FormatSequencingError RecoveryQuality of Service/Quality of ProtectionInteraction Model
To help examine these points in-depth Progress has created a series of technical briefs (white papers). These papers use the 'Seven Points of Mediation' as a way of describing how an ESB is, in fact, a comprehensive infrastructure onto which services can delegate these points. The overriding idea is that if a service delegates each and every point of mediation, it becomes more reusable in more contexts. These papers explain how Sonic ESB enables a service to free itself of these considerations, ultimately, so that it can provide the agility that SOA promises.
Be sure to watch the Transport, Location, and Semantics podcast and download the technical brief to learn more about the Seven Points of Mediation and the importance of each in relation to supporting a truly agile and responsive business application infrastructure.
Check out all of the Enterprise Integration Whiteboard Series white papers and videos here!
View all posts from Jonathan Daly on the Progress blog. Connect with us about all things application development and deployment, data integration and digital business.
Copyright © 2016, 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 or appropriate markings.