# System Design, Backend

Published articles for System Design, Backend.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## Five Caching Strategies Every Backend Dev Should Know

DevFeed: [Five Caching Strategies Every Backend Dev Should Know](<https://devfeed.tech/articles/five-caching-strategies-every-backend-dev-should-know-33337.md>)

Original publisher: [Read original article](<https://blog.ratnesh-maurya.com/blog/Distributed-Caching-Strategies-Architecture>)

Author: ratneshmaurya2311@gmail.com (Ratnesh Maurya)

Published: 2026-02-24T00:00:00Z

Content type: tutorial

Language: en

Sources: [Ratn Labs](<https://devfeed.tech/sources/ratn-labs.md>)

Topics: [Caching](<https://devfeed.tech/topics/caching.md>), [Back end](<https://devfeed.tech/topics/backend.md>), [Development](<https://devfeed.tech/topics/development.md>)

Tags: [backend](<https://devfeed.tech/tags/backend.md>), [beginner](<https://devfeed.tech/tags/beginner.md>), [caching](<https://devfeed.tech/tags/caching.md>), [caching-strategies](<https://devfeed.tech/tags/caching-strategies.md>), [guide](<https://devfeed.tech/tags/guide.md>), [system-design](<https://devfeed.tech/tags/system-design.md>), [system-design-backend](<https://devfeed.tech/tags/system-design-backend.md>)

### AI overview

A beginner-friendly guide to five distributed caching strategies: Cache-Aside, Read-Through, Write-Through, Write-Back, and Write-Around, including when to use each.

### Source excerpt

A beginner-friendly guide to Cache-Aside, Read-Through, Write-Through, Write-Back, and Write-Around, with when to use each.

## Architectural Design for a Ride App such as OLA, UBER, RAPIDO

DevFeed: [Architectural Design for a Ride App such as OLA, UBER, RAPIDO](<https://devfeed.tech/articles/architectural-design-for-a-ride-app-such-as-ola-uber-rapido-33335.md>)

Original publisher: [Read original article](<https://blog.ratnesh-maurya.com/blog/Architectural-Design-for-a-Ride-App-such-as-OLA-UBER-RAPIDO>)

Author: ratneshmaurya2311@gmail.com (Ratnesh Maurya)

Published: 2024-07-30T00:00:00Z

Content type: article

Language: en

Sources: [Ratn Labs](<https://devfeed.tech/sources/ratn-labs.md>)

Topics: [microservices architecture](<https://devfeed.tech/topics/microservices-architecture.md>), [Architecture & Design](<https://devfeed.tech/topics/architecture-design.md>), [gRPC](<https://devfeed.tech/topics/grpc.md>), [App](<https://devfeed.tech/topics/app.md>)

Tags: [architecture](<https://devfeed.tech/tags/architecture.md>), [backend](<https://devfeed.tech/tags/backend.md>), [microservices](<https://devfeed.tech/tags/microservices.md>), [microservices-architecture](<https://devfeed.tech/tags/microservices-architecture.md>), [queues](<https://devfeed.tech/tags/queues.md>), [rest](<https://devfeed.tech/tags/rest.md>), [software-architecture](<https://devfeed.tech/tags/software-architecture.md>), [system-design](<https://devfeed.tech/tags/system-design.md>), [system-design-backend](<https://devfeed.tech/tags/system-design-backend.md>), [tracking](<https://devfeed.tech/tags/tracking.md>), [vs](<https://devfeed.tech/tags/vs.md>)

### AI overview

An overview of architectural design for a ride-sharing app, covering microservice boundaries, REST, gRPC, message queues, geolocation tracking, and the trade-offs between starting with a monolith and adopting microservices.

### Source excerpt

Microservices architecture for ride-sharing: service boundaries, REST vs gRPC vs message queues, geo-location tracking, and trade-offs between monolith-first and microservices.