Thanks! Didn’t realise that customization existed via Swagger.
As far as macro goes, you don’t need to do anything special for SAM, since the SAM macro has already translated function definitions into standard CloudFormation template.
Alex Debrie has a good tutorial: https://www.alexdebrie.com/posts/cloudformation-macros/
Please don’t think of Nuclio (or any other platforms for that matter) as “Lambda Killer”, it’s another FAAS platform with its advantages and disadvantages. Lambda is fit for many problems but is not the right solution for every problem, and neither is Nuclio the silver bullet for all problems.
Because there is no
TimeoutCount metric, and unlike errors, there is no error message either (you get a line
Task timed out after x seconds instead).
So when your alert goes off because the error count spiked, what do you do? You look for “error” in the logs, and you won’t find anything! Of course, if you know to look for…
Why do you think Lambda functions are fragile? You get multi-AZ redundancy (3 AZs) out of the box, better security (no OS-level attacks), and auto-scaling. That’s a pretty good baseline resilience!
Also, invocations can last for 15 mins.
For sharing code within a bounded context, e.g. a service or API made out of multiple functions, you can have them in the same repo, like I have the
lib folder in this repo.
That’s a very valid point and one that I had run into a few times myself. There are workarounds for that however, by splitting the resources into nested stacks.
The serverless framework has a number of plugins that lets you do that. None of them is perfect, and I have even once rolled my…
All of those are points that should be discussed, so even AWS novices can learn from and understand when this approach is appropriate to their use case.
I don’t agree with your assessment that this combination of requirements is niche. But regardless of whether it’s niche or not, if it’s your requirement, then you gotta deal…
It really depends on your requirements, hence why we discussed the approach with 3 different criteria. If precision is important to you, then yes, you’re right, it’s not a good fit for you.
But equally, there are use cases where scalability is of paramount importance and precision is of little consequence. One of my clients…
Thank you! This is too often ignored and you end up with whatever culture that just happens to be. Founders play such an important role in shaping that culture by setting examples and ensuring recruitment is aligned with company culture.