AWS Lambda vs. Tanzu Application Catalog

Lambda excels at event-driven, short-lived tasks, such as processing files or building simple APIs. However, it's less ideal for long-running, computationally intensive, or applications that rely on carrying the state between jobs. Cold starts and constant load can easily balloon the costs.

Incentivized

The best way to take advantage of VMware Application Catalog (Bitnami) is as in the case I mentioned, that you constantly implement these free software, where any time saved is important in terms of installation, configuration and testing environment, it really is a very useful solution, also if you need a good community and support; however the cloud and VMs solutions is not designed for huge products, these can be slow or remain insufficient if the use of these grows a lot, even though it is an easy-to-use product, you need to have enough knowledge in terms of installation and management of cloud solutions, a beginner can find himself in trouble

Incentivized

• No provisioning required - we don't have to pay anything upfront
• Serverless deployment - it gets executed only when request comes and we pay only for the time the request is getting executed
• Integrates well with AWS CloudWatch triggers so it is easy to setup scheduled tasks like cron jobs

Incentivized

• pre-packaged templates they provide.
• ease of cloud-deployment of your projects.
• The development community page always has useful information and there is a lot of support.

Incentivized

• Developing test cases for Lambda functions can be difficult. For functions that require some sort of input it can be tough to develop the proper payload and event for a test.
• For the uninitiated, deploying functions with Infrastructure as Code tools can be a challenging undertaking.
• Logging the output of a function feels disjointed from running the function in the console. A tighter integration with operational logging would be appreciated, perhaps being able to view function logs from the Lambda console instead of having to navigate over to CloudWatch.
• Sometimes its difficult to determine the correct permissions needed for Lambda execution from other AWS services.

Incentivized

• Possibility to configure the implementation through mobile devices
• Sometimes the performance of the VMs is slower than expected
• A best way to do the upgrades, you have reinstall and reconfigure in this process

Incentivized

I give it a seven is usability because it's AWS. Their UI's are always clunkier than the competition and their documentation is rather cumbersome. There's SO MUCH to dig through and it's a gamble if you actually end up finding the corresponding info if it will actually help. Like I said before, going to google with a specific problem is likely a better route because AWS is quite ubiquitous and chances are you're not the first to encounter the problem. That being said, using SAM (Serverless application model) and it's SAM Local environment makes running local instances of your Lambdas in dev environments painless and quite fun. Using Nodejs + Lambda + SAM Local + VS Code debugger = AWESOME.

Incentivized

Most of it is intuitive. I think some of the awkwardness is found by new users who are unfamiliar with other software applications.

Incentivized

Amazon consistently provides comprehensive and easy-to-parse documentation of all AWS features and services. Most development team members find what they need with a quick internet search of the AWS documentation available online. If you need advanced support, though, you might need to engage an AWS engineer, and that could be an unexpected (or unwelcome) expense.

Incentivized

They have an expert team, not just a frontline team that has learned the FAQs but a team that knows the product.

Incentivized

AWS Lambda is good for short running functions, and ideally in response to events within AWS. Google App Engine is a more robust environment which can have complex code running for long periods of time, and across more than one instance of hardware. Google App Engine allows for both front-end and back-end infrastructure, while AWS Lambda is only for small back-end functions

Incentivized

VMware Application Catalog (Bitnami) offers better tools to complete the task faster and more efficiently. The customer support and knowledge base is also well presented and trained

Incentivized

• Positive - Only paying for when code is run, unlike virtual machines where you pay always regardless of processing power usage.
• Positive - Scalability and accommodating larger amounts of demand is much cheaper. Instead of scaling up virtual machines and increasing the prices you pay for that, you are just increasing the number of times your lambda function is run.
• Negative - Debugging/troubleshooting, and developing for lambda functions take a bit more time to get used to, and migrating code from virtual machines and normal processes to Lambda functions can take a bit of time.

Incentivized

• We save a lot of time implementing the apps, less engineers working on this phase
• The upgrade process of the apps can be a pain and a waste valuable time
• The mains options of the VMware Application Catalog (Bitnami) are free so is important for save money in our organization

Incentivized