4 ms·
I actually designed the original serverless system (a few years back when I was still at Prime Video), and yes we did and it did sort of look like it could work
by timbokz 4y ago
I actually designed the original serverless system (a few years back when I was still at Prime Video), and yes we did and it did sort of look like it could work until it didn't. Obviously wasn't the right solution for the scale we had in mind (or rather the type of problem we were working on) but it's sad to see the mistake of one team be used to justify shitting on serverless as a general solution.
- MichaelZuo 4y agoI thought the article was phrased bit oddly. Do you mind saying where it did seem like a sensible solution?
- moorow 4y agoNot OP, but as someone that's now rebuilt 4 serverless systems into monoliths (across 4 orgs) and achieved some pretty stunning results, serverless would be useful if all of these things are true: 1) Your workload is fairly simple 2) Your workload is unpredictably spiky from low lows to high highs 3) Latency is not a concern If any of these aren't true, you're probably better off using a monolith (but you should think logically about your individual use case).
- jjgreen 4y agoA rational and pragmatic response to an issue like this? You must be new here ...
- MichaelZuo 4y agoThese conditions seem to limit serverless systems to a very niche set of circumstances.