AWS Cloud9 is a cloud-based integrated development environment (IDE) used to write, run, and debug code with just a browser. It includes a code editor, debugger, and terminal. Cloud9 comes prepackaged with essential tools for popular programming languages, including JavaScript, Python, and PHP, with no need to install files or configure a development machine to start new projects.
N/A
AWS Lambda
Score 8.5 out of 10
N/A
AWS Lambda is a serverless computing platform that lets users run code without provisioning or managing servers. With Lambda, users can run code for virtually any type of app or backend service—all with zero administration. It takes of requirements to run and scale code with high availability.
AWS Cloud9 has great advantages over other software that have the same purpose as the one, one of which is that it is available in the cloud so it does not require installation time, as well as being updated, while other tools such as Visual Studio Code require the previous …
AWS Lambda
No answer on this topic
Features
AWS Cloud9
AWS Lambda
Access Control and Security
Comparison of Access Control and Security features of Product A and Product B
When I am working with a large team of developers. Also, when a security policy, you are not allowed to install any app on your laptop. Cloud 9 is well integrated with Cloud commit. So we don't have to spend time in configurations.
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.
Confusing documentation - AWS's documentation remains quite confusing, and the layout of other services/settings that you have to use with Cloud9 can be a bit of a handful.
Sometimes slow - As the size of a project increases, the editor gets increasingly slower, and starts slowing down the browser overall.
Long setup process - The setup for Cloud9 can be hard and tough, especially since the documentation is quite hard to understand.
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.
The interface for Cloud9 needs some improvement. It is simply not as powerful and intelligent as a local text editor would be and thus it lacks the capabilities of fast filling when coding. Otherwise, I think it has a fair interface that they have tried mimicking an IDE.
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.
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.
[AWS] Cloud9 offers specific features not available in the competition: Code collaboration using the chat features is the highlight which sets it apart. [The] code completion feature makes [it] very similar to the offline IDE like eclipse. It's much easier to use compared to Codeanywhere. It provides terminal access to EC2 instances and hence other amazon services.
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
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.
