| Fire the astronaut architect immediately. Seriously. I couldn't fathom why the hell you'd migrate an existing application to this other than because the guy is a one trick pony who drank all the sales kool aid from cloud vendor of the hour. We had one, he's gone. We burned millions of dollars on things with no discernible ROI because someone saw some shiny poo at a conference. It becomes a religious crusade, not a sound technical decision. Key concerns: 1. You're locking your platform into one supplier permanently. The exit fee is starting again. Literally burn it to the ground. 2. You're going to introduce problems when you migrate it. The ROI is negative if you spend money and achieve more bugs without improving functionality. 3. The cost estimation of every pure serverless platform is entirely non-deterministic. You can't estimate it at all even with calculators galore. 4. The developer story for serverless applications is quite frankly a shit show. Friction is high, administrative host is high and the tooling is usually orders of magnitude slower and more frustrating than local dev tools. 5. It's going to take time to migrate it which is time you're not working on business problems and delivering ROI to your customers. As always ask yourself: is the customer benefiting from this now or in the future? If the answer is no or you don't know, don't do it!!!! Really sit down, find a sound business decision analysis framework and put all the variables in and watch it melt instantly. All you're going to do here is put a "successful" (pah!) project under the architect's belt before he pisses off and trashes someone else's product. As a somewhat extreme opposite of this, I would at this point never allow my cloud estate to progress past portable IaaS products and possibly Kubernetes control plane management. Anything else is a business risk. |