AWS Lambda vs. Salesforce Lightning Platform

Overview
ProductRatingMost Used ByProduct SummaryStarting Price
AWS Lambda
Score 8.8 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.
$NaN
Per 1 ms
Salesforce Lightning Platform
Score 8.3 out of 10
N/A
Salesforce Platform is designed for building and deploying scalable cloud applications with managed hardware provisioning and app stacks. It provides out-of-the-box tools and services to automate business processes, integrate with external apps, and provide responsive layouts and more.
$25
Per User Per Month
Pricing
AWS LambdaSalesforce Lightning Platform
Editions & Modules
128 MB
$0.0000000021
Per 1 ms
1024 MB
$0.0000000167
Per 1 ms
10240 MB
$0.0000001667
Per 1 ms
Starter
$25.00
Per User Per Month
Plus
$100.00
Per User Per Month
Offerings
Pricing Offerings
AWS LambdaSalesforce Lightning Platform
Free Trial
NoNo
Free/Freemium Version
NoNo
Premium Consulting/Integration Services
NoNo
Entry-level Setup FeeNo setup feeNo setup fee
Additional Details
More Pricing Information
Community Pulse
AWS LambdaSalesforce Lightning Platform
Top Pros
Top Cons
Features
AWS LambdaSalesforce Lightning Platform
Access Control and Security
Comparison of Access Control and Security features of Product A and Product B
AWS Lambda
9.3
3 Ratings
3% below category average
Salesforce Lightning Platform
-
Ratings
Multiple Access Permission Levels (Create, Read, Delete)9.03 Ratings00 Ratings
Single Sign-On (SSO)9.52 Ratings00 Ratings
Reporting & Analytics
Comparison of Reporting & Analytics features of Product A and Product B
AWS Lambda
6.1
3 Ratings
4% below category average
Salesforce Lightning Platform
-
Ratings
Dashboards6.73 Ratings00 Ratings
Standard reports6.52 Ratings00 Ratings
Custom reports5.02 Ratings00 Ratings
Function as a Service (FaaS)
Comparison of Function as a Service (FaaS) features of Product A and Product B
AWS Lambda
7.9
3 Ratings
3% below category average
Salesforce Lightning Platform
-
Ratings
Programming Language Diversity9.03 Ratings00 Ratings
Runtime API Authoring8.33 Ratings00 Ratings
Function/Database Integration8.33 Ratings00 Ratings
DevOps Stack Integration6.03 Ratings00 Ratings
Platform-as-a-Service
Comparison of Platform-as-a-Service features of Product A and Product B
AWS Lambda
-
Ratings
Salesforce Lightning Platform
8.9
36 Ratings
8% above category average
Ease of building user interfaces00 Ratings7.836 Ratings
Scalability00 Ratings9.834 Ratings
Platform management overhead00 Ratings8.230 Ratings
Workflow engine capability00 Ratings9.332 Ratings
Platform access control00 Ratings9.733 Ratings
Services-enabled integration00 Ratings9.433 Ratings
Development environment creation00 Ratings9.230 Ratings
Development environment replication00 Ratings9.328 Ratings
Issue monitoring and notification00 Ratings7.731 Ratings
Issue recovery00 Ratings7.929 Ratings
Upgrades and platform fixes00 Ratings9.733 Ratings
Best Alternatives
AWS LambdaSalesforce Lightning Platform
Small Businesses
IBM Cloud Functions
IBM Cloud Functions
Score 8.1 out of 10
AWS Elastic Beanstalk
AWS Elastic Beanstalk
Score 9.1 out of 10
Medium-sized Companies
Red Hat OpenShift
Red Hat OpenShift
Score 8.8 out of 10
IBM Cloud Private
IBM Cloud Private
Score 9.5 out of 10
Enterprises
Red Hat OpenShift
Red Hat OpenShift
Score 8.8 out of 10
IBM Cloud Private
IBM Cloud Private
Score 9.5 out of 10
All AlternativesView all alternativesView all alternatives
User Ratings
AWS LambdaSalesforce Lightning Platform
Likelihood to Recommend
9.3
(48 ratings)
9.3
(36 ratings)
Usability
9.0
(13 ratings)
5.5
(2 ratings)
Support Rating
8.7
(20 ratings)
8.1
(15 ratings)
User Testimonials
AWS LambdaSalesforce Lightning Platform
Likelihood to Recommend
Amazon AWS
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.
Read full review
Salesforce
We use Salesforce Lightning Platform in everyday business as sales coordinators. By using this tool, we are able to send new requests to clients and communicate regarding pending proposals in real-time. This also tool holds many of our client accounts where we are able to monitor their sales and revenue.
Read full review
Pros
Amazon AWS
  • 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.
Read full review
Salesforce
  • Reporting and Dashboards are thorough and can show a wealth of important data to inform and scale processes. It's helpful in a high volume sales cycle to be able to quickly identify weak points in performance and productivity so that adjustments can be made.
  • Highly customizable. We are able to customize just about everything which allows us to track very specific things and in theory create better efficiency.
  • Parent/Child account hierarchy exists which is helpful.
  • Contact records can be associated with multiple accounts and opportunities. This, in theory, should minimize duplicates and mismanagement of contacts.
  • Console helps a lot with data nesting. Having a fairly comprehensive look at an account without searching through various tabs and sections speeds up an otherwise cumbersome platform.
Read full review
Cons
Amazon AWS
  • 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.
Read full review
Salesforce
  • Can be cumbersome: takes multiple clicks to get where you need to go
  • Lightning is slower than original Salesforce, and it is very noticeable
  • The UI change means sometimes I can't find what I need, so I have to switch back to the Classic version to find it
Read full review
Usability
Amazon AWS
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.
Read full review
Salesforce
This builds off a number of things I have already mentioned. This question completely depends on the competence of the developer. This makes the user friendliness of the UI 50/50. However if you have the ability I would say it is quite UI friendly.
Read full review
Support Rating
Amazon AWS
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.
Read full review
Salesforce
Salesforce's support is top-notch. They have subject-matter experts that are accessible at all times to address needs as they come up. They let you know in advance when there are system updates and enhancements so that you are prepared for upcoming changes. I've never had an issue that wasn't addressed immediately when reaching out for support.
Read full review
Alternatives Considered
Amazon AWS
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.
Read full review
Salesforce
We were previously using an older version prior to it becoming Salesforce Lightning Platform so we were well adverse on the advantages of using a CRM, to begin with. It made sense to convert to Salesforce Lightning Platform after we were given a free trial of the platform. Certain reps were chosen to experiment with it and from there a decision was made to move forward. We've been customers ever since.
Read full review
Return on Investment
Amazon AWS
  • 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
Salesforce
  • Better visibility of Accounts and Contacts interactions makes it easier to maintain during employee transitions.
  • Tracking of current jobs and relating them to past jobs is very useful.
  • More efficient use of Sales Reps time.
  • Sales Managers have good visibility into how their people are working.
Read full review
ScreenShots