Scaling to 15000 Functions and Beyond

by alexellisukon 10/20/23, 9:31 AMwith 57 comments
by latchkeyon 10/21/23, 11:42 PM

It is hard for me to understand why anyone would build so many individual functions. Just build one function, put a router in it and then call out to as many individual handlers as you want. Then you're just deploying a single function to the PaaS and everything is simple.

by withinboredomon 10/22/23, 12:46 AM

Can I just say I was shocked to see a "Pricing" page on something called "openX." Then, on the pricing page, there was no price... so, now I'm just confused. I'm also trying to understand what this 15k functions post is all about, since you'd need an enterprise license to use that many. Whatever that means.

by ganzuulon 10/22/23, 7:58 AM

With about 20 000 genes to make a human... What are you making that requires 15 000 functions?

by activescotton 10/21/23, 10:43 PM

Your relentless customer service is commendable. Good work. Serverless works well in many scenarios and being able to run it on any k8s cluster without proprietary platform hooks is a good thing for all of us to have an option for.

by GiorgioGon 10/21/23, 9:27 PM

Or stop chasing the latest fad(s) and build a regular old boring service. The dev experience for building/debugging/troubleshooting distributed functions/lambdas is atrocious. Use boring tech, solve business problems and create value without adding needless complexity because devs want to play with the latest toys.