AWS Lambda vs OutSystems

• AWS Lambda is a welcoming platform, supporting several languages, including Java, Go, PowerShell, Node.js, C#, Python, and Ruby. And if you need to deploy a Lambda function in another language, AWS offers a Runtime API for integration.
• We really appreciate how AWS Lambda is always-on for our functions, with only a brief "cold-start" waiting period the first time a function is called after being dormant.
• In addition to only generating costs when it's actually being used, AWS Lambda really puts the "serverless" in serverless architecture, offering turnkey scaleability and high availability for our code with zero effort on our part.

Read full review

• Deployment management – OutSystems has a built in robust, multi-environment deployment system that helps ensures the clean and error free deployment of applications through the development, testing and production product lifecycle
• Rapid application development – Through the low code, graphical development environment you can develop applications far quicker than with more traditional development environments
• Cross platform mobile development – OutSystems handle the development and building of mobile application for both iOS and Android in a simple streamlined way that removes 90% of the problems normally associated with multi platform development

Read full review

• The UI and Developer experience is not so great. IF you use an abstraction like Serverless Application Model (SAM), things get pretty easy, but it's still AWS UI/DX you're working with after that (which is to say, not their strength).
• Documentation is always a mixed bag. Sometimes it's just easier to google your specific problem and see how others have solved it. This can be much faster than trying to find an example that may or may not be there in the documentation (which oftentimes has multiple versions and revisions).

Read full review

• The platform controls all the parts. While great for development and overall maintenance, it could lead to discussions with your DBA (who has to trust the platform). As a developer I love the platform, as a DBA I would like more control.
• By making software development model driven using flows, you are forced to rethink the way of programming. It makes it easier, but sometimes the way of working leads to code which could be optimized (standard problem in model based software development).
• Most of the code is generated, so the technical knowledge of the inner working of coding are not Essentials. This could lead to degration of this knowlegde. As part of this, most technologies will only be used when OutSystems supports it. They do a good job on implementing these things. But things like Node.js would be nice.

Read full review

• I was able to perform a lot of processing on data delivered from my website and little or no cost. This was a big plus to me.
• Programming AWS Lambda is quite easy once you understand the time limits to the functions.
• AWS Lambda has really good integration with the AWS S3 storage system. This a very good method of delivering data to be processed and a good place to pick it up after processing.

Read full review

• The ease of use of the OutSystems development process has been the biggest ROI for us. We have developed our Framework product and maintained/enhanced it with only 4 workers.
• OutSystems has enhanced their product very significantly over the last 4 years. They have gone from a simple to use tool to a very simple to use sophisticated tool that covers the standard mainframe-based computing apps and the apps used on handheld mobile devices all using the same basic set of development tools.

Read full review