Weekend Reading #68
Weekly tech digest: DDD bounded contexts, Netflix Live Origin streaming infrastructure, Uber’s shift to cloud-native observability, and Lyft’s evolving feature store architecture
You're viewing blog posts that cotains Event-Driven Architecture tag
See all postsWeekly tech digest: DDD bounded contexts, Netflix Live Origin streaming infrastructure, Uber’s shift to cloud-native observability, and Lyft’s evolving feature store architecture
In this article, we explore microservices and distributed systems interview questions and answers, and what every .NET engineer should know, from service boundaries and BFF to sagas, events, service discovery, and communication patterns.
In this article, we explain what distributed deadlocks are, how they differ from blocking and slowness, the main types of distributed deadlocks, and practical strategies to prevent them in real systems.
This chapter explores NoSQL Databases questions that .NET engineers should be able to answer in an interview.
Walk through consistency models in distributed systems: Strong, bounded staleness, session, causal, and eventual consistency, explain how they work with examples, and help you understand when each model makes sense.
This chapter explores SQL Database questions that .NET engineers should be able to answer in an interview.
This week: skip-level meeting insights, Uber’s standardized mobile analytics, event-driven architecture best practices, and double-booking solutions at scale.
Master ASP.NET Core for interviews! Explore middleware, routing, DI, caching, & security with expert Q&A for junior to senior .NET devs.
Weekend Reading: A weekly roundup of interesting Software Architecture and Programming articles from tech companies. Find fresh ideas and insights every weekend.
This chapter explores design patterns, anti-patterns, and principles that are usually used across development on .NET.
This chapter explores advanced asynchronous and parallel programming in .NET, including Tasks, Thread Pools, channels, race conditions, context switches, and best practices.
AbstractLess: Approach to avoid complexity in your system architecture