Source Link 

https://www.linkedin.com/feed/update/urn:li:activity:7096815232123068416?utm_source=share&utm_medium=member_desktop

📱 𝗪𝗲𝗯/𝗠𝗼𝗯𝗶𝗹𝗲 𝗔𝗽𝗽: The front-end of the application where users engage directly. This can be a browser-based web application or a native mobile application. It communicates with the backend through the API gateway.

🚪 𝗔𝗣𝗜 𝗚𝗮𝘁𝗲𝘄𝗮𝘆: An entry point for the application's backend. This component typically manages request routing, authentication, rate limiting, and other cross-cutting concerns. Essentially, it functions as a reverse proxy, directing requests to the relevant services.

🔀 𝗜𝗻𝘁𝗲𝗴𝗿𝗮𝘁𝗶𝗼𝗻 𝗟𝗮𝘆𝗲𝗿: Here, you'll often find business logic, especially when various microservices and external services come into play. This layer orchestrates calls to different services, manages data transformations, and facilitates communication between components.

🛠 𝗠𝗶𝗰𝗿𝗼𝘀𝗲𝗿𝘃𝗶𝗰𝗲𝘀: These represent small, autonomous services that oversee specific chunks of business logic or domain functionality. Each microservice ideally has its standalone database for decoupling, scalability, and maintainability, allowing them to be developed, deployed, and scaled independently.

🗃 𝗗𝗮𝘁𝗮𝗯𝗮𝘀𝗲 (𝗗𝗕): This refers to persistent storage for application data. In line with the microservices paradigm, each microservice would optimally have its own database to maintain data integrity for its specific domain.

𝗢𝘁𝗵𝗲𝗿 𝗖𝗼𝗺𝗽𝗼𝗻𝗲𝗻𝘁𝘀:

In addition to the diagram's components, several other components might find use in a microservices architecture, such as:

🌐 𝗦𝗲𝗿𝘃𝗶𝗰𝗲 𝗠𝗲𝘀𝗵: A service mesh offers service discovery, load balancing, and fault tolerance features for microservices.

🖥 𝗖𝗲𝗻𝘁𝗿𝗮𝗹𝗶𝘇𝗲𝗱 𝗟𝗼𝗴𝗴𝗶𝗻𝗴 𝗮𝗻𝗱 𝗠𝗼𝗻𝗶𝘁𝗼𝗿𝗶𝗻𝗴: A centralized system for logging and monitoring to monitor application health and performance.

⚡ 𝗖𝗗𝗡 (𝗖𝗼𝗻𝘁𝗲𝗻𝘁 𝗗𝗲𝗹𝗶𝘃𝗲𝗿𝘆 𝗡𝗲𝘁𝘄𝗼𝗿𝗸): A CDN enhances application performance by caching static content at edge locations.

⚖️ 𝗟𝗼𝗮𝗱 𝗕𝗮𝗹𝗮𝗻𝗰𝗲𝗿𝘀: These help distribute incoming traffic across multiple servers, boosting performance and reliability.

💾 𝗖𝗮𝗰𝗵𝗶𝗻𝗴: Caching stores frequently accessed data in memory to elevate application performance.

Source Link

https://www.linkedin.com/posts/brijpandeyji_imagine-youre-in-a-library-the-books-activity-7098264772470525952-bjC-?utm_source=share&utm_medium=member_desktop

Imagine you're in a library. 📚

The books most frequently read are placed in an easily accessible shelf right next to the reading area.

Why?

To speed up access and improve the reading experience.

This is exactly what caching does in the realm of computing.

Think of cache as a high-speed storage mechanism that can be either a reserved section of main memory or an independent high-speed storage device.

It's a place to store a subset of data - typically, the most frequently used data - in a location where it can be accessed quickly.

Caching is used extensively across various facets of computer systems - in hardware (like CPU cache), operating systems, web browsers, and of course, backend development.

Today, we're diving into its role in the backend side of things, which is absolutely vital to understand for anyone working on or studying about system performance and efficiency.

Now, why is backend caching important?

When dealing with web applications, caching on the server-side can significantly enhance performance by reducing database load, cutting down latency, and improving request handling capacity.

It's like having a mini database that is faster and quickly accessible, storing data that is frequently needed. 🚀

No, we're going to focus on different backend caching strategies, such as Read Through, Write Through, Write Around, Write Back, and Cache Aside.

𝗥𝗲𝗮𝗱 𝗧𝗵𝗿𝗼𝘂𝗴𝗵:

1. The client requests data.
2. The cache intercepts the request.
3. If the data is in the cache (cache hit), it is returned to the client.
4. If the data is not in the cache (cache miss), the cache fetches the data from the database.
5. The cache stores a copy of the data and returns it to the client.
   
𝗪𝗿𝗶𝘁𝗲 𝗧𝗵𝗿𝗼𝘂𝗴𝗵:

1. The client writes data.
2. The write operation is directed at the cache.
3. The cache updates its data.
4. The cache then ensures that the data is also written to the database.
5. The cache then acknowledges the write operation to the client.
   
𝗪𝗿𝗶𝘁𝗲 𝗔𝗿𝗼𝘂𝗻𝗱:

1. The client writes data.
2. The write operation is directed only at the database, bypassing the cache.
3. The data does not immediately enter the cache.
   
𝗪𝗿𝗶𝘁𝗲 𝗕𝗮𝗰𝗸 (𝗼𝗿 𝗪𝗿𝗶𝘁𝗲 𝗕𝗲𝗵𝗶𝗻𝗱):

• The client writes data.
• The write operation is directed at the cache.
• The cache updates its data and immediately acknowledges the write operation to the client.
• The cache then asynchronously writes the data to the database.
  
𝗖𝗮𝗰𝗵𝗲 𝗔𝘀𝗶𝗱𝗲 (𝗼𝗿 𝗟𝗮𝘇𝘆 𝗟𝗼𝗮𝗱𝗶𝗻𝗴):

1. The client requests data.
2. If the data is in the cache (cache hit), it is returned to the client.
3. If the data is not in the cache (cache miss), the client fetches the data from the database.
4. The client then writes any data it reads into the cache.