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
Red Hat JBoss EAP
Score 8.5 out of 10
N/A
N/A
N/A
Splunk Observability Cloud
Score 8.5 out of 10
N/A
Splunk Observability Cloud aims to enable operational agility and better customer experience through real-time AI-driven streaming analytics allowing accurate alerts in seconds. It is designed to shorten MTTD and MTTR by providing real-time visibility into cloud infrastructure and services.
I have only used WebSphere for an evaluation period but I felt it was even harder to learn and it's cost was going to be bigger in the long run. Oracle WebLogic Server was more like the middle ground for what we needed at the time, both in terms of costs and learning curve.
As mentioned earlier we didn't choose Oracle WebLogic Server, but received it as part of the application we bought. After using it for a few years we found it to be a stable product that has a bit of a learning curve compared to Microsoft IIS but is as stable and maybe even …
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 …
Oracle Weblogic Application Server is very robust and has good features and stability. It is a very sought-after tool for deploying many kinds of applications.
Director, eCommerce Analytics and Digital Marketing
Chose Oracle WebLogic Server
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 …
Oracle WebLogic Application Server is a leading server side container. It is far superior than IBM's WebSphere application server, JBOSS or Tomcat server. The easiness of using Oracle's weblogic application server is much user friendly and also it has great support and user …
Oracle Weblogic Application Server gains its reputation from the performance, easy of maintenance, to be compared with the competitor solutions. However, Weblogic is "all-in-on" solution, sometimes it is too fat for some business needs that only requires part of the full …
The main competitor is Wildfly and Websphere. The choice it's all about the bundled cost regarding the chosen OS and Java vendor. All three are almost the same in terms of performance and features. An exceptional alternative from the OSS ecosystem is Payara. Payra has some …
Applications Developer Information Technology Specialist
Chose Oracle WebLogic Server
Oracle WebLogic Application Server is much more stable when compared to opensource application servers like Oracle GlassFish Server or Apache Tomcat. Coming to JBoss Enterprise Application Server, Oracle WebLogic Application Server has better support with most of the cloud …
Apache Tomcat requires a lot of out-of-the-box set-up that is difficult to work with, especially when it comes to production-ready configurations. The only advantage it has over Oracle WLS is that it's free, which is probably why many commercial server products are bundled with …
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.
We are using OBIEE application and when we install an application it is installed automatically with the application. We selected the WebLogic Server for better administration and maintenance of the application. It is very important for us to keep our production application up …
WebSphere is another major contender and they have pitching and are more updated/streamlined. I still prefer WebLogic from an administrator standpoint. Support is much better and there are more options for finding answers to issues or new features.
Red Hat JBoss EAP is good and open source. We chose Oracle WebLogic because we are using Oracle products like Oracle Enterprise Manager and it's very easy to integrate WebLogic with it. Also, for our mission critical applications, we wanted an application server with great …
Compared to the alternatives, Weblogic is on the heavier side and requires more configuration to get it running. Instance startup time is also relatively long, but this could be due to the application size deployed on the server. Licensing cost for WebLogic would also be higher …
WebSphere Application Server is propriety and increases project cost. It is slightly complicated to learn when compared to Jboss EAP. These were the two main reasons why we chose Red Hat JBoss EAP over Websphere Application Server. Also, JBoss EAP is light weight and requires …
We decided to use Red Hat JBoss EAP as it lowers our overall cost, supports all the features that we are looking for including clustering, distributed caching and web services. JBoss EAP is modular and has cloud-ready architecture.
JBoss does practically everything Apache Tomcat and Weblogic does in terms of our requirements, but JBoss is more suited for larger enterprise J2EE apps compared to Tomcat. Boot time is not as quick as Tomcat, but still relatively fast for our deployments. The system can also …
Jboss supports JEE standards and provides features like high availability, clustering, hot deployments, configurable features. you can quickly add or remove needed features and cut jboss footprint and reduce boot time.
it could stack up against this version of Splunk because in this instance of having the cloud option as an available use case it furthermore has more use cases and the options for the data to always be readily available will furthermore allows for analysts to review the data in …
Datadog pushes intom proprietary ecosystem and pricing structure.Compared to self hosted prometheus and grafarna but it gave headache og managing our own monitoring infrastructure at scale.Prometheus is excellent for scraping cluster metrics but it doesnt handle distributed …
I guess scale is the main factor against grafana and ease of use against amazon elasticsearch service and also i have used signoz and ELK Stack also, but stability Splunk Observability Cloud gives is too good and also it comes with high avability and you have to maintain …
We initially chose Splunk Observability Cloud because it promised full-stack visibility and tighter integration. The other tools didn't offer this as part of the core package. Their analytics and real-time dashboards looked strong during the demo but it turned out to a lot …
I selected Splunk Observability Cloud because it focused so much on OTEL standards which will help us in future as OTEL is covering most of the observability standards. And also it has the best Kubernetes observability as I already explained it has several predefined dashboards …
Splunk Observability Cloud stood out for its real-time data ingestion, native OpenTelemetry support, and seamless correlation between metrics, traces, and logs, which gave us faster root cause analysis and better end-to-end visibility compared to Grafana setups that required …
To be honest, Datadog is very similar to Splunk and LogScale to a lesser degree, but it is just as good if you don't need too complex observability. Grafana is still growing and might reach the same level soon.
It's able to quickly detect and resolve issues across the entire spectrum of deployments including on-premises, public cloud, private cloud, hybrid cloud and multicloud
The above applications have their own use cases. Thousand Eyes or Sitescope is used for URL monitoring and Splunk is used for application monitoring. Appdynamics is also used for application monitoring and can monitor the server very well but it lacks when searching in logs …
Splunk is superior in many ways to these solutions when I'm comes to ingesting, storing, manipulating, and using data, but dynatraces automatic agents do make it much easier to use out of the box. Nagios seems much cheaper but does not provide as much functionality as Splunk. …
SQL is a great tool for smaller quick checks. When trying to monitor several different environments, applications, APIs, several thousand devices, connections, and technology, it just doesn't stand up to what you need. Splunk Infrastructure Monitoring has really stood out …
We are having other monitoring tools like AppDynamics, Dynatrace, Datadog and already using their end-user monitoring capability. Most of our customers are looking for agent-free monitoring where they don't want to instrument any agent on their client-side (as it might …
Splunk Infrastructure Monitoring provides far superior options for anybody using a complex hybrid multi-cloud environment and allows both your SOC and NOC to work together on the same data while driving their own insights.
We found other products are still in the old world view …
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.
It's well-suited for being less bulky and is more manageable than other IBM products for Java applications. It's more scalable and provides broader features than others, and is able to load balance with better visibility. The "containers" within are lighter weight and thus don't consume as many resources as Websphere did.
Good for below cases 1. There is a front end and need to correlate data with front end data 2. multiple microservices and need to check the health of each system 3. correlate data from various sources 4. Application performance is a key to be captured 5. application performance is a key metric.
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.
JBoss deployment and configuration is easy and fast. This leads to lower cost and faster deliveries.
Jboss gives you lot of flexibility around performance tuning options to better suite your application needs.
It is modular and cloud ready. This can be installed on-premise and cloud with equal ease.
I specifically love it's integration with mod_cluster. It is a smart httpd based load balancing component that listens to incoming requests on web server using httpd and then intelligently routes the request to Jboss hosts.
The first one is its Kubernetes container monitoring.
I really like this features because as we know how much K8s is vast and to manually monitor each part of the Kubernetes it takes so much time but Splunk Observability Cloud makes it easier. And even once we integrate K8s with Splunk Observability Cloud it gives us some prebuilt dashboards which gives holistic view of our Cluster and its nodes, pods, etc.
The dashbaord feature of Splunk Observability Cloud, it gives us full flexibility to customize our dashboard with a wide range of predefined chart types.
Now it also supports OTEL, which is a plus point for observability. As now everyone is moving towards Otel and in current market there are only few tools who supports OTEL based integrations, Splunk Observability Cloud is one out of them.
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)
An indicator for errors on the navigations pane so that we don't have to go through each tab.
As we go more and more cloud maybe you guys can implement a pay-as-you-use strategy so that small companies using it not frequently can also afford it.
That's it can't think of any and it wont let me skip to next question. Thanks
Good: Stable system with low error rate Easy to use for simple use cases Bad: UI is not very clear for complex usage Mobile view (when logged in from phone) is bad No library for .net
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.
It's quite easy to learn and use. We have transitioned our Red Hat JBoss EAP set up to client team. They had no technical background of managing it but were quick to learn the product.
Overall a great tool to have in your toolbox, It is very intuitive and our entire staff uses the tool. It is easy to use and cost is very reasonable. Splunk also has excellent support team and very easy to work with. Every time we had a challenge, support team was able to help us with the end result.
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.
WebSphere Application Server is propriety and increases project cost. It is slightly complicated to learn when compared to Jboss EAP. These were the two main reasons why we chose Red Hat JBoss EAP over WebSphere Application Server. Also, JBoss EAP is light weight and requires less server resource
To be honest, Datadog is very similar to Splunk and LogScale to a lesser degree, but it is just as good if you don't need too complex observability. Grafana is still growing and might reach the same level soon.