3 ms·
Can someone explain why I shouldn't just use something like cockroachdb, yugabyte or spanner for my primary database nowadays? I've seen the pain and resources
by friedman23 4y ago
Can someone explain why I shouldn't just use something like cockroachdb, yugabyte or spanner for my primary database nowadays? I've seen the pain and resources wasted from teams needing to find ways to shard mysql and postgres and make them scale. Sure, you might say I might never need that scale but why not just avoid this problem entirely? If I'm building something I intend to support hundreds of millions of users why would I choose a technology I know will fail to scale to that?
- ReflectedImage 4y agoBecause you are working for a company that like 99% of companies have less than a million users? You want data analytics, financial reports, the ability to query your data in new ways you didn't think of when you first built the product? NoSQL comes at a great cost. When you hit a million users, the entirely of your codebase will be on-fire with scalability issues anyway so it won't make any difference?
- endisneigh 4y agoUsing a sharded database is not just for scale.
- necovek 4y agoSo instead, add more complexity? Isolation? Please do elaborate.
- friedman23 4y agoThose databases I mentioned are not NoSQL, they are relational databases.