Get the latest tech news
Good system design
I see a lot of bad system design advice. One classic is the LinkedIn-optimized “bet you never heard of queues” style of post, presumably aimed at people who are…
Drawing the line here is a judgment call and depends on specifics, but in general I aim to have my tables be human-readable: you should be able to go through the database schema and get a rough idea of what the application is storing and why. If you’re pulling, that will mean standing up a bunch (say, a hundred) of fast read-replica cache servers that will sit in front of your main application and handle all the read traffic. The main point I’m trying to make is what I said at the start of this post: good system design is not about clever tricks, it’s about knowing how to use boring, well-tested components in the right place.
Or read this on Hacker News