3 ms·
That seems like the worst of both worlds, during the brown-out you have to keep paying for the compute while your customers don't get a reliable service, even i
by remram 3y ago
That seems like the worst of both worlds, during the brown-out you have to keep paying for the compute while your customers don't get a reliable service, even if they have a plan to migrate.
Also you probably can't keep charging customers for that period since you offer a crippled service on purpose.
- scosman 3y agoIf you are shutting it down, you can pay for the grace period. Period.
- remram 3y agoJust shut it down for real (after proper early warnings), so you save on compute and no one is confused about the state, and offer data retrieval for the grace period. Brownouts are great for API changes, but not very useful before a full shutdown.
- scosman 3y agoYou assume warnings reach users. Some people miss emails. Fewer miss a service going offline. Keeping data after shutdown is a good backup.
- remram 3y agoThat's why I'm saying to take it offline. Purposefully broken service is not very valuable, can't really be sold, and yet can still be missed; it also costs you money.