Re:Serverless to Monolith – Should Serverless Lovers Be Worr...
by lozenge on Sunday July 02, 2023 @05:45AM
(#36559914)
Sure, creating is easy, what about monitoring, testing, rate limiting, updating (it can't be atomically updated with another resource, good luck testing that), security patching? What if you create a condition which causes an infinite loop of invocations? This is really rare in monoliths because we all agree on patterns like MVC that determine who calls what. When Conway s Law determines your infrastructure this is no longer the case.
Re:Serverless to Monolith – Should Serverless Lovers Be Worr...
by rajamaka on Sunday July 02, 2023 @07:08AM
(#36560316)
I have worked with serverless for years and all of these are ranging from completely non issues to easily solvable.
Re:Serverless to Monolith – Should Serverless Lovers Be Worr...
by namaria on Tuesday July 04, 2023 @04:30AM
(#36583812)
"I haven't had this problem therefore it doesn't exist."
Re:Serverless to Monolith – Should Serverless Lovers Be Worr...
by nostrebored on Tuesday July 04, 2023 @02:41PM
(#36590928)
All of the problems the OP mentioned are really trivial with every serverless stack I’ve ever used.
Like many of the problems (security patching, monitoring, logging) are part of the serverless pitch.
Re:Serverless to Monolith – Should Serverless Lovers Be Worr...
by namaria on Tuesday July 04, 2023 @03:32PM
(#36591547)
Yes cloud services make it trivial to set up and run software offerings. They are designed so it is easy to enter and hard to leave. And they make things unnecessarily complicated and expensive over if it grows to any non trivial degree. By then you're stuck rationalizing your previous choice because it would be very costly and complicated to move away. I'm glad you haven't had these problems, but it doesn't mean they don't exist. The issue is, when you have one of these 'good to have' scaling problems after going all in on cloud vendor hype, it's too late. So random internet strangers who have seen the issues that lie ahead try to warn other people. Some will arrogantly say they see no problem, full steam ahead. That'll just mean they will have only themselves to blame if they ever find themselves in this quagmire.
Cloud providers don’t care about your serverless function utilization for 95% of people. A huge chunk of people will never pay more than a single digit serverless bill, regardless of if they have 450 lambdas or 40. If creating a new function matches your mental model of how things works, simplifies ops and log reading, or gives you access to a library in a different language, I’d say you made a great call.