AWS Lambda vs. IBM Cloud Functions vs. Salesforce Experience Cloud

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

IBM Cloud Functions [is] not the worse product on the IBM cloud. I decided to write this review as I thought it would be balanced. I would still use functions to set up a serverless architecture where execution time is pretty quick and the code is relatively simple. I wouldn't use IBM Cloud Functions for async calls obviously, as costs could be higher. The functions documentation is lacking in terms of CI/CD, and there are unexplainable errors occurring - like the network connection that I mentioned. So I wouldn't just rely on IBM Cloud Functions too much for the entire system, but make sure it's diversified.

For well-suited, this product is great for your external clientele groups that you would not necessarily want to have a high user fee rate for. So basically general public or a group that will be authorized to come in and just do a few things here and there, but you don't necessarily want them access to all of your systems and your data points for groups that it would not be a great use for. I'd say probably your high level internal staff, they're going to be using a lot of the backend functionality automations, evaluating data, managing data, and doing custom inputs. That's just not what's intended for.

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

• Great substitute for a simple API calls to run non-complicated code.
• Easy way to run Python/Java/Javascript to get something done.
• File validation.

Incentivized

• Easy to use, just like Salesforce's other products. Many users can sit down and figure it out in no time, and with a little training become power users.
• Fast and secure - Salesforce is a leader in the cloud world so you get consistently fast results and security that is top notch in the industry.
• Accessible from anywhere - if you use cloud CMS already this is a no-brainer, but for those that do in-house CMS still, this is a major difference. Mobile access from anywhere on the planet without a VPN is something you just can't do without the cloud.

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

• Billing can be a hassle, not the most responsive customer service/support team
• Handles & executes most functionalities, but other platforms offer more scalability if you're seeking consistent and stable growth

Incentivized

• Unlike other CMS platforms like Wordpress and Adobe Experience Manager, Salesforce does not provide a fully featured editor with a drag-and-drop design tool.
• Our content creators and marketing team often struggle with permissions and how to distribute content across different experience cloud sites.
• Also, there is no side-to-side comparison view for content editors to update the content easily.

Incentivized

Renewal exercise is already underway. Platform is to ubiquitous to not leverage, especially at a Fortune 50 firm

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

Strengths: - Intuitive for Salesforce Users – If you’re already working within the Salesforce ecosystem, the Salesforce CMS is easy to navigate, with a clean UI, drag-and-drop content management, and reusable assets for quick updates. - Seamless Integration – Since it connects natively with Experience Cloud, Marketing Cloud, and CRM, it allows for efficient multi-channel content distribution without needing extra third-party tools. - AI-Powered Personalization – The ability to deliver dynamic content based on user profiles and engagement data is a huge plus, making content delivery more relevant and impactful. Challenges: - Learning Curve for New Users – If you're not already familiar with Salesforce, the interface can feel overwhelming, requiring training to fully leverage all features. - Limited Customization & Workflow Automation – While it works well for structured content, advanced approval workflows and deep editorial customization are limited compared to enterprise CMS platforms like Adobe Experience Manager. - Media & Design Limitations – Salesforce CMS is not as robust for managing rich media-heavy content, which can be frustrating for teams needing more flexibility in multimedia presentation.

Incentivized

Again, since we provide and recommend solutions, I can't speak to every client's individual experience, but can offer general reflections as to keep their collaborations private, that they are satisfied with the experience. We hear a lot about how this system helps to encourage collaborations between their own business partners, customers, and internal members, and enables quality integrations with other products that help drive revenue.

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

Although support from Salesforce itself can be quite unresponsive sometimes, the community hub is incredibly helpful. The large user base of Salesforce products contribute to troubleshooting and the forums are a powerful tool for finding solutions and possible bugs and response times can be quite fast compared to your regular support channels.

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

• ICF is a lightweight service and does not require runtime configurations
• Scalable on demand and hence there is no need to pay for runtime costs

Incentivized

Salesforce Experience Cloud was selected due to its tight integration with our existing Salesforce CRM platform. Customization of the portal was much, much simpler compared to Sharepoint - especially with role-based security parameters that are ultimately inherited based on attributes within the Salesforce CRM platform. Salesforce Experience Cloud was a natural fit for this customer-facing purpose.

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

• It directly affected our expenses since we do not need to deploy and maintain a set of separate applications.
• It allowed us to pay for only the amount of time cloud functions run.
• It saved on maintenance and monitoring of the applications it replaced.

Incentivized

• Time savings for our customer success team - no need to continually follow up on tickets as customers have access to see status themselves
• In the future, it will also allow us to create more impactful knowledge articles that will increase self-service over ticket creation

Incentivized