Viktar Patotski ·
· Performance
· 16 min read A cache is the reflex after you fix the slow query. The real decision is where it lives. A local in-memory cache is faster and simpler than Redis until you run more than one instance, and then it quietly serves stale data. Here is how to pick.
Viktar Patotski ·
· Databases
· 14 min read Most teams reach for sharding years before they need it. There is a ladder of cheaper, lower-risk fixes that comes first, and the right rung depends on which bottleneck you actually have: read load, write load, or data size. Here is the ladder, from cheapest to last resort.
Viktar Patotski ·
· Architecture
· 22 min read Both are excellent databases and for most SaaS workloads either one is fine. The honest answer: pick Postgres for greenfield, keep what you run well, and switch only for a reason you can name. Here are the few differences that actually decide it.
Viktar Patotski ·
· Architecture
· 7 min read A government directive can now switch off your AI provider overnight - and pricing, deprecation, and policy could always do it. If a core feature depends on one model API you don't control, that's a single point of failure. Here's how to treat model access like any other supply-chain risk.
Viktar Patotski ·
· Databases
· 21 min read Most slow-query problems are not a missing index, they are the wrong index, or ten indexes nobody needs. Start from the query plan, build the index the query actually wants, and drop the ones taxing every write.
Viktar Patotski ·
· Cloud & Cost
· 7 min read RDS is often the second or third biggest line on an AWS bill, sometimes the first, and most of it is avoidable. The levers that move it: fix the queries before you upsize, match the instance to your load shape, and stop provisioning storage for data that has not arrived yet.