What the hell have you built
wthhyb.sacha.house
What the hell have you built
1–10 of 239 posts
Re: What the hell have you built
#2From the titular tweet (12 years already !): https://x.com/codinghorror/status/347070841059692545
Re: What the hell have you built
#3s/postgres/sqlite/g
Re: What the hell have you built
#4s/postgres/sqlite/g
back in the day, the hype was all arround postgres, but I agree
Re: What the hell have you built
#5Nah, postgres is overhyped, MariaDB is enough and recently: https://mariadb.org/mariadb-vs-postgresql-understanding-the-...>
Re: What the hell have you built
#6Nah, postgres is overhyped, MariaDB is enough and recently: https://mariadb.org/mariadb-vs-postgresql-understanding-the-... >
I love this comment because it misses the point in exactly the way the article talks about.
Re: What the hell have you built
#7I feel like sometimes it’s a form of procrastination.
There are things we don’t want to do (talk to costumers, investors, legal, etc.), so instead we do the fun things (fun for engineers).
It’s a convenient arrangement because we can easily convince ourselves and others that we’re actually being productive (we’re not, we’re just spinning wheels).
Re: What the hell have you built
#8What the hell have you built? Turns out a pretty straightforward service.
That diagram is just aws, programming language, database. For some reason hadoop I guess. And riak/openstack as redundant.
It just seems like pretty standard stuff with some seemingly small extra parts because that make me think that someone on the team was familiar with something like ruby, so they used that instead of using java.
"Why is Redis talking to MongoDB" It isn't.
"Why do you even use MongoDB" Because that's the only database there, and nosql schemaless solutions are faster to get started... because you don't have to specify a schema. It's not something I would ever choose, but there is a reason for it.
"Let's talk about scale" Let's not, because other than hadoop, these are all valid solutions for projects that don't prioritize scale. Things like a distributed system aren't just about technology, but also data design that aren't that difficult to do and are useful for reasons other thant performance.
"Your deployment strategy" Honestly, even 15 microservices and 8 databases (assuming that it's really 2 databases across multiple envs) aren't that bad. If they are small and can be put on one single server, they can be reproduced for dev/testing purposes without all the networking cruft that devops can spend their time dealing with.
Re: What the hell have you built
#9Heh
Once you have a service that has users and costs actual money, while you don’t need to make it a spaghetti of 100 software products, you need a bit of redundancy at each layer — backend, frontend, databases, background jobs — so that you don’t end up in a catastrophic failure mode each time some piece of software decides to barf.
Re: What the hell have you built
#10s/postgres/sqlite/g
Yeah, we run a fairly busy systems on sqlite + litestream. It's not a big deal if they ae down for a bit (never happened though) so they don't need failover and we never had issues (after some sqlite pragma and BUSY code tweaking). Vastly simpler than running + maintaining postgres/mysql. Of course, everything has it's place and we run those too, but just saying that not many people/companies need them really. (Also considering that we see system which DO have postgres/mysql/oracle/mssql set up in HA and still go down for hours do a day per year anyway so what's it all good for).