K8s is overkill. Jvm is heavy. Pg is fine but relational dbs generally suck.
K8s is overkill. Jvm is heavy. Pg is fine but relational dbs generally suck.
I've been learning k8s fundamentals recently after using borg for a long time and then awhile kind of just poking at k8s trying to use it without learning it. Honestly I think it seems like about as simple as a solution to a broad set of real common problems could plausibly be.
You're gonna need to give me some more on why it's "quite flawed for modern web apps". I may even agree with you, but it's tough to know from what you've written so far.
Referring mostly to the query planner - you have no control over it, and you have to dive deep to figure out why it's making certain plans, and how it collects statistics to make these calls. Plus the planner essentially gives up at 6+ joins.
> quite flawed for modern web apps
Try listening to updates on a query.
It’s fundamentally the wrong approach and people don’t realize. The relational model is good for analytics.
Think about how often you need to know the internals or you have to debug perf by trying to get a black box to do what you want.
Devs should be a layer deeper.