AWS Elastic Beanstalk vs. Google Cloud AI

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

Google Cloud AI is a wonderful product for companies that are looking to offset AI and ML processing power to cloud APIs, and specific Machine Learning use cases to APIs as well. For companies that are looking for very specific, customized ML capabilities that require lots of fine-tuning, it may be better to do this sort of processing through open-source libraries locally, to offset the costs that your company might incur through this API usage.

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

• good conversion from the voice to the text
• speed in the conversion from voice to text
• time-saving in the conversion activity
• analysis of the results of the conversion in real time

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

• Some of the build in/supported AI modules that can be deployed, for example Tensorflow, do not have up-to-date documentation so what is actually implemented in the latest rev is not what is mentioned in the documentation, resulting in a lot of debugging time.
• Customization of existing modules and libraries is harder and it does need time and experience to learn.
• Google Cloud AI can do a better job in providing better support for Python and other coding languages.

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

We are extremely satisfied with the impact that this tool has made on our organization since we have practically moved from crawling to walking in the process of generating information for our main task to investigate in the field through interviews. With the audio to text translation tool there is a difference from heaven to earth in the time of feeding our internal data.

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

I give 8 because although it´s a tool I really enjoy working with, I think Google Cloud AI's impact is just starting, therefore I can visualize a lot/space of improvements in this tool. As an example the application of AI in international environments with different languages is a good example of that space/room to improve.

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

Every rep has been nice and helpful whenever I call for help. One of the systems froze and wouldn't start back up and with the help of our assigned rep we got everything back up in a timely manner. This helped us not lose customers and money.

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

In fact, you only need the basic tech knowledge to do a Google search. You need to know if your organization requires it or not,. our organization required it. And that is why we acquired it and solved a need that we had been suffering from. This is part of the modernization of an organization and part of its growth as a company.

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

These are basic tools although useful, you can't simply ignore them or say they are not good. These tools also have their own values. But, Yes, Google is an advanced one, A king in the field of offering a wide range of tools, quality, speed, easy to use, automation, prebuild, and cost-effective make them a leader and differentiate them from others.

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

• Artificial intelligence and automation seems 'free' and draws the organization in, without seeming to spend a lot of funds. A positive impact, but who is actually tracking the cost?
• We want our employees to use it, but many resist technology or are scared of it, so we need a way to make them feel more comfortable with the AI.
• The ROI seems positive since we are full in with Google, and the tools come along with the functionality.

Incentivized