Principles for Designing Scalable Microservices
Key principles for designing scalable microservices, including Single Responsibility and Independent Deployability, to ensure performance and maintainability.
Key principles for designing scalable microservices, including Single Responsibility and Independent Deployability, to ensure performance and maintainability.
Compares monolithic, modular monolith, and microservices architectures, detailing their characteristics, advantages, and challenges.
A structured learning plan for C#/.NET developers to master microservices architecture, covering fundamentals, implementation, and Azure deployment.
A guide to implementing OpenTelemetry for distributed tracing in ASP.NET Core applications to improve observability and performance.
A technical analysis of the Outbox Pattern for microservices, examining its implementation, criticisms, and modern alternatives in 2024.
A technical analysis of the Outbox Pattern for microservices, its implementation, criticisms, and modern alternatives in 2024.
A guide to building event-driven applications using Azure Event Grid and C#, covering architecture benefits and implementation.
Explains the Saga pattern for managing data consistency in distributed microservices transactions, including implementation on AWS.
An introduction to NATS, an open-source technology for connecting applications and microservices over a network.
The latest episode of Building SaaS covers post-launch improvements and user experience polishing for the JourneyInbox application.
First part of a series on building a vehicle tracking app using Azure services, covering the system architecture and components.
Explains how a microservices architecture is essential for successful blue/green deployments and common pitfalls when services are not independent.
A guide on integrating an Angular front-end application into a .NET Aspire orchestration setup for cloud-native development.
A technical comparison of RabbitMQ and Apache Kafka for messaging in microservices, covering their architectures, patterns, and use cases.
Discusses why blindly copying technical solutions or processes from one team to another often fails due to unique team and company contexts.
A case study on implementing a custom microservice (Chronos) to measure end-to-end latency in a microservice architecture.
A developer reflects on leaving Rencore after seven years, highlighting work on architecting a SaaS platform, cloud migration, and compliance.
A guide to using Project Tye to simplify local development by running multiple .NET APIs and services with a single command.
Using OpenTelemetry to identify and manage database dependencies in microservices architectures.
A developer shares a list of their recent tech conference talks on topics like Kubernetes security, WebAssembly, and Docker.