AWS Lambda vs. Salesforce Agentforce Commerce

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

Global Sites; larger commerce organizations but not too large where the % rev-share would affect its feasibility in a feature comparison. Salesforce is rock solid in infrastructure and rarely has outages or issues; it scaled appropriately for holiday peak and was able to accomplish anything we put our minds to as long as we staffed development appropriately. The latter, however, is not to be overlooked. Developers are necessary and expensive.

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

• Traffic - When we have sales, our traffic will increase exponentially and their cloud can handle the huge uptick in traffic we receive without overloading our servers.
• Site updates - it continually monitors in the background for any upgrades or updates needed so we don't have to go in and do it ourselves. A real time saver!
• Integration - outside plugins and add-ons are easy to install with Salesforce commerce cloud as it allows a seamless integration of extra plug ins onto our site.

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

• The UX within the Business Manager portion of Demandware, the primary interface for marketers, is generally a confusing, inconsistent mess. Particularly infuriating are the lack of consistency for search and sort behavior within the tool.
• A number of useful features, such as the ability to set schedules or tie features to unique customer segments, have seemingly arbitrary limitations imposed.
• Demandware's idea of leveraging the community to be a learning resource and a sounding board for new ideas and features is a nice theory, but in practice it doesn't work for businesses with a lot of customization. I'm left with the impression that individual support is not a priority.

Incentivized

A huge factor influencing our decision to remain on the Demandware platform is that our new parent company is standardizing all its luxury brands in the US on it. We are fortunate. However, even if we had remained an independent company, I believe we would continue on the Demandware platform for all the reasons outlined in this review. I appreciate the stability the platform has provided to our eCommerce site in the last three years as well as the continuous improvements and technological advances being rolled out that will allow us to keep the site fresh, engaging, modern and stable. I've heard many horror stories from colleagues on other platforms who struggle with the expense and complexity involved with making what should be minor and simple changes and updates to their sites.

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

The overall ease of using the system. Consolidation in location for our team members. Mobile application for on the go research, as many of our team members are constantly traveling to job sites or to meet clients. No more duplicate calls to current customers, since we have 12 different divisions that span the company. Mostly the ability to look at the database when our team members begin cultivating a new
lead/prospect with a potential customer to see if anyone within the team has a
relationship with that person or the company they work for.

Incentivized

We have only had one instance where the platform went down in the time we have been using it.

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

They are very responsive and a support technician will be assigned quickly. Even if there is further clarification needed for the ticket, or a solution is not immediately available, you feel that someone is there and staying on top of the issue. Most common issues are resolved quickly and satisfactorily.

Incentivized

The in-person training was thorough. Trainer was pretty dry, but covered everything really well.

Implementation went fairly smoothly.

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

When I think of Salesforce products, I sometimes think of them interchangeably as one big lump. It's hard not to be incredibly immersed in the ecosystem day in and day out and taking advantage of resources like Trailhead. While Microsoft Dynamics compares in quality and offerings, it doesn't offer the same engagement and resources as Salesforce in its communications, social, and marketing, which makes a difference in terms of relevance and help. Commerce Cloud comes with the support you need to succeed and the tools you need to grow. In a high demand consumer world, we need products like this to keep up and get ahead. The minute we catch up, we're behind. Salesforce helps you stay on pace and create the unique and personalized experiences customers everywhere expect.

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

• In my experience I see most of the retailers see better sales after moving to Demandware.
• Site performance is really good if the application built with best practices suggested by Demandware.
• Service integrations have some limitations in terms of quota etc but still all are inside manageable grounds.

Incentivized