AWS Elastic Beanstalk is the platform-as-a-service offering provided by Amazon and designed to leverage AWS services such as Amazon Elastic Cloud Compute (Amazon EC2), Amazon Simple Storage Service (Amazon S3).
$35
per month
Microsoft Dynamics 365
Score 7.9 out of 10
N/A
Microsoft Dynamics 365 is a CRM providing sales, marketing, and service functionality. It is offered as SaaS and on-premise. Dynamics 365 is part of the larger Dynamics suite of business intelligence and ERP products.
$44
per month
Pricing
AWS Elastic Beanstalk
Microsoft Dynamics 365
Editions & Modules
No Charge
$0
Users pay for AWS resources (e.g. EC2, S3 buckets, etc.) used to store and run the application.
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.
All told, if it hadn't been for the fact that we were testing it with both employees who knew CRM lingo and those who were new, we wouldn't have found such an issue. The program itself can be very useful for people who already manage CRMs, who know how to use them, who know how to run and manage employees on them, namely because of the "one-stop-shop" concept in data visibility. When it came down to it though, if you have high-turnover, then this product will devolve into only being used for it's base components. Down the middle, we found that the people who'd been in marketing for 4-5 years fell into the product easily because of the way it was written. Everyone before that, with novice experience, thought it was written like a textbook for a graduate class - little to no leeway if you don't happen to know one specific term
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.
Some useful out-of-the-box features, like mass uploads of Leads from trade shows or when qualifying a Lead, CRM automatically creates the Opportunity, Contact, and Account for you, etc.
Really powerful customizations through the user interface to improve user experience. Things like Business Rules, for example, if Field A = 1, then Field B = 2 and Field C = 2, if Field A = 2, then Field B and Field C don't apply, so automatically hide them.
Or other functionality that improves user experience, like Business Process Flows. These walk users step by step through our business process, helping them know when certain actions should take place, and at what point other data is now required. We've used this extensively with our Lead to Opportunity to Quote to Order process, helping users understand the business process each step of the way.
Customizations built on top of the platform now called model-driven PowerApps. You can have connections to "typical" data, like Accounts, Contacts, or Opportunities, for example, but then connect that data to custom entities, records that only apply to your specific business. This is all done through the user interface and allows you to customize and automate specific line-of-business applications for your specific needs.
Behind the scenes, D365 CE is built on SQL. So the data conforms to industry standards and makes it much easier to interact with. Your developers and IT team will thank you.
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.
Microsoft Dynamics 365 storage & license cost can prohibit some large deployments or even cost-sensitive small projects from using the platform (although I'm certain most deployments would realize a positive ROI if implemented correctly with process automation).
The cost and licensing document for Dynamics 365 is 61 pages and will take a rocket scientist to understand it. It's better to just have your Microsoft help estimate the cost if they are willing to help you that.
The documentation on how to first fully understand the Out of the Box default solution and settings is lacking or even non-existing. This has the potential to derail Dynamic 365 launches and implementations from the gitgo. Want to use an out of the box entity?.. well it's probably related to 5 other entities that require configuration and full understanding of it to successful implement. And you ask where is the laymen guide or instructions?... User groups and forums. In Summary, Microsoft can up its game in deployment training and supporting documentation.
Microsoft needs to incentivize more external platforms to build app connectors for easy integration, such as ZenDesk, Slack, Tableau, etc. Even the current connector apps such as Salesforce, MailChimp, Docusign are useless or don't work at all.
Several limitations inhibit successful Dynamics 365 deployments such as: limited number of Rollup field calculations (summarizing fields on child/related records), limited number rows that can exported to Excel via advanced find, Dynamics 365 files, log and database storage size limit is extremely small and will always require purchasing additional storage (for Online deployments).
New user buy-in or acceptance or system platform changes can be difficult if a solid change management plan isn't enacted.
Don't expect much help from Microsoft on implementation or solutions unless it's a technical flaw with the platform. Microsoft relies on their MVP partner network to consult for implementations at a hefty cost. Hiring a knowledgeable and savvy Dynamics 365 System Administrator can reduce the need for consultant support; of course, this is dependant upon many many variables.
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.
CRM has allowed us to keep all of our data in one place that is easy for all users within the company to view. I came into the company after they had been using CRM for about 4 years. They have all said that since we have used this it has helped us control work processes better, it has allowed us to be able to track things so much better, and has been something that has helped unite many processes that used to be all over the place. We are currently using CRM 4.0 and are planning on upgrading in the next 18 months to the 2011 version. Support for 4.0 is almost all but dried up. Understandably so. Some of the customization we have done, and a plugins we use, are now contained within the 2011 version so we are looking forward to that upgrade. We use an email marketing company as well, and they primarily support the 2011 version, but their product connects and is integrated within CRM. This is a great benefit as well so that all of our marketing information can be contained in one location.
It is a great tool to manage your applications. You just need to write the codes, and after that with one click, your app will be online and accessible from the internet. That is a huge help for people who do not know about infrastructure or do not want to spend money on maintaining infrastructure.
The user-interface is very clunky, truncating data fields while wasting space on the screen. There are too many menus.
Getting bulk data into the system used Excel. This caused much "mojibake" (look it up in Wikipedia) by the poor handling of different character sets (UTF-8 and Windows 1252).
Getting data out of the system was extremely long-winded and unreliable. It seemed that Microsoft never wanted us to copy data out of the system.
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.
Our partner, Ledgeview Partners has been FANTASTIC to work with. They are always timely in their response and have taken time to understand our business and our specific needs. We've made a lot of advanced customizations and they have been a great help in making those updates.
- 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.
We used a data warehouse to house our data, and our IT team and implementation vendor worked diligently ahead of time to construct idea implementation plans. Out of millions of records- we had less than a dozen errors, which is remarkable. My major insight is simply having a group of completely devoted individuals working towards your goal who fully understand the desired outcome. Focused resources for implementation season are critical to success.
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.
Salesforce has more desirable functions than Microsoft Dynamics 365, at a competitive price. Its user interface is far more superior, it has more customization, easier customization, and out of the box it is more pleasing to the eye and to the end user. If the client doesn't have a deep-rooted connection with Microsoft I wouldn't leap to Dynamics 365.
On our purchase, I'd been interrogated about our usage. Our needs are met by Microsoft Dynamics 365, which is simple to use. With so much data and information available, we must ensure that it is presented correctly to managers. Due to a lack of use, we don't have to spend as much money on Salesforce.
My company's preferred program right now is Microsoft Dynamics 365. We use it to keep track of customers and important sales metrics in a streamlined manner. Anyone familiar with CRMs will find the tool extremely useful. Considering that we have a good turnover, this product will be used for its basic segments. As a result, there are few chances of error with Microsoft dynamics because it is so easy to use. Many options for recording data on these leads are available. It meets our needs and pays off.
