Likelihood to Recommend
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.
Read full review
Well Suited - Collecting data and organizing it. - Eliminate a lot of admin work. - Send auto-response emails to customers/users. - Notify relevant users when the data is updated. - Creating business process flows. Less Appropriate - If creating a flow to create a pdf file that combines all the attachments into one pdf file. - Flow will fail sometimes if the flow is too long and complex and if the flow connections are changed from one user to another.
Read full review Pros 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. Read full review "When an item is changed in a SharePoint list, do ____" - very easy to trigger massive flows of data based upon a one-field change on a SharePoint list. Being able to manually trigger from a Microsoft PowerApp button press to perform actions. Scheduled tasks - once a day, get every record in (LIST) with (Filters) and do (Stuff) to them. Read full review Cons 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. Read full review I think general training could be improved. I'm sure there are many more uses than the simple automation tasks I was using Power Automate for, but I didn't have the time or bandwidth to dig through Microsoft's documentation on the tool. Read full review Likelihood to Renew
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.
Read full review Usability
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.
Read full review
For most tasks WinAutomation is great and easy to use. You just set up tasks on a step by step basis and you can even tell the program what to do when there is an error (such as continue with job). Sometimes with complicated web extraction jobs it would be good to be able to easily extract data from the web page source.
Read full review Support Rating
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.
Read full review
So Microsoft Flow support for its general troubleshooting or correcting issues is excellent. But to my knowledge, Microsoft Flow itself does not have service providers, even though they offer templates on their online app. I have found myself many times trying to complete individual actions that have no known template or even forum example. Every business is unique, and Microsoft does an excellent job of providing versatile yet straightforward systems. Microsoft Flow is definitely on the more advanced side of things. Having support or being able to purchase superior service (on building personalized flows) would be great.
Read full review Implementation Rating
- 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.
Read full review Alternatives Considered
We also use
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
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.
Read full review
Microsoft Power Automate is the first flow-based service that I have used, and I loved its convenience. It does take some time to learn and a lot of research. I recommend that you first plan out how you imagine that the flow should work and change things around as you start creating the flows.
Read full review Return on Investment 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 Read full review Power Automate has allowed us to create applications or customer interfaces we would not have been able to if we weren't able to move data around like we can with Power Automate Power Automate helped us connect 3rd party systems that previously had no connection by passing data between different channels. This reduces license counts. Read full review ScreenShots