Microservices All In One

Platform
https://github.com/panaverse/learn-generative-ai/tree/main/05_microservices_all_in_one
_platform
What is Microservice?
“A method to build software as a collection of small, independent services, each
serving a specific function.”

Key Features of Microservice can be

Independently Deployable Loosely Coupled Focused Functionality

Updates don't affect others. Communicate via APIs, easing Enhances modularity and
updates. reusability.
Benefits and Challenges
Benefits Challenges

Agility Quick
Complexity
More complex than traditional
to deploy new features.
monolithic apps.

Scalability Operational Overhead

Increased monitoring and
Services scale independently.
troubleshooting.

Maintainability API Management

Needs efficient communication
Easier to update and manage.
design.
 Team Ownership in Microservices
While a single developer can start a microservice, a cross-functional team's collective
expertise ensures its sustainable growth and resilience.

Why Team?
Diverse Skills Efficiency and Scalability
01. Combines expertise for superior
problem-solving.
03. Facilitates parallel work and faster
development, accommodating service
evolution.

02. 04.
Quality and Maintainability Reduced Risk
Encourages collaborative code reviews and Ensures continuity and minimizes
knowledge sharing. disruption if a member leaves.
Microservices: Types and Data Persistence
Microservices can be categorized by their accessibility to users and systems, and they
utilize various data persistence methods to manage and store information effectively.

Microservice Categories

Public Microservice Internal Microservice Hybrid Microservice

Open to external interactions. Restricted to internal system Combines public and internal
use. functionalities.
 Microservice Examples

Product Search Order Processing service User Management

service on an e-commerce within an e-commerce service with public login and
platform. platform. internal account management.

Microservice Data Persistence

Cache File Storage Database

Provides temporary storage for quickManages unstructured data like Stores structured data; can be
access to frequently used data. images and documents. relational (SQL) or NoSQL.
What is Microservice Application?
“A software application structured as a collection of small, autonomous services, each
fulfilling a specific role within the overall project.”

Consider the example of a large restaurant

Billing MS1 Kitchen MS2 Cleaning MS1

 What is monolith?
“A monolithic application is developed as a single, unified codebase, integrating all
functionalities, from user interface to data access, into one tightly coupled package.”

Key Features of Monolith can be

Unified Codebase Single Stack Tightly Coupled Single Deployment Unit

Single codebase for entire application Interconnected components Built, deployed, and scaled as
development and maintenance with require joint deployment. one entity.
one tech stack.
Benefits and Challenges
Benefits Challenges
Scalability
Simplicity in Development & Difficult to scale specific features;
Deployment often requires scaling the entire app.
Initially easier to manage, suitable
for smaller projects.
Complexity & Maintenance
Large codebases become unwieldy,
Performance complicating updates and fixes.
Effective for stable applications
with limited growth Reliability Bugs
expectations. can affect the entire
application's availability.
 What wrong with monolith?
While monoliths can be effective for certain project sizes and use cases due to their
simplicity and initial performance advantages, they face significant challenges in
scalability, maintenance, and agility as they grow, often making microservices a preferred
approach for larger, more dynamic applications.

Scalability Complexity & Maintenance

Difficult to scale specific features; Large codebases become unwieldy,
often requires scaling the entire app. complicating updates and fixes.

Reliability Bugs
can affect the entire
application's availability.
 Choosing Between Monoliths and Microservices
When to Choose a Monolith

Scope Development Simplicity

Best for smaller, well-defined projects Ideal when development and deployment
with limited growth expectations. simplicity are prioritized over scalability.

When to Opt for Microservices

Agility Resilience
Supports rapid, independent deployment Faults in one service don’t affect the entire
of features, facilitating faster iteration. application, improving overall stability.
Microservices: Avoiding Cloud-Vendor Lock-in
Our vision to build microservices on an all-in-one platform that minimizes cloud-vendor
lock-in is achievable through a strategic combination of technologies, each playing a
unique role in the ecosystem.

Technologies Breakdown

Docker Kubernetes
Facilitates consistency and portability across Offers a cloud-agnostic orchestration layer for
environments by containerizing applications, containers, enabling applications to run on any
making it easier to move workloads across infrastructure, from public clouds to on-premises
different clouds without lock-in. data centers, aiding in avoiding vendor lock-in.
Microservices: Avoiding Cloud-Vendor Lock-in

Serverless Containers Terraform

While they provide operational convenience, As an infrastructure as code tool that supports
they often tie you to a specific cloud. multiple cloud providers, Terraform allows you to
However, adopting Kubernetes can help define your infrastructure in a way that's not tied
mitigate this by allowing you to run to a single cloud, facilitating easier migration and
containers in a serverless fashion using management across clouds.
open-source projects like KNative, offering
more flexibility.
 Microservices: Avoiding Cloud-Vendor Lock-in

FastAPI PostgreSQL
Being a framework for building APIs with Python, As an open-source relational database, PostgreSQL can
FastAPI is independent of the cloud platform, run in any environment, cloud or on-premises,
ensuring that your application logic remains avoiding database lock-in while offering the benefits
portable and cloud-agnostic. of a robust, enterprise-grade database system.

GitHub Actions Kafka

Provides CI/CD capabilities that are not Kafka's open-source nature allows it to run on any
inherently tied to any cloud service, allowing infrastructure, supporting event-driven architectures
you to deploy applications across different without locking you into a specific cloud provider's
environments and cloud providers. messaging service.
Is Microservice a passing FAD?
Given the substantial benefits and the alignment with current technological and business
trends, microservices architecture is likely to remain a significant element of software
development for the foreseeable future.

While trends in technology do evolve, the fundamental drivers behind the adoption of
microservices—such as the need for agility, scalability, and resilience in application
development—are likely to persist. This suggests that microservices are not merely a
passing trend but a response to the long-term evolution of software development
practices.
Domain Driven Design
Domain-Driven Design (DDD) is a software development approach focused on aligning
software models with business domains. It's particularly effective in microservices
architecture due to its emphasis on clear boundaries for domain contexts, perfectly
complementing the principles of microservices.

Key Concepts and Their Application in Microservices

Bounded Contexts Single Responsibility Principle (SRP)

01. 02.
Defines
clear boundaries within which a domain Each microservice should have a singular
model applies, ensuring microservices focus, encapsulating all necessary logic
are autonomous and self-contained, and data for its function, leading to small,
embodying the microservice principle of task-specific services that are easy to
independence. manage.
Domain Driven Design

Key Concepts and Their Application in Microservices

Loose Coupling High Cohesion

03. Microservices communicate through
well-defined APIs, minimizing
04. Services focus on providing a specific
piece of functionality, making them easier
dependencies and allowing independent to maintain and evolve since all
evolution, critical for a resilient and components are related to their specific
manageable architecture. responsibility.
 Best Practices
Use separate data storage Separate build for each
01. Service A Service B 03. microservice
Service A

Service B

02. 04.
Keep code at a similar level of Assign each microservice with a
maturity single responsibility

Service B Service A

Level 2 Level 3
 Best Practices
Deploy into containers Adopt domain-driven design
05. Service A
07.
Service B

06. 08.
Design stateless services Design micro frontend
Payment Frontend
Request
Service
API Gateway
Response Payment Service
 Best Practices
Orchestrating microservices
09.
API Node 1

API Node 2

API Node 3
Kubernetes
Master