Menu

1 / 5

For consultancies: building integration projects faster and handing them over without pain

DEV Community: opensource·rinat kozin·about 11 hours ago
#d8k2ZVQS
#devtoopensource#devto#dev#client#redb
Long article (1722 words) — no AI summary yet.
Reading 0:00
15s threshold

How many hours of your last project went into work the client doesn't want to pay for as a separate line? The broker connection, retries and duplicate protection, database migrations, deployment, monitoring. In the estimate it hides under "architecture" and "integration", and the client still asks why it takes so long.

I have been building backends for clients for over twenty years, and for the last three years and more I have built them on my own open source .NET ecosystem, redb. This article is about why it is a convenient stack for a firm that builds software for clients: what gets faster, what is easier to hand over, and where its honest limits are.

The same bricks at every client

The ecosystem is a data store, the redb.Route integration engine, the redb.Tsak host for modules and the redb.Identity login server. Data is a C# class, a process is a route, an external system is an address string. Every client gets the same project structure.

A project starts from a template.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.