Kubernetes Introduction
Monolithic Architecture
Micro Services Architecture
Monolithic Vs. Micro Services Architecture
Containers Overview
Container Orchestration Engines
Managed Kubernetes Services
Kubernetes Architecture
Kubernetes Cluster Setup
POD Management
Replication Controller
ReplicaSet Controller
Deployment Controller
Kubernetes Services
Configure aws-provider on kubernetes cluster
Load Balancer service on Kubernetes
Learn Kubernetes | K8s Tutorial for Beginners
DevOps Tech Hub116 Followers
Micro Services Architecture
Consider an example of online retail portal, customer can browse the services through browser and can add products to the cart, order a product, authorize payments, and track shipments. These are different components built based on Micro services model. Each component as a separate loosely coupled service depending on the business requirement. Network established to have communication between all these service components but works as independent code base.
Micro services Architecture deploy these components into separate unit of application code in separate compute platform.
Below listed each service component has its own code deployment:
- Catalog – Listing Products inventory
- Order – Takes customer order and process it
- Payment – Manage Payments through payment gateway
- Shipment – Manage Shipping the product
- Tracking – Showing the Product Shipment status
Below Architecture describes the “Microservices Architecture” view of deploying all service components in separate compute platform with separate artifact(.war)
Previous Next