- Scaling with common sense #2: Being future ready.
- The cost of Hash Tables | The Backend Engineering Show
- What Software Architecture Should Look Like • Dave Farley • GOTO 2022
- Concurrency vs. Parallelism — A brief view
- Designing Tinder
- Designing Microservices the right way
- Microservice Architecture @Uber
- Clean Software Architecture
- Software Architecture Chronicles
- Domain-Driven Design with Onion Architecture
- Exploring the Hexagonal Architecture
- E-Commerce/food delivery app (Zomato/Swiggy/1mg)
- The Best Way to Think about Resilience Is Not to
- DDD, Hexagonal, Onion, Clean, CQRS, … How I put it all together
- DDD + Golang
- Quick & Brief Overview of the basics
- Backend Development Topic
- Load Balancing
- Designing a URL Shortening service like TinyURL
- When is a API not RESTFUL?
- Go Use Cases : With scalability in Mind
- On Engineering Dependibility
- More on System Design Basics
- API Gateway Pattern
- 8 steps to build a scalable and distributed system design for web applications
- Building robust distributed systems
- Architecting Backend For A Social Product
- http://highscalability.com/plentyoffish-architecture
- Trouble with Timestamps
- All Things Clock, Time and Order in Distributed Systems: Logical Clock vs Google True Time
- CD/CI for ML Models at Uber
- Redis as a Cache : But Why?
- 7 Microservices Best Practices for Developers
- Pitfalls and Patterns in Microservice Dependency Management
- Language Choice Matters : Why We Switched from Python to Go
- Pieces of a Scalable iOS App Architecture
- Robustness in Complex Systems
- Out of the tar pit
- Create Distributed, Scalable, Durable, and Highly Available Software— With Cadence
- Proxy vs Reverse Proxy (Real-world Examples)
These are also necessary since they give a fair idea as to organize code that is used to build and maintain components. I have covered this in great length in other links and repos of mine.
- Best Book Ever : GoF
- 4 Design Patterns You Should Know for Web Development
- Traversy Media -- 5 Design Patterns Every Engineer Should Know
- Introduction to Creational Design
- API Design-First Using the "Align-Define-Design-Refine" Process
- Adopting an API Design-First Approach
- Components, Patterns and Sh*t That’s Hard to Deal with