Software architecture · System design

Decisions made before certainty

I work with founders, CTOs and boards on the technical decisions that come before a significant investment. I bring architectural discipline to AI-assisted development.

Build from architecture to production

You have an MVP to build, starting from an idea or a prototype, and need senior technical leadership to design and deliver it.

Scale a system in production

Your system starts to break under growth: response times, security findings or infrastructure costs grow faster than the number of users.

Oversee an external supplier

Your software is built by a supplier and you need someone on your side who can judge estimates, answers and releases.

<4 hdowntime since 2017, none in the last three years
Mobility · National traffic information

Replacing an inherited traffic information system

After ACI group acquired its traffic agency, I assessed the inherited PHP and Oracle system: it could not scale and went down repeatedly. I designed its replacement: 18 services on AWS that merge six sources on DATEX II, GTFS and TMC every 3 to 5 minutes and serve about 10,000 events a day to HERE, TomTom, Radio24 and others.

9%average database CPU at 9M API calls per hour
Public sector · National compliance register

Locating the load on a register of 400,000 business sites

54% of database waits came from writing a log row for every API request: 2 billion rows, 13 TB. Caching token validation cut total SQL time by 77% and database CPU by 89% in load tests. I led the architecture review and the caching strategy with Redis on top of the database.

216×query time, from 325 s to 1.5 s
Retail · Fiscal and EDI documents

Moving 150 million documents off SQL Server

12 servers processed 6,000 files an hour, but searches took minutes and history was limited to two months. MongoDB won a competitive PoC against SQL Server and Oracle. In the design benchmark, the new write path sustained 537 writes per second against the 300 required for ten times the volume.

7,500historical responses as statistical baseline
HR tech · Behavioural assessment

Moving a scoring method out of Excel

A behavioural assessment method, which scores candidates against role profiles, lived in a spreadsheet with its algorithms and 7,500 past responses. I rewrote the scoring engine in Java on RESTHeart and MongoDB, with tests that compare profiles and population statistics against the spreadsheet. The multi-tenant web application reached production in under three months.

4cities, one architecture
Luxury e-commerce

One architecture across four cities

A single shared e-commerce platform on Adobe AEM for a luxury brand: frontend in Berlin, backend in Gurgaon, deployment in Shanghai, client in Geneva. Local compliance and Chinese localization were built into the design.

2M+Docker pulls of RESTHeart
Own products · Open source

Products I build and operate

I co-created RESTHeart, the open source backend for MongoDB, in 2014: more than ten years in production, adopted by Unisys, Northrop Grumman, Crownpeak and others. Ulabase, MobiStream and Sophia, a RAG platform, are built on it.

Building software with AI keeps getting faster. When producing code takes less time, it matters more to know what that code will cost in fixes, maintenance and downtime.

AI-written code almost always looks good, even when it is fragile inside. To assess it, you need to know the practices by which it was designed, tested and prepared for production.

I organize agentic development with Lean engineering practices.

Agents need explicit job descriptions and hard guardrails. The workflow operates as a pull system: well-specified tasks wait on a board, where dedicated agents pull work within their scope, implement changes, and validate them against tests.

Without that structure, agents generate more code than anyone can review.

A new product starts with a Discovery. It takes two to four weeks at a fixed price.

Business

I start from the goals of the initiative, the obstacles in the way and the criteria that measure success. I map the main processes and the people involved.

Technology

I choose the architecture, the technologies and the infrastructure of the system. If a prototype exists, I use it as the specification. I keep its technologies when there is a reason to.

Scenarios

I define what the project includes and what it excludes, and in which order. Each possible approach comes with its assumptions, dependencies and risks, and an indicative timeline.

Document

You get a written document with enough information to decide go or no-go, and a realistic cost range for development. It is yours and can be used with another supplier.

Maurizio Turatti

Tell me what you're building.

info@maurizioturatti.com

Write to me
PerformanceSpelunking the call chainOct 2026
EngineeringMQTT and MongoDBSept 2026
EngineeringAI doesn't want to kill us, but it could do it anywaySept 2026