System integration involves integrating existing (often disparate) subsystems and then creating unique and new value for the customer or end user. This blog lays out various steps to take and things to consider when planning an integration solution.
This rather long, but extremely well-researched article by Kai Wähner is a follow-up and update to his previous article "Microservices and whether that spells the death of the Enterprise Service Bus and other middleware." In this piece, he discusses how relevant microservices, containers, and a cloud-native architecture is for middleware. Take the time and read this... it's well worth it!
In this post, author Dmitriy Setrakyan shows you how to load data from a MySQL database into an Ignite distributed cache. Read on and see how it's done.
There are a lot of parallels between the Internet Of Things and Microservices. One of the big battles in the design is the granularity of each service and the impact that can have on interdependency and network costs.
With a modern IIoT and cloud platform underlying the next generation of applications and analytics, the oil and gas industry can move beyond just doing the same thing faster or cheaper and adopt new levels of productivity.
Almost all applications that perform anything useful for a given business need to be integrated with one or more applications. With microservices-based architecture, where a number of services are broken down based on the services or functionality offered, the number of integration points or touch points increases massively.
CORE
