Agent memory helps GitHub Copilot remember context across sessions. This post explains how it works and which memory tools you can use with Copilot and similar MCP clients.
Learn how to use Wolverine with RabbitMQ or Kafka in a two-microservice e-commerce sample and switch transports with configuration while keeping transactional outbox, durable inbox, and internal durable processing.
Set up a full observability stack for .NET microservices using OpenTelemetry instrumentation, OpenTelemetry Collector data pipeline, and Grafana with Prometheus, Tempo, and Loki — plus Kibana for log visualization.
Learn how to use MassTransit with RabbitMQ or Kafka in a two-microservice e-commerce sample and keep database writes, integration events, inbox handling, and local post-commit processing aligned through transactional messaging patterns.
In modern microservices architectures, applications are composed of multiple independent services, each managing its own data. While this design improves scalability and flexibility, it introduces a critical challenge: how to maintain data consistency across services when a business transaction spans multiple boundaries.
Caching is a powerful way to make your web applications faster and more efficient. In ASP.NET Core, HybridCache is a modern caching solution that combines the speed of in-memory caching with the consistency of distributed caching.
The CAP Theorem was introduced by Eric Brewer in 2000. It is a fundamental principle in distributed systems that describes the trade off between consistency, availability, and partition tolerance. And in the distributed systems, we can only have two of three properties simultaneously.
In .Net 7 and above, EF Core supports JSON document columns and most of relational databases like SQL Server, PostgreSQL and MySQL support this feature.
In the new era of software, ensuring performance and stability under heavy loads is very paramount. Load testing is a critical step in the software development lifecycle, as it helps identify performance bottlenecks and vulnerabilities.
In Vertical Slice Architecture instead of splitting in technical aspect, we split our system to some business functionalities and inner each business we have some features/slices.
