Five years ago a data warehouse was a one stop shop for all of your data and analytics needs. The types and sources of data a business has access to has grown exponentially in this time though and businesses need to expand their data strategy beyond the data warehouse if they want to use their data for intelligent decision making, competitive advantage and business growth. In this blog we’re going to discuss the key ingredients you need for a holistic data strategy.
In a systems integration context RPA tools are enabling automated integration with legacy systems that wasn’t previously possible, easy or feasible. As with any technology, however, there are some scenarios where RPA is not a good fit (nothing is ever a silver bullet, is it?). In this blog I’m going to detail some key points you should consider before using RPA as another tool in the “integration” toolbox.
One of the biggest issues I see in the market is the notion of procuring the perfect platform. When talking to a new or prospective client for the first time I will often hear “We have this mess on Product A, Database B so we’re thinking of moving to Platform X”. In my experience there is no single platform, product or framework that solves all the Information Technology problems a business will encounter. Every business is different. Every challenge is different. Every context is different.
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.
Subscribe to receive more great articles just like this one.