Hacker News new | ask | show | jobs
by marcus0x62 967 days ago
> In October 2021, they successfully migrated their first API route to AWS Lambda, the most critical one handling all live credit card transactions. Over the following year, more and more API endpoints were migrated away from the servers to AWS Lambda.

Why? Why do people insist on doing this? Move something less important first, prove you can operate in production, then move the crown jewels.

1 comments

I'd love to hear about the rationale behind this decision, because operational cost certainly isn't it. It's ludicrous to migrate a high-traffic, high-risk API to a function-as-a-service solution like AWS Lambda. Either they have a very unique requirement or it sounds like this might very well be the poster child of clueless resume-driven development.
IME the rationale behind such decisions is what I call the "sinking ship" phenomenon in infrastructure. Maybe their system was failing in weird ways, hard to maintain, causing all sorts of issues, etc. In that "sinking ship" it's always gonna be "women and children first," or rather, their most critical systems first.
What specifically makes it ludicrous to you?