4 ms·
Out of the tar pit suggests we should all go back to one big SQL server and probably resort to something approximating SSR web apps again. You know... 2-3 big p
by bob1029 3y ago
Out of the tar pit suggests we should all go back to one big SQL server and probably resort to something approximating SSR web apps again. You know... 2-3 big powerful servers like we used to have. How fast is a stack like this today compared to 20 years ago?
This is mostly what we have done. We want to make money. There are barely 10 of us. We don't have time for make believe work that doesn't bring in extra revenue. We used to play in traffic with conversations like "micro services" and "one repo per service" but our investor killed that mode of business and gave us one more chance to do it right.
I recall the original reason for moving away from one big database being something approximating "it won't scale". How well are those various k8s contraptions scaling relative to the "legacy" verticals they purport to replace? How many of us would go back in an instant if given the opportunity?
I think the biggest fear for most on HN is going through ego death over this. The fact that even your "hard" problem is trivially solved with boring tools that were invented before you were born.
- mwcampbell 3y agoI wonder if even the multiple servers and dedicated SQL server are overkill for most applications. The simplicity of running the whole thing on one machine using SQLite, with Litestream or something like it for backups, is really seductive. Edit to add: and as you've pointed out before, the locality of having the database right there in the application process leads to really good performance.