F5 Distributed Cloud App Connect vs. Red Hat JBoss Enterprise Application Platform

My advice is if your firm build multi-cloud, high availability SaaS products or you just run polyglot workloads across kubernetes and VMs, then F5 Distributed Cloud App Connect is your guy. Coming from an expert, just start with a few core services or else you will be overwhelmed.

Incentivized

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

• Ease of use - standing up a new site took very little time, less then an hour.
• Connecting the dots - the ease at standing up a load balancer and advertising it on CEs was simple and straight forward. Once you get familiar with the field layout it's very comparable to BIG-IP

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

• User access roles should be more granular what we currently have
• user interface should be user friendly
• Setup process and guided workflows could add a user friendly process for first time users
• log export from SIEM tool still require a manual intervention

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

At this point it has become too focal to our operations. An entire department could collapse if we dropped it now or in the near future. My experiences as mentioned in the previous questions tell of its gravity

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

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

Incentivized

From what we have been able to test load/responsiveness is quick and when we've tested out reporting and troubleshooting modules they have pulled the correct information in quick timeframes. We haven't been able to test out any software integration with Splunk of other software on our system since we are still in early POC stages but from what we've been told we should be able to implement that in our environment

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

-F5 Distributed Cloud App Connect provides more granular security policies with features like DOS, WAF etc and others lack -F5 Distributed Cloud App Connect provides high performance global network and other rely on public internet and impact is latency and it gives F5 Distributed Cloud App Connect a better user experience

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

• Inconsistent policies and procedures and now its all seem to be sorted and now requires less support
• Deployment cycle time was reduced and achieves a faster adoption of newly added contents
• Saved migration cost and more gave durability to the existing setup

Incentivized

• 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