adimiko / transactionalbox

Outbox and Inbox Pattern in .NET (scalability & fault tolerance). Ensures eventual consistency between services. (microservices, event-driven architecture, message streaming)

Hi, I'm Adrian Mikołajczyk 👋

.NET Developer

Software Enginner at Warsaw School of Computer Science 👨‍🎓 ENG | PL
Hobbies: Programing 💻 | Street workout 🤸‍♂️ | Finance 💸 | Economy 💹

Languages and Tools 🛠️

C# | ASP.NET | WindowsForms | Docker | Postman | Visual Studio Code | Visual Studio

transactionalbox's Issues

Shared IEntityTypeConfiguration for OutboxMessage (EntityFramework)

Duplicate detection (Idempotent messages)

System.Text.Json Serializer

for JsonSerializer etc.

Messages compression and decompression

Distributed lock to standalone package

Get message from Transport

Add message to Outbox (Storage)

Shared IEntityTypeConfiguration for InboxMessage (EntityFramework)

using for DistributedLock

DistributedLock should be used with using, because when will be exception Dispose method will be executed and lock will be released.

InMemory lock SemaphoreSlim(1,1)

ConfigureAwait(false)

InMemory Transport

TransportMessageFactory - divides into multiple TransportMessages when the payload will be greater than the transport limit per message

• maximum expected bytes of transport message => X
• transport message bytes limit (retrun Transport package) => Y

Round_up(X/Y) = number of transport messages

ITransactionalBoxLogger (Wrapper Pattern)

Create wrapper for Microsoft ILogger.

Envelope Pattern

Sequential GUID

Cancellation Tokens for Workers

New tasks when the prototype is ready

Create new tasks based on problems encountered while creating the prototype

Message expiration time

Prototype refactoring

TTL for IdempotentInboxKeys (concrete message type)

Multiple messages in payload (Transport)

Settings Validator

Entity Framework Outbox Model

Model for Transport

|POC| OutboxWorker: EntityFramework - Scaling and parallel processing

BackgroundServiceBase (Problem): when there are a lot of fired tasks, not all are processed

IInboxHandler - compile handle method using LabdaExpression

Transport discriminator

One outbox with messages for multiple transports

Get message from inbox

HostName Service

Wrap Dns.GetHostName() to app service

Place where can be used

• TransactionalBox.OutboxWorker.Kafka

Inbox Idempotency

TimeProvider abstraction

InMemory OutboxStorage

Entity Framework Inbox Model

InMemory InboxStorage

Database structure optimized for performance

Outbox Serializer Configuration

Add logo to all packages

Push message to Transport

Outbox worker: processing in packages

OutobxWorker should get the package of messages and add them to the transport.
It should then mark as processed the messages that have been added to the transport.

InboxExecutionContext

Gzip (compression & decompression)

Decorate BackgroundService (errors, retry, logging etc.)

Create a single logic that can be reused by background services

Inbox Deserializer Configuration

Remove processed messages from outbox

Split one big message into multiple small

ServiceNameProvider

App service, which will contain the name of the service

Custom compression & decompression

InboxWorker: Listening to multiple topic