Share your experience using Microgen Aptitude [EOL]

Our main use cases with JBoss Enterprise Application Platform were that we are an application software developer, developing the channel platform, the internet banking, and the mobile banking for the banks.

The channel platform was hosted on JBoss Enterprise Application Platform.

JBoss Enterprise Application Platform's best features include that it was very simple to install and enabling clustering between two instances was simpler than compared to WebSphere or WebLogic. Clustering became very much easier, and setup was very straightforward.

I used other products such as WebSphere and WebLogic, and I saw JBoss Enterprise Application Platform as a very lightweight container rather than a heavy container. The startup time was much faster compared to other application servers, and debugging was reliable. We did not see the application going into a hang state. It never happened in JBoss Enterprise Application Platform. Other application servers typically degrade over time, and the application resources can become hung.

The memory utilization and the heap garbage collection that was running was very efficient, so the resource utilization was better. The robust security model of JBoss Enterprise Application Platform contributed positively to our data integrity and compliance in our development processes, and it was very good.

In my opinion, there are areas that could be improved with JBoss Enterprise Application Platform, such as the management console.

I am not certain whether it has all of the enterprise features incorporated such as what IBM WebSphere has, including real-time performance monitoring of your application, monitoring your JVM heap graphs, or even the CPU utilization graphs. I am not certain whether this is present or not.

We thought that if application performance monitoring tools were already part of the management console at runtime, it would be very helpful.

The last time I used JBoss Enterprise Application Platform was version 7.7.4 recently.

I used other products such as WebSphere and WebLogic, and I saw JBoss Enterprise Application Platform as a very lightweight container rather than a heavy container.

The startup time was much faster compared to other application servers, and debugging was reliable. We did not see the application going into a hang state.

My thoughts on JBoss Enterprise Application Platform's pricing is that from a subscription model perspective, the price was very reasonable compared to other application servers and other commercial products. JBoss Enterprise Application Platform was much better in terms of cost.

I have experience with JBoss Enterprise Application Platform, as we earlier used it, but we moved completely to Tomcat.

I did not use JBoss Enterprise Application Platform with AWS as our main cloud provider, as it is a standalone solution.

We generally put it on premises at the financial institutions.

I am not certain if Red Hat uses AWS as their cloud provider for this product.

We did utilize the JBoss Enterprise Application Platform management console. We were running both in standalone mode as well as the domain mode.

We are more of a modular monolith, so we did not write microservices.

I did not try anything on the cloud, so I am probably not aware of its adaptability between cloud and on-premises deployments.

I do not know much about JBoss Enterprise Application Platform's support or the documentation, as we did not get into that too much.

Our company originally purchased JBoss Enterprise Application Platform through Red Hat partnerships.

The reasons I rate it so highly are that it was simple, lightweight, and the performance was very good. I rate this product a 9 out of 10.

I have an application with JBoss Enterprise Application Platform and a middleware. I used JBoss Enterprise Application Platform for about eight years until 2016. I implemented a ticketing solution and middleware application to connect several databases and several languages, creating an omnichannel experience. I have two kinds of implementations in the commercial area, including ticketing and e-commerce with the same middleware, and I used it for bank financials. One bank in Guayaquil used my middleware.

The best feature for JBoss Enterprise Application Platform for me is high availability, and it is very strong. It is strong because it supports many concurrencies.

I lost one opportunity for licensing to a bank that was implementing on-premises. It was too expensive to license JBoss Enterprise Application Platform for each process. The customer needed to implement on a server with 32 processes, and the price from a local provider was approximately $64,000. Because they are a bank, they need local support, not international support. For that reason, it was too expensive for them, and we were discarded and could not implement the solution.

I used JBoss Enterprise Application Platform for about eight years until 2016.

I do not have any problems with this deployment.

Because the bank needed local support rather than international support, it was too expensive for them, and we were discarded.

I offered implementing the same services in Microsoft IIS, but they needed several months to develop the new solution, and they did not have time for that developer.

JBoss Enterprise Application Platform is easy to implement.

The customer needed to implement on a server with 32 processes, and the price from a local provider was approximately $64,000.

I offered implementing the same services in Microsoft IIS, but they needed several months to develop the new solution, and they did not have time for that developer.

I use JBoss Enterprise Application Platform management both through the management interface and through command line. I use JBoss Enterprise Application Platform for deployment in Microsoft servers, and in Linux and Oracle Linux. I am trying it in my own cloud and have deployed JBoss Enterprise Application Platform on Oracle Cloud to implement it in the cloud, which is very good. My overall rating for this solution is ten out of ten.