This is a feed of links I've run across and found interesting or noteworthy. The images, content and opinions in them are owned by their respective authors.
Marten is a .NET Transactional Document DB and Event Store on PostgreSQL. Every dotnet dev should try it as an alternative ef-core, not everything needs a fu...
A .NET document database working on any RDBMS. Contribute to sebastienros/yessql development by creating an account on GitHub.
Marten is a .NET Transactional Document DB and Event Store on PostgreSQL. Every dotnet dev should try it as an alternative ef-core, not everything needs a fu...
Dies ist Beitrag 2 von 2 der Serie “Rethinking Authentication for SPAs: Easier and More Secure with Gateways” The Problem: Security Tokens in the Browser The […]
Contribute to rebus-org/Rebus.OpenTelemetry development by creating an account on GitHub.
Distributed tracing is great for observing a request flowing through a set of distributed services. However, it can also be used as a crutch!
Posts in this series: An IntroTrace ContextDiagnostic EventsOpenTelemetry IntegrationActivity and Span CorrelationVisualization with ExportersUser-Defined Context with Correlation ContextActivitySource and OpenTelemetry 1.0Source Code In the last post, I walked through the overall problem we run into with diagnosing issues in distributed systems - mainly that it can be difficult to
Is it possible to use REST API with CQRS? Of course! Resources can represent more than just Entities, they can be Commands and Queries.
We demonstrate how to build a RESTful API on top of CQRS systems. The result joins HTTP semantics and REST style with distributed computing concerns such as eventual consistency and concurrency.
If you wonder how to design API for your advanced systems, you are in the right place. In this article, I show that using the REST API with CQRS pattern, advanced business domains, Event Sourcing, and Microservices can be easily applied. And yes, REST API can be enough for your needs!