4 ms·
How is that different from just a normal Webhoster? Except, being more expensive, I guess?
by PurpleRamen 3y ago
How is that different from just a normal Webhoster? Except, being more expensive, I guess?
- CuriouslyC 3y agoIt gives you the flexibility to easily swap in pieces in another language without making architectural changes while being as simple to work with (after devops work) as a monolith. If you have an orchestration setup to manage your functions rather than using Lambda/etc it doesn't cost any more than a monolith either (aside from competent devops salary).
- PurpleRamen 3y ago> It gives you the flexibility to easily swap in pieces in another language Which you can also do with a Webhoster. Well, it depends a bit on what languages or environment they offer of course. > without making architectural changes I guess those pieces have a way to communicate with each other? So the point here is more that you are forced to work with an architecture which is from the beginning designed for pluggable pieces.
- irjustin 3y agoI should've put context, but we are a b2b and barely have any CPU utilization and mostly in bursts. Normally we would have at minimum 2x Fargate "mediums" sitting around for redundancy. ~US$130/mth now our server costs <$5/mth. Our CI/CD is WAY more expensive.