Amazon Elastic Kubernetes Service (EKS) vs. Salesforce Lightning Components & Developer Experience

It is well suited when you want to have a Kubernetes cluster in AWS Cloud and want to avoid all the management overhead of maintaining your own cluster in terms of the control plane. EKS seems to be lacking in features when compared with AKS and GKE. Backups, service mesh, and monitoring have a lot of room for improvements.

Incentivized

If you have a large customer base and a large amount of data on each of your customers, it is really strong in creating personalized content that your salespeople can use in their pitch meetings—and then setting up workflows for automated for lifecycle journey creations to automatically go out to customers.

Incentivized

• Upgrade the kubernetes clusters to the latest version with a single click
• Auto scaling policies to automatically scale the nodes
• Detailed logs and events on the cluster within the EKS clusters portal, cloudwatch logs and metrics

Incentivized

• It has a very smooth integration with Salesforce and third-party tools, ensuring easy tracking of policies and assets.
• It also has impressive security features like used-based permissions and encrypted data.
• Everything can be managed from a centralized place which saves a lot of time.

Incentivized

• AWSIAM integration with Kubernetes RBAC could be better.
• Enabling some add-ons like service mesh, and monitoring will be nice instead of having to install them yourself after the creation of the cluster.
• EKS bootstrap time could be faster ...

Incentivized

• It takes a while before it recognizes bounced emails.
• We get so many notifications from a single action. Not sure if this can be modified in the settings though.
• Error messages are sometimes unclear which makes it hard for us to identify the problem.

Cluster maintanence is reduced, easier to deploy resources, great observability insights

Incentivized

It's very good, but it's still living in a little bit in an older design aspect, but I think a lot of it is about to come out, just hasn't quite gotten there yet. Still a little clunky from a you have to know it to know it or you know it to use it. It takes a little bit of training to get into it. It's not quite the, anybody can come in and start using it immediately, type feel.

Incentivized

I am not an administrator so there may very well be outstanding Support and I am just not privy to it. On a user level it's hard to gauge the effectiveness and responsiveness of Support because nearly everything has to go through an administrator

Incentivized

It feels like AWS is behind the EKS race, the only advantage I'm able to see right now is the support of IPv6, however, trying to promote AWS alternatives that are different from the market and more like a vendor locking solutions like ECS/Fargate have kept AWS behind and focusing on the wrong things. EKS needs to really improve its integration with the Kubernetes ecosystem and have an enterprise solution for monitoring, backups, and service mesh.

Incentivized

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.

Incentivized

• Good performance of platform without hiccups
• Less number of people required to manage cluster
• Easier to deploy new microservices

Incentivized

• 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.

Incentivized