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
Pantheon
Score 9.8 out of 10
N/A
Pantheon is a WebOps platform where marketers and developers collaborate to drive results. The vendor states that with Pantheon, site owners maximize their capacity to update website design and functionality, responding to market trends, catering to consumer behavior, and adding real value to the business's bottom line. Today, companies compete on the basis of digital experiences, and the best results emerge from an agile build-test-learn process. Whether it's publishing content,…
$29
per month
Pricing
AWS Elastic Beanstalk
Pantheon
Editions & Modules
No Charge
$0
Users pay for AWS resources (e.g. EC2, S3 buckets, etc.) used to store and run the application.
Although it may seem a good fit for a company that needs extra control over the deployment process and development process, for a firm that is mainly concentrating on SEO, it would be an overkill. Pantheon provides that sweet automation that allows us to shed some weight on …
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.
Pantheon is excellent for medium-large websites that require high availability and a managed workflow. It would be inappropriate for small websites because of the cost or for situations where more control of the environment is appropriate. We find it useful because we rarely do anything outside of the Drupal application.
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.
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.
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.
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
Pantheon is an easy system, especially to the users with previous experience with other similar platform and the interface is clear enough to easily understand how things operates. On the Cloud deployment everything also works effectively and the technical team from Pantheon community are very helpful on providing the necessary assistant to their customers.
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.
Even tier 1 Pantheon chat and ticket support are knowledgeable, competent, and useful. They routinely understand and promptly resolve urgent, complex, and/or unusual issues that other hosts need to escalate to tier 2 or tier 3 support personnel. I honestly can't think of a truly negative or disappointing support experience in the years I've used Pantheon hosting for client websites.
- 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 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.
Although it may seem a good fit for a company that needs extra control over the deployment process and development process, for a firm that is mainly concentrating on SEO, it would be an overkill. Pantheon provides that sweet automation that allows us to shed some weight on development and focus on our business activities.
