4 ms·
It still amazes me that AWS doesn't provide good local debugging/development support out of the box. I feel like we're slowly going back in time. Iteration cycl
by _gabe_ 4y ago
It still amazes me that AWS doesn't provide good local debugging/development support out of the box. I feel like we're slowly going back in time. Iteration cycles are very high, debugging cloud dev is essentially placing a bunch of print statements and trying to trace the code, build times take forever...
Edit: Here's some more conversations I found on the topic of the terrible workflow for cloud dev if anyone is interested https://news.ycombinator.com/item?id=26855037 https://news.ycombinator.com/item?id=26855037
- sozal 4y agoYou are right, local development and debugging is still one of the biggest pains of serverless world. This was our motivation to develop MerLoc
- _gabe_ 4y agoIt looks awesome :) Unfortunately we have a full Javascript stack at my company, but I'll keep an eye on this in case anybody adds more dev environments!
- user3939382 4y agoI just got xdebug working in ECS. It took really understanding xdebug config in depth but it’s amazing now that it’s working.
- tlarkworthy 4y agoYeah, you are right. I made https://webcode.run https://webcode.run also for this reason (also hot code reload and debugging but for JavaScript computational notebooks)
- deleted 4y ago[deleted]
- scarface74 4y agoThere is “sam local”. But honestly, all a Lambda is a script with a function that takes two parameters - an event and a context. You can scaffold testing and development just like you would a controller action in an MVC framework - use a test harness that calls the method with the correct JSON payload and usually a null event context.
- kkielhofner 4y agoThis where Azure and the Microsoft ecosystem is pretty far ahead from a developer experience standpoint. I’m not an MS fanboy by any stretch but VS Code, Azure Functions, and even local storage emulation with Azurite is pretty slick. First time I played with it my background was very far from anything in this space (literally first time I used node) and I had a completely locally developed toy function with storage up and running in maybe 30 minutes. Then in a few clicks it was deployed and running in Azure. All in less time than it took for me to wander through the AWS docs and console to even figure out which product to use.