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
Most Big Data projects fail. There are many reasons for this, usually around the business reason for the project, and data quality (along with a lack of skills). A key part of ‘Cloud Transformation’ is
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
Containers and Virtual Machines both have a role within the modern Cloud architecture. Both possess some advantages and disadvantages. The graphics below summarises the key differences: Main use case for Cloud Containerisation is application
Database design for high end applications Many applications today are data-intensive, not CPU intensive. Raw unlimited CPU power is rarely an architectural or application limiting phenomenon for most applications. Raw CPU power is rarely a
12 Factors and the Strangler Pattern Cloud native builds will mean that legacy applications, will need to be rebuilt to fit into cloud patterns. An example of a pattern to use to rebuild