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.
$NaN
Per 1 ms
LambdaTest
Score 7.4 out of 10
Mid-Size Companies (51-1,000 employees)
LambdaTest is a cloud-based platform that helps users run manual and automation tests of their website and mobile apps. Users can test their native mobile application (Android and iOS) and mobile websites on Real Devices on cloud or choose from emulators & simulators for a multitude of configurations.
$15
per month per user
Pricing
AWS Lambda
LambdaTest
Editions & Modules
128 MB
$0.0000000021
Per 1 ms
1024 MB
$0.0000000167
Per 1 ms
10240 MB
$0.0000001667
Per 1 ms
Lifetime Free
$0
1 Concurrent session Per Month
Live
15/Month (Billed Annually)
per month Parallel Test
Real Device (Includes Live)
25/ Month (Billed Annually)
per month Parallel Test
Web Automation
$79/per Month (Billed Annually)
per month Parallel Test
Web & Mobile Browser Automation
$99/per Month (Billed Annually)
per month Parallel Test
Native App Automation
$125/per Month (Billed Annually)
per month Parallel Test
Web & Mobile Browser on Real Device
$128/per Month (Billed Annually)
per month Parallel Test
HyperExecute Cloud (Multi OS)
$159/per Month (Billed Annually)
per month Parallel Test
HyperExecute On-Premise
CUSTOM PRICING
Parallel Test
Enterprise
CUSTOM PRICING
Parallel Test
Offerings
Pricing Offerings
AWS Lambda
LambdaTest
Free Trial
No
Yes
Free/Freemium Version
No
Yes
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
For Enterprises Customize plans. Please contact our Chat Support or drop us email at support@lambdatest.com
Scenarios where AWS Lambda is well suited: 1. When we need to run a periodic task few times in a day or every hour, we may deploy it on AWS Lambda so it would not increase load on our server which is handling client requests and at the same time we don't have to pay for AWS Lambda when it is not running. So, overall we only pay for few function invocations. 2. When some compute intensive processing is to be done but the number of requests per unit of time fluctuates. For example, we had deployed an AWS Lambda for processing images into different sizes and storing them on AWS S3 once user uploads them. Now, this is something that may happen few times every hour on a particular day or may not happen even once on other days. To handle this kind of tasks AWS Lambda is a better choice as we don't have to pay for the idle time of the server and also we don't have to worry about scaling when the load is high. Scenarios where AWS Lambda is not appropriate to use: 1. When we expect a large request volume continuously on the server. 2. When we don't want latency even in case of concurrent requests.
LambdaTest is very well suited for cross-device testing as they provide a wide array of options to choose from. It is very reliable and mimics the actual device. In scenarios wherein the user is having an urgent issue and needs to emulate the bug, the app sometimes is quite slow and may hinder from having a very efficient testing.
Lambda provides multiple methods for triggering functions, this includes AWS resources and services and external triggers like APIs and CLI calls.
The compute provided my Lambda is largely hands off for operations teams. Once the function is deployed, the management overhead is minimal since there are no servers to maintain.
Lambda's pricing can be very cost effective given that users are only charged for the time the function runs and associated costs like network or storage if those are used. A function that executes quickly and is not called often can cost next to nothing.
Putting a significant portion of your codebase into AWS Lambda and taking advantage of the high level of integration with other AWS services comes with the risk of vendor lock-in.
While the AWS Lambda environment is "not your problem," it's also not at your disposal to extend or modify, nor does it preserve state between function executions.
AWS Lambda functions are subject to strict time limitations, and will be aborted if they exceed five minutes of execution time. This can be a problem for some longer-running tasks that are otherwise well-suited to serverless delivery.
Sometimes the live apps gets slow so its better that this doesn't happen more often
Still room to add more device vendors like, Huawei now doesn't support play services so its better thay we also have some devices which are with Huawei services only
It is very reliable and can provide great results for all the stakeholders. Access is very quick and there are wide-array of devices that can be used to provide a robust application. Having limited resources on a remote setup really helps users to complete task with this emulator. This helps a lot in development team.
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.
LambdaTest provides video recording and screenshots of all your tests in their test logs, which makes tracking easier. Test statuses, such as Lambda Error and VM allocation, allowed us to quickly troubleshoot any build that failed while executing. So overall, it's been great to use for our Tester and Developer team.
I have not needed support for AWS Lambda, since it is already using Python, which has resources all over the internet. AWS blog posts have information about how to install some libraries, which is necessary for some more complex operations, but this is available online and didn't require specific customer support for.
The customer support team is very active and cooperative. Once, I contacted them in their off timings because of an issue, I got an instant reply from the executive and he resolved the issue very efficiently. This is why we have been using LambdaTest for more than two years. It is best suited for us.
Azure Functions is another product that provides lambda functionality, but the documentation for some of Azure's products is quite hard to read. Additionally, AWS Lambda was one of the first cloud computing products on a large cloud service that implemented lambda functions, so they have had the most time to develop the product, increase the quality of service, and extend functionality to more languages. Amazon, by far, has the best service for Lambda that I know.
LambdaTest offers me a large number of real-time mobile devices and browsers for testing, as well as debugging tools like Screenshot Testing and Issue Tracker. This is what I like the most about LambdaTest and prefer it over Sauce Labs. Additionally, my team has reported faster testing speeds with LambdaTest compared to SauceLabs
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.