Kubernetes vs. Salesforce Agentforce Commerce

K8s should be avoided - If your application works well without being converted into microservices-based architecture & fits correctly in a VM, needs less scaling, have a fixed traffic pattern then it is better to keep away from Kubernetes. Otherwise, the operational challenges & technical expertise will add a lot to the OPEX. Also, if you're the one who thinks that containers consume fewer resources as compared to VMs then this is not true. As soon as you convert your application to a microservice-based architecture, a lot of components will add up, shooting your resource consumption even higher than VMs so, please beware. Kubernetes is a good choice - When the application needs quick scaling, is already in microservice-based architecture, has no fixed traffic pattern, most of the employees already have desired skills.

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

• Complex cluster management can be done with simple commands with strong authentication and authorization schemes
• Exhaustive documentation and open community smoothens the learning process
• As a user a few concepts like pod, deployment and service are sufficient to go a long way

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

• Local development, Kubernetes does tend to be a bit complicated and unnecessary in environments where all development is done locally.
• The need for add-ons, Helm is almost required when running Kubernetes. This brings a whole new tool to manage and learn before a developer can really start to use Kubernetes effectively.
• Finicy configmap schemes. Kubernetes configmaps often have environment breaking hangups. The fail safes surrounding configmaps are sadly lacking.

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

The Kubernetes is going to be highly likely renewed as the technologies that will be placed on top of it are long term as of planning. There shouldn't be any last minute changes in the adoption and I do not anticipate sudden change of the core underlying technology. It is just that the slow process of technology adoption that makes it hard to switch to something else.

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.

It is an eminently usable platform. However, its popularity is overshadowed by its complexity. To properly leverage the capabilities and possibilities of Kubernetes as a platform, you need to have excellent understanding of your use case, even better understanding of whether you even need Kubernetes, and if yes - be ready to invest in good engineering support for the platform itself

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.

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.

Most of the required features for any orchestration tool or framework, which is provided by Kubernetes. After understanding all modules and features of the K8S, it is the best fit for us as compared with others out there.

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

• Because of microservices, Kubernetes makes it easy to find the cost of each application easily.
• Like every new technology, initially, it took more resources to educate ourselves but over a period of time, I believe it's going to be worth it.

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