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
Azul Platform Prime
Score 8.6 out of 10
N/A
Azul Systems headquartered in Sunnyvale is exclusively focused on Java and the Java Virtual Machine (JVM). They build fully supported, standards-compliant runtimes that help enable Java-based businesses. Their services include Azul Platform Prime (formerly Zing), a JVM with "better behavior" enabling sustained performance, fast warmup and predictable latency without GC pauses, jitter or application timeouts. Zing can be deployed in an on-prem data center or on the Cloud.
N/A
ComponentOne
Score 9.0 out of 10
N/A
ComponentOne Studio, from software company GrapeCity in Pittsburgh, Pennsylvania, provides Visual Studio controls.
$1,299
per year per developer
Pricing
AWS Elastic Beanstalk
Azul Platform Prime
ComponentOne
Editions & Modules
No Charge
$0
Users pay for AWS resources (e.g. EC2, S3 buckets, etc.) used to store and run the application.
No answers on this topic
Enterprise
$1,299.00
per year per developer
Offerings
Pricing Offerings
AWS Elastic Beanstalk
Azul Platform Prime
ComponentOne
Free Trial
No
No
Yes
Free/Freemium Version
Yes
No
No
Premium Consulting/Integration Services
No
No
No
Entry-level Setup Fee
No setup fee
No setup fee
No setup fee
Additional Details
—
—
—
More Pricing Information
Community Pulse
AWS Elastic Beanstalk
Azul Platform Prime
ComponentOne
Features
AWS Elastic Beanstalk
Azul Platform Prime
ComponentOne
Platform-as-a-Service
Comparison of Platform-as-a-Service features of Product A and Product B
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.
If you want some low cost JDK provider where you need the frequent updates as well, you can go ahead for Azul Zing instead of OpenJDK. But if budget is not a concern, I would recommend going for some well known company such as Oracle. Also if you are using Azul for production, make sure to use it for Dev ENV too so as to reproduce issues.
C1 is great for creating custom reports. We have client apps where we've created some fairly complicated reports such as invoices and real estate inspections. We also use the True DBGrid in many of our apps since it is so customizable. Its grouping and filtering features are very nice and can provide summary counts and totals at the bottom or right side of the grid that are very handy.
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.
The True DBGrid control is nice for showing parent/child relationships and being able to drill down and show the child data. It also is nice for showing summary totals.
The report engine is great for building custom reports for Win Forms or web apps. It can do everything that Crystal Reports can do.
They have a good selection of controls that can do just about anything you can imagine.
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
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.
- 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.
We have been in business since 1992, so we have used many different products over the years. The two other products we've primary used that are similar to ComponentOne, are Infragistics and Crystal Reports. Infragistics has a vast array of controls similar to ComponentOne. We use both to be honest and I'm not sure which one I would pick over the other. I guess that would depend on what you're trying to accomplish and if one had some control or capability that the other didn't. ComponentOne does have the reporting capabilities, where Infragistics does not.
ComponentOne allows us to add additional features to our apps that wouldn't be found in apps written with just Visual Studio itself. That allows our clients to get more creative in their requirements, which in turn, means more work and billable hours for us!
Our apps appear more professional when using ComponentOne which helps us get projects for new clients.
ComponentOne also helps us to save clients some money since we are not having to develop things that it can do from scratch.
