With the arrival of microservices, the lines between systems integration and applications are becoming increasingly blurred. Previously, a traditional enterprise application as a single big monolith would perhaps make some network calls to an integration layer to connect with other external single monolithic applications. These days a microservices approach advocates having intelligent APIs and building microservices just be big enough “to fit in your head”. This leads to many more integration points in a traditional business application between microservices, certainly more than what we encountered in a traditional enterprise systems integration.
Posted on 28 July, 2017 by Riaan Ingram & Siddharth Dubey
Result Caching is a very popular Oracle Service Bus (OSB) feature which is often used for performance improvements. It allows local caching of response payloads from external services. Too often these cached payloads become outdated and need to be cleaned or refreshed, but programmatically controlling the selective ‘cleaning’ or refreshing of these response payload caches remains a challenge.
One of the recurring challenges we see in software development is getting stakeholders, developers and project members in different areas of the business to agree the business objectives and priorities for an application. In this blog, I am going to share some of the common strategies we adopt to manage alignment amongst stakeholders to ensure application success.
The rise of APIs provides another avenue for sending and receiving large documents. This blog will discuss when it’s appropriate to use large documents with APIs and provide some recommendations to ensure success.
Subscribe to receive more great articles just like this one.