AWS Elastic Beanstalk vs. Google Cloud Run vs. SolarWinds Database Performance Analyzer

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

Microservices and RestFul API application as it is fast and reliant. Seamless integration with event triggers such as pubsub or event arc, so you can easily integrate that with usecases with file uploads, database changes, etc. Basically great with short-lived tasks, if however, you have long-running processses, Cloud Run might not be idle for this. For example if you have a long running data processing task, other solutions such as kubeflow pipelines or dataflow are more suited for this kind of tasks. Cloud Run is also stateless, so if you need memory, you will have to connect an external database.

Incentivized

This is an easy 10 because I actually have recommended this product to multiple clients and colleagues! Any shop that writes its own SQL queries will benefit from the insight provided by SolarWinds Database Performance Analyzer, so they know which of their queries is causing a bottleneck. Small shops or databases with only a few tables likely will see far fewer opportunities for optimization.

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

• Auto scaling is the best one
• provide direct VPC connectivity and rigid network
• Cloud SQL and Pub/Sub services
• Handling latency issues

Incentivized

• Maintains historical SQL execution data, enabling forensic analysis
• Has the ability to slice and dice the data so that you can drill down to the execution of a single SQL statement being executed by a stored procedure
• Alerts to when the consumption pattern changes
• Shows historical average run times against the current, illustrating problems when they arise
• Provides tuning advice based on best practices

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

• The UI can be made simpler. Currently the UI is bloated and it takes time to find out what you want
• More integrations with container registry providers (ECR, dockerhub)
• Better permissions UX. Currently GCP requires service accounts to be used with cloud products, the experience adding/removing permissions is difficult to navigate

Incentivized

• Alerts seem to be lacking in DPA compared to competitor's tools. They can be setup but are not quite as easy or as helpful as some other tools I have used.
• Grooming/pruning the repository database isn't very easy. We don't manage a lot of instances but our repo DB has grown pretty significantly.
• At times when I am drilled-down to a chart, it can be difficult to navigate around from that point to another time range/query/metric.

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 definitely need to renew it because we dont own our own infrastructure and storage and we are happy with Cloud Run features

Incentivized

We have relied on this product for a very long time and it continues to exceed expectations. The product is a vital part of our organization at this point, it would not be very ideal for us to abandon it. We use it almost every day and depend on its alerts for critical parts of our business

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

The UI/console is great... the documentation is top-notch for developers, but the CLI itself when you have to script around it is very complex and easy to forget some options... the downside of a generic command line client.

Incentivized

I don't want to think about managing clusters of SQL servers in the future without this tool. We have demoed other tools and SolarWinds Database Performance Analyzer is the gold standard for usability and insight into what your servers are doing. The UI is a bit dated, but everything is laid out in a logical manner and drilling down into queries or timeslices is extremely intuitive.

Incentivized

Not seen any major issues when we run applications its good

Incentivized

Initially we felt slow but slowly it picked up and easy to manage

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

I have had to use their support on a few occasions, for reasons that I am not clear about until recently I have always had problems upgrading the software (although the last 2 updates have gone without issue which I am very pleased to say). On those unfortunate occasions, the support has been brilliant with either excellently documented guides on how to resolve the issue by myself or have been hands-on with calls and screen sharing to remotely fix the issue. Every time the problem was sorted and more importantly, nothing was lost (apart from a bit of time). And as I stated above whatever the problem was that was causing my upgrade issues appears to have been resolved in the last 2 updates.

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

I was involved in the initial implementation setup, Its easy with the given documentaiton we can do ourself. Not that critical

Incentivized

Follow the guidelines for the capacity of the servers. We found that the DPA databases were getting rather large and also that there are ways to reduce their size built into some of the options.

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

AWS Lambda supports code zip package, enabling lower cold start time. Also, AWS Lambda pricing is much simpler, easier to understand.

Other than that, the 2 products are very similar, including the Docker image support: the image must be built based on proprietary base image.

Obviously, if your other services are running in GCP, then Google Cloud Run is your only choice for tight integration, & private networking.

Incentivized

At the time, we found SolarWinds Database Performance Analyzer to be easier to setup and to have a richer feature set than Redgate SQL Monitor, plus, from what I remember, the DPA pricing worked better for us over the course of a year. We're very happy with all the features DPA has to offer.

Incentivized

Not part of purchase.

Incentivized

It has good auto scale feature and reliable also

Incentivized

We have very good support when needed

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

• Built in support for auto scaling helps reduce operational overhead
• Any application performance issues can be addressed quickly by allocating more resources while a proper fix can be planned and rolled out later
• Using Google Cloud Run enables development of microservices which provides granular control for scaling critical services in the platform

Incentivized

• It has allowed us to progress as an organization with much less reliance on a direct DBA than would traditionally be required
• Allowed us to be much more proactive in our performance monitoring and responding to issues that would affect users.

Incentivized