For CTOs & architects

Why we rejected microservices for Ordivis Platform.

Why the modular monolith is the more robust design for on-premises operation – written for teams that have had to look after a Kubernetes cluster in their own data centre without a platform team behind them.

One deployment. One transaction. No distributed outages.

Microservices push complexity into the network: service discovery, distributed transactions, eventual consistency, sidecars, mesh. In the customer's data centre – without a platform team – that becomes a burden, not an advantage.

Ordivis Platform is a modular monolith: clearly separated modules (CMDB, ticketing, IPAM, ISMS …) with clean boundaries, but one shared, transaction-safe deployment. A single update run updates the entire instance atomically.

// Module boundaries inside the monolith
Ordivis Platform
 ├─ Modules.Cmdb       Api·App·Domain·Infra
 ├─ Modules.Ticketing  Api·App·Domain·Infra
 ├─ Modules.Ipam       Api·App·Domain·Infra
 ├─ Modules.Discovery  Api·App·Domain·Infra
 ├─ Modules.Security   Api·App·Domain·Infra
 └─ Modules.Audit      Api·App·Domain·Infra

1 process · 1 transaction · 1 update

The technical decisions in detail

.NET 10 throughout

All modules on one current, long-term supported runtime. One language ecosystem, one build, one debugging model – no polyglot zoo to maintain.

Recursive CTEs instead of a graph DB

CI dependencies and business service impact are computed through recursive PostgreSQL CTEs – no second, unwieldy graph system in operation.

One database per tenant

Physical separation on one PostgreSQL server, plus a central registry for tenants and memberships. Deleting a tenant means dropping a database – clean for GDPR evidence.

WinUI 3 + SignalR

The native desktop client avoids the latency of sluggish web interfaces. Admins work in real time through SignalR push.

A thin client – secure & everywhere

The desktop client talks only to the REST API – never directly to the database, and without DB credentials on the workstation (nothing to steal). Every access runs through auth, RBAC and audit; PostgreSQL stays unreachable from the client network – a minimal attack surface, no way around it. One port is enough for workstations: operation over VPN, across several sites, and with a securely published HTTPS API worldwide too.

ECDSA P-256 activation

Asymmetric signature verification is embedded locally – activation is tamper-proof and works entirely offline.

Low support complexity

No microservice network outages, no mesh debugging. Troubleshooting and testing stay manageable – for you and for us.

„The modular monolith is not a return to the big ball of mud. It is the deliberate decision to enforce modularity in the code and keep complexity out of operations – where there is no platform team in the customer's data centre.“ Architecture principle for Ordivis Platform, Grams IT

Take these decisions apart.

We prefer a technical argument to a slide deck. There is no self-hosted trial installation before general availability on 1 January 2027 – we show you the running stack live by video call. It already carries the first pilot customer's production operation.