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.4 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.
[AWS Lambda] is very well suited for the projects that doesn't have any infra but needs it where short running processes are required. But if your application need to run continuously than this might not be the very apt tool for you.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
