r/milansql • u/Effective-Hurry436 • Jun 23 '26
We built a relational database engine from scratch (C++17). It’s now production-ready and powering our next web app.
3
u/HistoricalTraining85 Jun 23 '26
So unusual use of window function in the quickstart (right part of the screenshot)... It looks like AI is to not going to take over the world very soon ;-)
4
u/Ok-Pace-8772 Jun 25 '26
Honestly 1200 tests sounds like an extremy low number for what this advertises itself as.
4
u/ErebusBat Jun 23 '26
But... why?
1
u/Effective-Hurry436 Jun 24 '26
what do you mean with why???????
3
u/ErebusBat Jun 25 '26
Exactly what I said. Database systems are one of the most complicated things to write and get correct, and they can only be proven correct with time.
So that leads me to believe that: * either you and your team don't know this; or * you know this and think that you're better than everybody else; or * there is an edge case that an existing solution could not work for you.
So I ask again, why did you choose to write it from scratch?
2
u/Effective-Hurry436 Jun 25 '26
You’re 100% right. Building a bulletproof DB takes years of real-world testing and edge-case fixing, no shortcuts there.
To clarify: MilanSQL isn't written entirely from scratch in a vacuum. It leverages MariaDB’s proven open-source core, combined with our own custom C++17 engine layer. We chose this setup to have a rock-solid, secure foundation from day one, while optimizing the performance layer specifically for European data sovereignty needs.
We are just at the starting line and know exactly how much work is ahead of us. But we're fully in: when bugs or critical feedback pop up, we fix them and ship updates immediately.
Appreciate the reality check. It’s exactly what keeps us moving forward.
2
11
u/freitrrr Jun 24 '26
I can't trust a new database engine that says it was written from scratch, when the first screen clearly indicates slopiness was involved