API and REST standards allowed an easier exchange of data and system connectivity. This has propelled the rise of containers, and Kubernetes, in which applications are broken down into smaller services. REST APIs are one
There is a connectivity overlap within level 7 between the API Gateway and a Service Mesh. Service Mesh’s, which are decentralized proxies running against each container, are used to manage network and routing between services.
Previous Blog on API Gateways (and APIs). A service mesh is a follow-on pattern built around API Gateway services. The focus of a service mesh is service connectivity between two or more services. Every time
API Gateways are often used to decouple consumers and producers of information. API Service Meshing can be used to decouple network management within, and between systems which rely on API integration to move and use
From the Open Group Business Architecture views, which address the concerns of the users of the system, and describe the flows of business information between people and business processes Data Architecture views, which address the
Virtual Machines and Monoliths can be valid. It is untrue that every application must be decomposed into microservices, and containers. Decomposed microservices architectures are difficult to build and operate, leading to higher costs. Not all
Monolithic applications may need to be decomposed in service-oriented components, to run and scale in lightweight containers. Similarly, monolithic Data architectures may need to be rebuilt into service-oriented Data flows and processes. This can transform
Most firms have issues with understanding their IT assets across environments. Many have more than 1 database of asset and configuration information; quite a few customise the configuration management database and make it difficult to
‘Transformation’ is a buzzword. You need to understand what it means, and properly define and parameterise the concept of ‘Transformation’.
