If you're new here, I'm André, a tech entrepreneur and founder of LaunchFast, a stack designed to help web developers significantly speed up their project development time. I post daily updates on my journey and progress.
Alright, folks! Here's the menu for today đ
Let's get to it.
Today Iâve sent an email to all the people who bought LaunchFast.
Iâve asked for their feedback and havenât received any replies yet, but I want to make them feel supported and that Iâm here to help if they get into trouble or find any problems with the product.
Iâve improved the current roadmap so customers can vote on their preferred features.
Non-customers can still see the roadmap, but cannot upvote.
This is how the roadmap looks at the moment.

(This is a screenshot from my local dev environment, thatâs why there are no upvotes.)
Youâll also notice that every feature has a âDiscuss on đâ button. This isnât in production yet, but it will be tomorrow.
Since the repo is private, users can click that button and discuss this feature, in public, on đ. Each feature has a corresponding post with a small description, like so đ

The downside is that users need an account on đ, but Iâll try it like this for now and see how it goes.
Iâve also added a newsletter subscription form for users who want to stay up-to-date with LaunchFast as new features are released.
If youâre one of them, feel free to subscribe!

Iâve spoken to Jan Sulaiman, Global Director at 1NCE, an IoT company, about their database performance needs. According to Jan, hitting the 500k writes/sec performance limitation of SQLite would ârequire hundreds of millions of devices.â
According to Jan (slightly edited for brevity): "[As] a very rough estimation, right now, we have around 5 Mio active devices. Our customers send, on average, one message per 15 minutes.
So that means we average 5556 messages/second.
This would also align with our overall Downlink/Uplink capacity. For our European Breakout, for example, we are currently averaging around 40 Mb/s downlink and 75 Mb/s uplink traffic. And that Breakout is handling around 2,2 Mio active devices.
Since you ask about write operations, we only need to look at the 75 Mb/s. Here I assume an average of 2 KB per message that needs to be written. If I use the bandwith, I also get roughly 4578 write operations per second.
So, it's pretty close to the first calculation.
Long story short - while we probably have quite a high number of operations we need to handle and millions of active devices - we still would never get to 500k+ transactions per second đ"
This ties into first-principles thinking and my explanation for choosing SQLite over any other database (MySQL, Postgres, MongoDB, etc), even if hosted on the same machine - SQLite is a zero-configuration, zero-latency database, and itâs just a file, making it dead simple to manage. Other databases require you to manage a server, connections, and authentication (offering another attack surface for hackers), and you wonât benefit from their higher performance anyway.
Hosted databases like Firebase and Supabase solve this problem by managing the database for you, but you pay an even higher cost: your performance is now subjected and limited to the networkâs bandwidth and latency.
In the best-case scenario, you add a 10 to 30ms overhead to every single query you make (this should be enough not to use them), in the middle-case scenario, you add 50 to 200ms of overhead if thereâs enough traffic, and in the worst-case scenario, the database is being DDoSâd and you canât connect to it, making your app dysfunctional.
But I digressâŠ
So whatâs the opportunity here? Jan agreed to be my guest on one of the videos I will do as part of LaunchFastâs documentation đ
Lisboa innovation for all is a social innovation prize from the Lisbon City Council, organized by the Unicorn Factory Lisboa and supported by the European Innovation Council, which aims to discover and support innovative and impactful solutions that can be applied practically in the city of Lisbon.
Theyâre offering 360.000⏠for projects on education, healthcare, and migration, and now that LaunchFast has been released, it would be a perfect opportunity to show, in public, what a developer is capable of with a powerful tool like LaunchFast.
LaunchFast will launch on MicroLaunch on the 1st of September!
MicroLaunch is a relatively new platform created by Said, and Iâve found a few errors, but I look forward to seeing how LaunchFast does on microlaunch and how much traffic it will bring.
At the moment, LaunchFast is hovering at around 40 users per day.

This was the plan yesterday:
As for the next steps, I donât know in which order I will do them, but this is the general plan:
Thatâs it for today, folks!
Have a great weekend and see you tomorrow!
P.S.: If youâre interested in LaunchFast, feel free to discuss and vote on the features youâd like to see come onto the product!
Nice post!
Thanks, mate!
Sqlite doesn't provide any solutions to file corruption for example
Oh, I actually donât know anything about this! Thanks for putting this on my radar, Iâll look into it.
If thereâs any articles or horror stories you can point me to, that would be awesome đđ«Ą
To answer your question, as SQLite is just a file, file corruption is handled by the file system.
For context, it has been more than 10 years since I've seen a corrupted file, and I work with thousands (millions?) of files daily.