3 ms·

Generally it's fun resume builder but not actually time well spent on your business. One super server can go far enough and hopefully you can design it to be a

Generally it's fun resume builder but not actually time well spent on your business. One super server can go far enough and hopefully you can design it to be able to scale as needed later.

jameskegel 10y ago
This is a risky assertion to make, in some cases for us.
- jerf 10y ago
  All engineering advice comes with the implicit caveat "subject to your local concerns". Yes, of course you may be working in a startup that requires 25GPUs to serve even one customer. No sarcasm. I can imagine some startups that might meet that requirement. But there are an awful lot of startups that start massively overengineering their footprint early when all they need is a web server with a cold or hot spare (use a load balancer with automatic failover if you've got one in your cloud or something, if not I wouldn't stress, and automatic failover on prototype-level application code can cause its own issues) and a database server with a good backup story and some mechanism for quickly bringing up a new one if necessary. (This generally leads you to some sort of clustering thing or a hot replicated spare because it doesn't take long before your database requires hours to rebuild from a backup or something.) You're often better served just giving occasional thought to how you might split things up in the future and using that to at least hint your design than actually splitting things up immediately.
aeorgnoieang 10y ago
> you can design it to be able to scale as needed later What's different about what you're referring to above and what the commenter mentioned? It seems to me like they were designing the app to be able to scale.
- brianwawok 10y ago
  Except they are also doing the dev-ops yucky work to do the scaling. It is a lot of extra work with no value until later. Say they are making a crud app. Keep no state in session. Deploy as easily as possible. Boom, done. Later you can add a load balancer to scale to 100 servers. Right now you can run it on 1. It is 'designed to scale'. But actually running your single app in a 1 node k8s cluster? That is days of extra work for nothing right now.

Generally it's fun resume builder but not actually time well spent on your business. One super server can go far enough and hopefully you can design it to be able to scale as needed later.

jameskegel 10y ago

This is a risky assertion to make, in some cases for us.

jerf 10y ago
All engineering advice comes with the implicit caveat "subject to your local concerns". Yes, of course you may be working in a startup that requires 25GPUs to serve even one customer. No sarcasm. I can imagine some startups that might meet that requirement. But there are an awful lot of startups that start massively overengineering their footprint early when all they need is a web server with a cold or hot spare (use a load balancer with automatic failover if you've got one in your cloud or something, if not I wouldn't stress, and automatic failover on prototype-level application code can cause its own issues) and a database server with a good backup story and some mechanism for quickly bringing up a new one if necessary. (This generally leads you to some sort of clustering thing or a hot replicated spare because it doesn't take long before your database requires hours to rebuild from a backup or something.) You're often better served just giving occasional thought to how you might split things up in the future and using that to at least hint your design than actually splitting things up immediately.

aeorgnoieang 10y ago

> you can design it to be able to scale as needed later What's different about what you're referring to above and what the commenter mentioned? It seems to me like they were designing the app to be able to scale.

brianwawok 10y ago
Except they are also doing the dev-ops yucky work to do the scaling. It is a lot of extra work with no value until later. Say they are making a crud app. Keep no state in session. Deploy as easily as possible. Boom, done. Later you can add a load balancer to scale to 100 servers. Right now you can run it on 1. It is 'designed to scale'. But actually running your single app in a 1 node k8s cluster? That is days of extra work for nothing right now.