Build, protect and deploy apps across any platform and mobile device
Deliver Awesome UI with the most complete toolboxes for .NET, Web and Mobile 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
A complete cloud platform for an app or your entire digital business
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-premises data source using a standard interface
Build engaging multi-channel web and digital experiences with intuitive web content management
It may seem odd to talk about contracts and SOA in the same sentence, but without them experienced enterprise architects and integration developers understand the negative consequences that will ripple through the business.
A service-oriented architecture (SOA) requires establishing contracts between its participants. The first or most basic SOA contract provision concerns what formats and protocols are used. When two service participants, a provider and a consumer, establish a contract, it must start out with some protocol and format artifact (or transport and data-level semantic), such as an XSD and the associated WSDL describing the interface between that consumer and producer. These decisions establish the beginnings of interoperability, specifically how the first-level pin-outs get wired together.
Beyond this basic level, IT professionals tend to think about contracts in two broad areas: the service-level agreement (SLA) and security. For IT, an SLA usually specifies scale, response time, and availability: for example, handling 10,000 requests per second with a response time of less than 500 milliseconds, and availability to four 9s, or 99.99 percent uptime. From a security standpoint, a contract covers four or five areas.
In installment #7 of the Enterprise Integration Whiteboard Series, Hub Vandervoort delves into the sixth point of mediation - Quality of Service (QoS) and Quality of Privacy/Protection. But rather than providing a comprehensive account of the idea of QoS and QoP, the video podcast and technical paper offer a high-level overview of some capabilities within Sonic ESB by itself and in association with Actional, which is largely built into the ESB infrastructure, and how those come together to create the foundation of QoSQoP—trust and commitment —required for effective contracts.
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 © 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.