Backend Design
[Part 2] System design 101
System Design is the process of defining the System Architecture and how it will be implemented. This article goes into the nitty gritty details.
Backend Design
System Design is the process of defining the System Architecture and how it will be implemented. This article goes into the nitty gritty details.
Backend Design
System design and software design are often used interchangeably. This blog post shares how we define them and use them in the context of debugging distributed systems.
Distributed Systems
Sixth instalment in the "Six modern software architecture styles" blog post series. In short: Liberté, Égalité, Fraternité for all the peers!
Distributed Systems
Fifth instalment in the "Six modern software architecture styles" blog post series. In short: Bring computation and data storage closer to the end user.
Distributed Systems
Fourth instalment in the "Six modern software architecture styles" blog post series. In short: Build and run services without having to manage the underlying infrastructure.
Distributed Systems
Third instalment in the "Six modern software architecture styles" blog post series. In short: Your components or services communicate through events.
Distributed Systems
Second instalment in the "Six modern software architecture styles" blog post series. In short: partition your problem into multiple, independent chunks that are scaled independently.
Distributed Systems
Leveraging tried-and-tested solutions saves time, ensures reliability, and helps avoid common pitfalls. We look at six common architectural styles used in distributed systems and talk about how to choose the best one for your use case.
Backend Design
We typically associate 'design' with visual aesthetics, but it's more than that. Backend engineers are masters of system design, meticulously crafting the architecture, dependencies, and data structures that influence user experiences. This post explores the hidden artistry in their work.
System Architecture
Traditional system documentation methods fail to keep up with modern software complexity. Auto-documentation transforms engineering teams by saving time, improving accuracy, and enabling seamless collaboration.
Thought Leadership
Recently, there has been an outpouring of commentary from CEOs in tech on the need to return to the office. We did a deep dive into how beneficial (or not) this would be for the productivity of developer teams.
AI
Depending on your specific use case, your approach to LLMs may vary. Here’s a breakdown of the options and best practices.