In my previous company, we relied on third-party APIs from a vendor. Recently, we were tasked with bringing those APIs in-house, reducing dependence on external vendors. We employed a JBoss server to facilitate the transition of these APIs into our existing system.
We used JBoss as our application server on the recommendation of the lead developer. JBoss's compatibility with Java EE, modularity, and support for clustering met the diverse needs of our applications. The management console and developer-friendly features simplify configuration and maintenance. JBoss provided a reliable and efficient runtime environment for our Java-based applications.
Our company uses the solution for enterprise clients in the banking and finance industries. We use different versions of the open source solution depending on client needs.
JBoss is an on-premises solution we use in a banking setting. It is used to manage servers and applications. There are two modes: domain and development. We can monitor and control all types of deployments in JBoss. We have around 20,000 to 30,000 users on the same application and everything is going via the JBoss. We were using JBoss 1.0 when I first installed it, but they've probably included some more security patches in the latest version.
Individual Contributor at a comms service provider with 10,001+ employees
Real User
2021-11-01T10:15:22Z
Nov 1, 2021
JBoss is used for our main applications, it is our core system. All the core systems that we use are on JBoss and we use mod_proxy combined with WildFly to do the load balancing. Additionally, we use automation using Red Hat Ansible Tower, and for a web server, we use Red Hat for the entrance.
Information Technology Consultant at a computer software company with 11-50 employees
Reseller
2021-03-26T20:56:49Z
Mar 26, 2021
I am working on a deal where JBoss is being renewed. It is a legacy version. The use case is around a financial institution that enables banks to do peer-to-peer transactions. Finance is the core business of the companies I'm working with.
The product is basically middleware. What we have is several applications running on JBoss. Basically, it is very old and there we have those services exposed. Our target is to move them to ERPC, or something more modern, like REST or ESPC, or a combination of both. What we currently have here, still, is SOAP services, which is a very old middleware. They also are using it for scheduling some items such as some recurrent procedures. They have a queue manager as well.
What is an application server and what purpose does it serve? As the years go by, technology becomes more and more complex. Applications are certainly no exception to this phenomenon. As a result, as time passes, the evolution of applications could make it difficult for them to be written and maintained by the organizations that use them. This is where application servers come into play. These servers are located at the midpoint of the data-processing network. The network operating...
In my previous company, we relied on third-party APIs from a vendor. Recently, we were tasked with bringing those APIs in-house, reducing dependence on external vendors. We employed a JBoss server to facilitate the transition of these APIs into our existing system.
The use cases include online webshops and any organization doing online business can use JBoss.
We used JBoss as our application server on the recommendation of the lead developer. JBoss's compatibility with Java EE, modularity, and support for clustering met the diverse needs of our applications. The management console and developer-friendly features simplify configuration and maintenance. JBoss provided a reliable and efficient runtime environment for our Java-based applications.
We provide the very basic JBoss setup for the implementation and the setup.
Our primary use case is for web applications.
For our application to deploy, we used to set up different platforms. We are certifying JBoss support as well for the deployment.
I use the platform mainly for presentations and meetings. It is also used to implement web applications.
We use JBoss exclusively for API integration and do not use it for other purposes. Our focus is solely on providing services and configuring ACLs.
Our company uses the solution for enterprise clients in the banking and finance industries. We use different versions of the open source solution depending on client needs.
JBoss is an on-premises solution we use in a banking setting. It is used to manage servers and applications. There are two modes: domain and development. We can monitor and control all types of deployments in JBoss. We have around 20,000 to 30,000 users on the same application and everything is going via the JBoss. We were using JBoss 1.0 when I first installed it, but they've probably included some more security patches in the latest version.
We primarily use the solution for business processes and mostly from the level of approval, within the organization.
JBoss is used for our main applications, it is our core system. All the core systems that we use are on JBoss and we use mod_proxy combined with WildFly to do the load balancing. Additionally, we use automation using Red Hat Ansible Tower, and for a web server, we use Red Hat for the entrance.
JBoss is a product that we implement for our clients. It is used as an application server and a web server.
I am working on a deal where JBoss is being renewed. It is a legacy version. The use case is around a financial institution that enables banks to do peer-to-peer transactions. Finance is the core business of the companies I'm working with.
The product is basically middleware. What we have is several applications running on JBoss. Basically, it is very old and there we have those services exposed. Our target is to move them to ERPC, or something more modern, like REST or ESPC, or a combination of both. What we currently have here, still, is SOAP services, which is a very old middleware. They also are using it for scheduling some items such as some recurrent procedures. They have a queue manager as well.