4 ms·
Nice article. One gripe: >For example, a 200ms service task that needs to run every five minutes would need a dedicated service instance (or two!) in a traditi
by FooHentai 9y ago
Nice article. One gripe:
>For example, a 200ms service task that needs to run every five minutes would need a dedicated service instance (or two!) in a traditional model
This feels like such a straw man. Under what traditional model would you spawn off an entire server instance for such a minor function? You'd slap it in as a service on an existing host. Hosts which for a long time now have been virtualized on consolidated hardware, not bare metal.
Serverless can bring big benefits for certain workloads, but hyping it up by misrepresenting the alternatives seems a dishonest attempt to justify investment in the big architectural changes you have to make to get there.
- jotto 9y ago> Under what traditional model would you spawn off an entire server instance for such a minor function I think that's the point - would you rather run your own VPS and manage the logs/errors from a cron job? Or simply write code that conforms to their contract and not worry about logs, errors, and whether it can scale or will fail to restart itself.
- dx034 9y agoOr have another vps/server with spare capacity where this makes sense to run as well? In most cases, such a function will be closely related to other functions and can be grouped with them.