Seven hundred stored procedures in the CleenUI codebase aren't a legacy pattern. They're an explicit interface contract between the application and the data layer — one that survives team changes, schema migrations, and AI-generated queries better than runtime-generated SQL does.
Read →The CleenUI codebase uses Dapper + ADO.NET against 700+ stored procedures across 300+ Azure SQL tables. Not as a legacy holdover — as a deliberate architecture decision made when the codebase was designed and confirmed by production deployment.
Read →The decision to use Dapper + ADO.NET against stored procedures is architectural, not accidental. It's a deliberate choice about who owns the query plan — and in the AI era, it turns out to be exactly the right choice.
Read →Microservices split what should not be split. An ORM adds a mapping layer between your code and your query plan. The modular monolith on .NET 8 + Azure SQL avoids both traps. Here is the architecture and why it holds.
Read →Configure a demo environment in about twenty seconds — theme, spacing, the modules you care about, sample data for your industry — then launch the full dashboard in your browser. Nothing to install, no signup.