Kubernetes and Storage
Kubernetes is a necessary infrastructure to manage decomposed applications focused on providing discrete functionality, in a lightweight container. This was called the SOA or service-oriented-architecture, now renamed ‘micro-services’ but essentially the same concept and
Kubernetes and the Micro-services ‘way of thinking’
Kubernetes (K8s) use-cases are centred on scaling. Architectures which are Containerised, with hundreds, or even thousands of Containers require immutable scalability. The management and orchestration complexity of such systems is best fulfilled by K8s and
Microservices and Refactoring Code
Source link here. Code refactoring enhances microservices One of the more important coding disciplines in object-oriented programming and SOA is code refactoring. The techniques allow developers to restructure code as they better understand usage considerations,
API LifeCycle Management, a summary
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
API Gateway and a Service Mesh: Summary of Use Cases
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.
Service Mesh as an extension to API Gateway Patterns
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 Gateway vs Service Meshing
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
Architectural Views for building Cloud Systems
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