"Oracle WebLogic Server: A Powerhouse for Java EE apps, But Not for Everyone"
Use Cases and Deployment Scope
We use Oracle WebLogic Server as our application server for a Java Enterprise application. We run up to 24 JVMs tu support our user base, along with JMS servers to handle asynchronous messaging queues. The application itself is to process Fraud and Disputes claims, as well as Account take over/Unauthorized account access.
Pros
- Oracle WebLogic Server JMS has been great for us to handle asynchronous message processing.
- Oracle WebLogic Server console has also been great as it makes it easier to manage all our application.
- The clustering capabilities also makes it easier to manage deployments across nodes and support for load balancing
- Lastly, the full Java EE support has been great, we've been able to install library to extend our applications integration capabilities.
Cons
- Debugging issues has been difficult sometimes, the documentation is too dense and finding the the root cause for an specific issue takes time.
- The Oracle WebLogic Server console UI feels old and gives a sense of lack of innovation even though it provides so much functionality.
- I'm not sure if Oracle WebLogic Server supports more modern frameworks, but it feels more like a Java EE specific, maybe there's an opportunity there to appeal to newer application platforms
Return on Investment
- It made it easy to handle over a 100 of deployments across multiple nodes every quarter.
- It was easy to scale up our application to 36 nodes as the volume of transactions increased over the years.
- Helped us achieve 99.999 availability for our users.
Usability
Alternatives Considered
IBM WebSphere Hybrid Edition
Other Software Used
PostgreSQL, Snowflake, Pega Platform




