3 ms·
For the amount of money that AWS is making it's amazing on the lack of documentation beyond the simple lambda hello world. I've been using C# and looking up ho
by quaffapint 5y ago
For the amount of money that AWS is making it's amazing on the lack of documentation beyond the simple lambda hello world.
I've been using C# and looking up how to handle DI and have been trying to piece together things from old articles and SO posts that I have no idea hold true today or not. Why they simply can't provide up to date best practices for various scenarios is beyond frustrating. I guess they're big enough they don't need to care that much.
- melony 5y agoTheir enterprise sales team is another story entirely.
- muh_gradle 5y agoI paid for Linux Academy, pre and post merger with acloud guru. It made such a huge difference in brining me up to speed. AWS docs and tutorials are just never enough sadly.
- elboru 5y agoI had the same issue a few weeks back. My solution was a variation of a SO answer. It was frustrating to not find an official answer.
- davidjfelix 5y agoAfter writing lambdas for node, python, go and java/kotlin, my advice is use a deterministic, compile-time or generated DI (in Java world, something like Dagger) or simply write the setup script that wires the components together. If you don't do this, your runtime DI will become one of the most expensive parts of your lambda stack. It will dramatically affect performance and your requirements for memory in ways it simply wouldn't for long running container services.
- philliphaydon 5y agoI have north of 400 (c#) lambdas for step functions. There’s absolutely 0 need for DI.
- davidjfelix 5y agoI totally agree here. We have used Dagger in a couple of translated Java/Kotlin lambdas but for the most part, controlling your setup scripts tightly matters which is the opposite of DI.