Oracle WebLogic Server is a unified and extensible platform for developing, deploying and running enterprise applications, such as Java, for on-premises and in the cloud. WebLogic Server offers a scalable implementation of Java Enterprise Edition (EE) and Jakarta EE.
N/A
WildFly
Score 0.0 out of 10
N/A
WildFly, the project formerly known as JBoss AS, is a Jakarta EE 10 Application Server, available for download free and open source under a Creative Commons license, and supported by Red Hat.
N/A
Pricing
Oracle WebLogic Server
WildFly
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
Oracle WebLogic Server
WildFly
Free Trial
No
No
Free/Freemium Version
No
Yes
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
Oracle WebLogic Server
WildFly
Features
Oracle WebLogic Server
WildFly
Application Servers
Comparison of Application Servers features of Product A and Product B
I see Oracle WebLogic Application Server being appropriate when an application needs several different data sources and messaging providers configured and accessible, with a configured level of control of resources (connection pools) and timeouts. It is also advisable to create distributed resources that you can configure as always active to provide more processing power, or as failover for situations of availability in case of disaster recovery, for example. An application where the number of required resources configured is very small and almost non-changeable, and no scalability is required, some other options exist in the market with less cost.
I love that the weblogic dashboard allows you to manage applications and see the status of each application.
Oracle WebLogic Application Server simplifies usage periods in the development and production of business applications.
Oracle WebLogic Server allows me to define various aspects of data source entry, including creating a specific multiple connection to facilitate data entry.
Performance and administration are highlighted in weblogic.
The Admin UI should be further simplified, the UI design was not too user-friendly— too many options and clicks required, difficult for the new beginners to figure out what they are looking for.
The admin server becomes the single failure point, although Oracle suggested some workarounds by setting VIP and VHost, it was not quite easy and straight forward.
Domain replication is hard, requiring a lot of knowledge and scripts efforts.
Admin will hang if the node manager communication encounters some issues for one or some nodes in the domain/cluster.
Not able to kill/terminate the stuck thread, the only way is to restart the managed server (JVM)
Oracle WebLogic Server has so many features that sometimes it's hard to find the right place to setup things, I think the dated user interface does not help with that either. This has a direct impact when deciding to use it as your application server, you'd need to have the right people and invest the time needed to master it. If you're application justifies it then it will definitely be a great choice in the long run.
I wasn't involved in selecting the server we were using but in our team we've made some efforts to improve the local deployment process by trying some other Applicational servers too. Apache Tomcat was a more lightweight solution for sure, and it coped well with our applications needs, configuration and performance wise. Despite that, since we didn't got clearance to change that into our local servers, we kept using Weblogic to guarantee compliance between the testing environments and production.
