Apache Kafka vs. Apache Pulsar vs. Oracle WebLogic Server

Apache Kafka is well-suited for most data-streaming use cases. Amazon Kinesis and Azure EventHubs, unless you have a specific use case where using those cloud PaAS for your data lakes, once set up well, Apache Kafka will take care of everything else in the background. Azure EventHubs, is good for cross-cloud use cases, and Amazon Kinesis - I have no real-world experience. But I believe it is the same.

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.

Incentivized

• Really easy to configure. I've used other message brokers such as RabbitMQ and compared to them, Kafka's configurations are very easy to understand and tweak.
• Very scalable: easily configured to run on multiple nodes allowing for ease of parallelism (assuming your queues/topics don't have to be consumed in the exact same order the messages were delivered)
• Not exactly a feature, but I trust Kafka will be around for at least another decade because active development has continued to be strong and there's a lot of financial backing from Confluent and LinkedIn, and probably many other companies who are using it (which, anecdotally, is many).

Incentivized

• 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

Incentivized

• Sometimes it becomes difficult to monitor our Kafka deployments. We've been able to overcome it largely using AWS MSK, a managed service for Apache Kafka, but a separate monitoring dashboard would have been great.
• Simplify the process for local deployment of Kafka and provide a user interface to get visibility into the different topics and the messages being processed.
• Learning curve around creation of broker and topics could be simplified

• 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

Incentivized

Kafka is quickly becoming core product of the organization, indeed it is replacing older messaging systems. No better alternatives found yet

Incentivized

Apache Kafka is highly recommended to develop loosely coupled, real-time processing applications. Also, Apache Kafka provides property based configuration. Producer, Consumer and broker contain their own separate property file

Incentivized

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.

Incentivized

Oracle WebLogic Application Server is great at security, performance and features.

Incentivized

Support for Apache Kafka (if willing to pay) is available from Confluent that includes the same time that created Kafka at Linkedin so they know this software in and out. Moreover, Apache Kafka is well known and best practices documents and deployment scenarios are easily available for download. For example, from eBay, Linkedin, Uber, and NYTimes.

Incentivized

The Oracle support is not great sometimes. They take a long time and need a lot of data over and over to resolve issues.

Incentivized

I used other messaging/queue solutions that are a lot more basic than Confluent Kafka, as well as another solution that is no longer in the market called Xively, which was bought and "buried" by Google. In comparison, these solutions offer way fewer functionalities and respond to other needs.

Incentivized

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.

Incentivized

• Positive: Get a quick and reliable pub/sub model implemented - data across components flows easily.
• Positive: it's scalable so we can develop small and scale for real-world scenarios
• Negative: it's easy to get into a confusing situation if you are not experienced yet or something strange has happened (rare, but it does). Troubleshooting such situations can take time and effort.

Incentivized

• 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.

Incentivized