AWS Elastic Beanstalk vs. Salesforce Data 360

I have been using AWS Elastic Beanstalk for more than 5 years, and it has made our life so easy and hassle-free. Here are some scenarios where it excels -

• I have been using different AWS services like EC2, S3, Cloudfront, Serverless, etc. And Elastic Beanstalk makes our lives easier by tieing each service together and making the deployment a smooth process.
• N number of integrations with different CI/CD pipelines make this most engineer's favourite service.
• Scalability & Security comes with the service, which makes it the absolute perfect product for your business.

Personally, I haven't found any situations where it's not appropriate for the use cases it can be used. The pricing is also very cost-effective.

Incentivized

Great tool for client management, sales tracking, cases studies. Using is as the source of truth for all client communication. Allowing more integration options for cc and ACH payments. Right now the options are limited and only integrate with strict processing capabilities that are not always in the businesses best interest.

Incentivized

• Getting a project set up using the console or CLI is easy compared to other [computing] platforms.
• AWS Elastic Beanstalk supports a variety of programming languages so teams can experiment with different frameworks but still use the same compute platform for rapid prototyping.
• Common application architectures can be referenced as patterns during project [setup].
• Multiple environments can be deployed for an application giving more flexibility for experimentation.

Incentivized

• Allows use to bring external data into Salesforce as zero-copy
• Is able to present data using standard Salesforce reports familiar to our users
• Allows us to establish multiple relationships between our CRM data and the external data to contextualize the imported data.

Incentivized

• Limited to the frameworks and configurations that AWS supports. There is no native way to use Elastic Beanstalk to deploy a Go application behind Nginx, for example.
• It's not always clear what's changed on an underlying system when AWS updates an EB stack; the new version is announced, but AWS does not say what specifically changed in the underlying configuration. This can have unintended consequences and result in additional work in order to figure out what changes were made.

Incentivized

• pricing or costing visibilty, we can't estimate what would be consumption this month and suddenly we get surprised
• CI/CD can be improved, that looks a difficult and hard
• Also sandbox comes with many limitation so very hard to replicate production like environment to test

Incentivized

As our technology grows, it makes more sense to individually provision each server rather than have it done via beanstalk. There are several reasons to do so, which I cannot explain without further diving into the architecture itself, but I can tell you this. With automation, you also loose the flexibility to morph the system for your specific needs. So if you expect that in future you need more customization to your deployment process, then there is a good chance that you might try to do things individually rather than use an automation like beanstalk.

Incentivized

The overall usability is good enough, as far as the scaling, interactive UI and logging system is concerned, could do a lot better when it comes to the efficiency, in case of complicated node logics and complicated node architectures. It can have better software compatibility and can try to support collaboration with more softwares

Incentivized

Most of the daily use features, are very usr friendly, intuitive, every end user can learn how to manage and operate basic activities such as enter information, send an email, send a campaign, create an email marketing template, run a report on the renewals for the month, open and close a support case, create new account or a new contact, etc

Incentivized

As I described earlier it has been really cost effective and really easy for fellow developers who don't want to waste weeks and weeks into learning and manually deploying stuff which basically takes month to create and go live with the Minimal viable product (MVP). With AWS Beanstalk within a week a developer can go live with the Minimal viable product easily.

Incentivized

- Do as many experiments as you can before you commit on using beanstalk or other AWS features. - Keep future state in mind. Think through what comes next, and if that is technically possible to do so. - Always factor in cost in terms of scaling. - We learned a valuable lesson when we wanted to go multi-region, because then we realized many things needs to change in code. So if you plan on using this a lot, factor multiple regions.

Incentivized

We also use Heroku and it is a great platform for smaller projects and light Node.js services, but we have found that in terms of cost, the Elastic Beanstalk option is more affordable for the projects that we undertake. The fact that it sits inside of the greater AWS Cloud offering also compels us to use it, since integration is simpler. We have also evaluated Microsoft Azure and gave up trying to get an extremely basic implementation up and running after a few days of struggling with its mediocre user interface and constant issues with documentation being outdated. The authentication model is also badly broken and trying to manage resources is a pain. One cannot compare Azure with anything that Amazon has created in the cloud space since Azure really isn't a mature platform and we are always left wanting when we have to interface with it.

Incentivized

we have evaluated Snowflake, adobe rt-cdp as well. They also offer a very strong capabilities but the Data 360 is more suitable for us because of the same Salesforce ecosystem. The main key factor is without any custom code we were able to include it into our automations. And ofcourse with agentforce already in plans, we had to pick Data 360

Incentivized

• till now we had not Calculated ROI as the project is still evolving and we had to keep on changing the environment implementation
• it meets our purpose of quick deployment as compared to on-premises deployment
• till now we look good as we also controlled our expenses which increased suddenly in the middle of deployment activity

Incentivized

• Salesforce Data Cloud has a positive impact on me as a realtor because it is easy to generate reports on customer data and see what is needed to be bumped to the next level. We have to earn a certain commission by the end of the year and it makes it easy to see how close you are
• It has a positive impact on keeping track of customers because it is nice to have it all in one place which is a nice time saver
• I like that you can even see customer info from other agents making it nice to compare and try and pass others
• Makes the customers journey smooth sailing because everything is in one place

Incentivized