AWS Auto Scaling vs. Red Hat JBoss Enterprise Application Platform

It is well suited for scaling up our cloud virtual machines to handle the increase or decrease in workload. It really helps us to satisfy the demand because it doesn't take lot of time to spin up new machines. If there is unpredictability in the demand it is very useful. But it is a over kill if demand is consistent.

JBoss EAP is subscription based/open source platform. It's very reliable and great for deploying high transaction Java based enterprise applications. It integrates well with third party components like mod_cluster and supports popular Java EE web-based frameworks such as Spring, Angular JS, jQuery Mobile, and Google Web Toolkit.

Incentivized

• Set policies to add more instances when CPU utilization exceeds.
• Prevents downtime, as we don't need to stop the servers.
• Auto Scaling group can be setup for different types of apps.

Incentivized

• MOD_CLUSTER integration. JBoss EAP integrates pretty well with mod_cluster. This is an intelligent load balancer especially useful in highly clustered environments.
• Supports enterprise-grade features such as high availability clustering, distributed caching, messaging etc.
• Supports deployment in on-premise, virtual and hybrid cloud environments.

Incentivized

• Update code and configuration when the number of servers is always changing
• How will user-uploaded content make it to new servers

Incentivized

• Difficult to replicate configuration outside of a container environment
• Still requires quite a bit of knowledge of the CLI
• Integration with deployment tools requires CLI knowledge

Incentivized

We are planning to migrate away from Jboss to Tomcat as Jboss has shown not interest in supporting OSGi which is heavily used at our shop

Incentivized

We use AWS auto scaling for scaling up our cloud virtual machines to handle the increase or decrease in workload. It really helps us to satisfy the demand because it doesn't take lot of time to spin up new machines. I gave the rating 10 because it really does help you to handle the sudden spike in number of requests.

JBoss overall is easy to use. The installation and deployment of applications are quick. Documentations and support are also readily available.

Incentivized

JBoss EAP is lightweight and doesn't really consumes much physical resources. It's high performing and suites well for high transaction Java enterprise applications. The out of box performance settings are not really great and you will have to configure the settings to suite your environment to leverage it's full benefits.

Incentivized

Fast response.

Incentivized

Used for the below reasons:

• Easy to implement and use
• Pay per use, cost savings
• Automate and build scaling plans
• Automate performance and workload

Incentivized

We selected JBoss because of compatibility with EJB's. We currently are trying to reduce our footprint and will highly consider using Tomcat.

Incentivized

• optimized the cost effectiveness
• save lot of money which help the organization to use it in effective areas
• Not applicable for all use cases.It is specific use cases and business problems

• Jboss EAP is easy to deploy and configure. This lead to lower cost and faster delivery.
• Even though we have large number of machines running JBoss, we have only two Jboss Administrators. It doesn't requires too much administration and maintenance on daily basis and reduces number of administrators required for large implementations.

Incentivized