Pallavi A.

Microservices Architecture

Microservices architecture is a paradigm shift in application development.

Instead of monolithic applications, complex systems are broken into smaller, independent services.

Let's delve into the key components that make this architecture tick -

1/ Clients
- The diverse users who interact with the application, be it via web browsers, mobile apps, or desktop software.

2/ Content Delivery Network (CDN)
- CDNs are a network of servers strategically distributed across the globe.
- They cache and deliver static assets (images, scripts, etc.) to users from the closest server, optimizing load times.

3/ Load Balancer
- A crucial traffic cop, it distributes incoming requests across multiple servers to prevent overload and ensure high availability and responsiveness.

4/ API Gateway
- The single entry point for all clients. It handles request routing, authentication, rate limiting, and other cross-cutting concerns, abstracting the complexity of the microservice ecosystem.

5/ Microservices
- The heart of the architecture. Each microservice is a self-contained unit responsible for a specific business capability.
- They communicate via lightweight protocols like REST or messaging.

6/ Message Broker
- Enables asynchronous communication between microservices.
- This loose coupling enhances flexibility and resilience, allowing services to evolve independently.

7/ Databases
- Microservices often have their own dedicated databases, adhering to the principle of data ownership and promoting loose coupling.
- This can lead to a polyglot persistence approach.

8/ Identity Provider
- Ensures secure access to microservices by handling authentication (verifying user identity) and authorization (determining user permissions).

9/ Service Registry and Discovery
- A dynamic directory where microservices register themselves and discover other services.
- This facilitates seamless communication in a constantly evolving environment.

10/ Service Coordination (e.g., Zookeeper)
- Tools like Zookeeper help manage the coordination and synchronization of distributed services, ensuring smooth operation and data consistency.

------

Connect/Follow - Pallavi Ghanshani


Image Credits - DesignGurus

#microservices

Let's talk about - API Protocols

1. REST (Representational State Transfer)
- An architectural style for designing networked applications.
- It emphasizes stateless communication, the use of standard HTTP methods (GET, POST, PUT, DELETE), and resources identified by URLs.

2. GraphQL
- A query language for APIs that allows clients to request exactly the data they need, nothing more and nothing less.
- This efficiency is a major advantage over REST, where endpoints often return fixed data structures.

3. SOAP (Simple Object Access Protocol)
- A protocol for exchanging structured information in the form of XML messages over a network.

4. gRPC (Google Remote Procedure Call)
- A high-performance, open-source framework for remote procedure calls (RPCs).
- It uses Protocol Buffers (a compact binary format) for data serialization.

5. Webhooks
- A mechanism for real-time communication between applications.
- A webhook is essentially an HTTP callback triggered by a specific event in one system, which sends a notification to another system.

6. WebSockets
- A protocol providing full-duplex communication channels over a single TCP connection.
- WebSockets enable real-time data exchange between a client and a server.

7. MQTT (Message Queuing Telemetry Transport)
- A lightweight publish-subscribe messaging protocol designed for low-bandwidth, high-latency, or unreliable networks.
- It is commonly used in IoT (Internet of Things) applications.

8. AMQP (Advanced Message Queuing Protocol)
- An open standard protocol for message-oriented middleware.
- AMQP provides features like reliable message delivery, routing, and queuing, making it suitable for enterprise integration scenarios.

9. EDA (Event-Driven Architecture)
- A software architecture pattern where applications react to events (e.g., user actions, sensor readings).
- EDA promotes loose coupling and scalability.

10. EDI (Electronic Data Interchange)
- A set of standards for exchanging business documents (e.g., purchase orders, invoices) electronically between organizations.
- EDI is widely used in supply chain management and logistics.

11. SSE (Server-Sent Events)
- A server-push technology that allows a server to send updates to a client over an HTTP connection in a unidirectional manner.

---

Tagging some amazing creators, who work hard to share great content.

[System Design & Software Development]
- Mayank Ahuja
- Raul Junco
- Saurabh Dashora
- Nikki Siapno
- Ashish Pratap Singh
- Brij kishore Pandey
- Neo Kim
- Arpit Bhayani
- Rocky Bhatia
- Arslan Ahmad

[𝐂𝐨𝐝𝐢𝐧𝐠 & 𝐈𝐧𝐭𝐞𝐫𝐯𝐢𝐞𝐰 𝐏𝐫𝐞𝐩]
Raj Vikramaditya
Riti Kumari
Abhishek Saini

[𝐁𝐞𝐜𝐨𝐦𝐞 𝐚 𝐁𝐞𝐭𝐭𝐞𝐫 𝐃𝐞𝐯𝐞𝐥𝐨𝐩𝐞𝐫]
John Crickett
Jordan Cutler
Adrian Stanek
Eric Roby

[𝐂𝐚𝐫𝐞𝐞𝐫 𝐆𝐫𝐨𝐰𝐭𝐡]
Hina Arora
Omar Halabieh
Gregor Ojstersek
Sarah
Gina

[𝐂# 𝐄𝐱𝐩𝐞𝐫𝐭𝐬]
Jalal Alzebda
Dave Callan
Pavle Davitković
Milan Jovanović
Nikola Knežević

Image Credits -> Ivan Novikov

#api #technology