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
RabbitMQ
Score 9.1 out of 10
N/A
RabbitMQ, an open source message broker, is part of Pivotal Software, a VMware company acquired in 2019, and supports message queue, multiple messaging protocols, and more.
RabbitMQ is available open source, however VMware also offers a range of commercial services for RabbitMQ; these are available as part of the Pivotal App Suite.
N/A
Pricing
Oracle WebLogic Server
RabbitMQ
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
Oracle WebLogic Server
RabbitMQ
Free Trial
No
No
Free/Freemium Version
No
No
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
RabbitMQ
Considered Both Products
Oracle WebLogic Server
Verified User
Professional
Chose Oracle WebLogic Server
Apache Tomcat is used by the group of developers in our organization but the major student ERP production systems do run on WebLogic due to its feature-rich nature and stability. Although the cost is considered a hindrance to its wider use.
If you need to have complex options in place you can count on Weblogic to be a robust Applicational Server you can rely on. But you would need to keep an eye on maintaining the framework updated quite frequently to avoid security breaches and subsequent severe situations. If you don't have other infrastructure for test purposes, I wouldn't advise you on having devs and QA installing this heavy application in their local machines, there are other lightweight solutions that would be a better fit for that.
It is highly recommended that if you have microservices architecture and if you want to solve 2 phase commit issue, you should use RabbitMQ for communication between microservices. It is a quick and reliable mode of communication between microservices. It is also helpful if you want to implement a job and worker mechanism. You can push the jobs into RabbitMQ and that will be sent to the consumer. It is highly reliable so you won't miss any jobs and you can also implement a retry of jobs with the dead letter queue feature. It will be also helpful in time-consuming API. You can put time-consuming items into a queue so they will be processed later and your API will be quick.
The brand relation between Java and WebLogic Application Server usually provides a quicker access to programming features and their availability for the applications deployed.
The access to centralized configuration both from console and command line WLST eases the implementation of changes major or not in an organized and expedite way.
The maturity of the product is also visible in the available tools provided by the product itself, for both monitoring of resources and alerting for availability and thresholds
What RabbitMQ does well is what it's advertised to do. It is good at providing lots of high volume, high availability queue. We've seen it handle upwards of 10 million messages in its queues, spread out over 200 queues before its publish/consume rates dipped. So yeah, it can definitely handle a lot of messages and a lot of queues. Depending on the size of the machine RabbitMQ is running on, I'm sure it can handle more.
Decent number of plugins! Want a plugin that gives you an interface to view all the queues and see their publish/consume rates? Yes, there's one for that. Want a plugin to "shovel" messages from one queue to another in an emergency? Check. Want a plugin that does extra logging for all the messages received? Got you covered!
Lots of configuration possibilities. We've tuned over 100 settings over the past year to get the performance and reliability just right. This could be a downside though--it's pretty confusing and some settings were hard to understand.
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
It breaks communication if we don't acknowledge early. In some cases our work items are time consuming that will take a time and in that scenario we are getting errors that RabbitMQ broke the channel. It will be good if RabbitMQ provides two acknowledgements, one is for that it has been received at client side and second ack is client is completed the processing part.
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.
RabbitMQ is very easy to configure for all supported languages (Python, Java, etc.). I have personally used it on Raspberry Pi devices via a Flask Python API as well as in Java applications. I was able to learn it quickly and now have full mastery of it. I highly recommend it for any IoT project.
I gave it a 10 but we do not have a support contract with any company for RabbitMQ so there is no official support in that regard. However, there is a community and questions asked on StackOverflow or any other major question and answer site will usually get a response.
I believe the Oracle WebLogic Suite is probably a better all encompassing suite of development tools for the IT department. [It] is probably a bit more expensive than other competitors like Apache Tomcat or NGINX, but is worth the investment if you consider the savings from time to get code into production.
RabbitMQ has a few advantages over Azure Service Bus 1) RMQ handles substantially larger files - ASB tops out at 100MB, we use RabbitMQfor files over 200MB 2) RabbitMQ can be easily setup on prem - Azure Service Bus is cloud only 3) RabbitMQ exchanges are easier to configure over ASB subscriptions ASB has a few advantages too 1) Cloud based - just a few mouse clicks and you're up and running
WebLogic Application Server definitely had a positive ROI since all the applications are deployed on a single platform and making maintenance extremely cost effective.
Since all major cloud vendors support and maintain WebLogic, it gives us an opportunity to explore possibilities to move the organizational infrastructure on to the cloud without too much effort.
Positive: we don't need to keep way too many backend machines around to deal with bursts because RabbitMQ can absorb and buffer bursts long enough to let an understaffed set of backend services to catch up on processing. Hard to put a number to it but we probably save $5k a month having fewer machines around.
Negative: we've got many angry customers due to queues suddenly disappearing and dropping our messages when we try to publish to them afterward. Ideally, RabbitMQ should warn the user when queues expire due to inactivity but it doesn't, and due to our own bugs we've lost a lot of customer data as a result.
Positive: makes decoupling the web and API services from the deeper backend services easier by providing queues as an interface. This allowed us to split up our teams and have them develop independently of each other, speeding up software development.
