IBM Cloud Code Engine is a fully managed, serverless platform that unifies the deployment of containers and applications including web apps, microservices, event-driven functions, or batch jobs. This serverless compute service aims to remove the burden of building, deploying, and managing workloads in Kubernetes so users can focus on writing code and not on the infrastructure that is needed to host it. With IBM Cloud Code Engine users can run any workload…
N/A
IBM WebSphere Hybrid Edition
Score 7.4 out of 10
N/A
WebSphere Hybrid Edition from IBM is a collection of WebSphere application runtimes and modernization tools that provides support for on-premise and major public cloud deployments, in virtual machines, containers and Kubernetes. The user can choose any WebSphere edition and deploy Liberty and application modernization tools to help move to a cloud-native architecture, modernize existing applications and support an existing WebSphere estate.
$88.50
per month
Splunk Observability Cloud
Score 8.4 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.
It would be a good solution for running serverless applications. Because infrastructure setup and maintenance expenses can be avoided, the investment will pay for itself. The time to value is short, allowing IT to respond to business demands quickly. It aided us in customizing security as well as operating a personal project using to autoscale up and down approach. Also, because there isn't much hassle, items can be pushed into production as soon as possible. Simply push a container, create an application, and you're ready to go. But, It is less suited when you have a static machine or need to keep data in some way and do not want to utilize network storage or a database.
IBM WebSphere Hybrid edition is well-suited for the development and deployment of large enterprise-level applications such as Electronic Health Records that are used in our organization. IBM WebSphere is appropriate for organizations that require strong security and compliance as it provides a high level of security and compliance features. This works well with organizations that are subject to strict regulatory requirements, such as hospitals.
Its great if you need real-time visibility across complex or regulated environments. Also strong for hybrid or multi-cloud setups where uptime, observability and fast IR are required. It’s probably overkill for smaller teams or environments that don’t have constant changes or compliance reporting needs. It's expensive and has a steep learning curve. Also, in my opinion, do not get yourself into a consumption based model. Costs can certainly get out of control quickly.
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 pricing structure is complicated, and the servers are expensive. I really think they should offer better pricing options and support for more languages
sometimes the servers go down, and they take too long to respond to support tickets
uploading documents is slow since I have to do it one by one, making the process much longer than it should be
Ease of use in terms of deployment, give simple interface to do simple stuff like Tomcat, JBoss or GlassFish.
Takes long time to start the server.
The Liferay wars need to be decorated and then deployed. Perhaps we could simplify that.
Some of the concepts are good for complexity that WAS can handle but could be simplified and better documented, like concepts of well and profile, context, etc.
A Liferay war file created using Liferay Developer studio runs fine in Tomcat, however that may not run in WAS 7.x because it needs to be decorated. I had one war for a Liferay portlet with a simple cron job, and had hard time running to WAS server. It was running on the latest free download done on my friends m/c. Other times I have seen that there are issues running a war file that runs on Tomcat but runs on WAS after lot of customization for WAS.
The corporations like this however, the product may need better vibrant community of users where issues can be discussed.
You can use table-like functionality to generate dashboards, but these queries are heavy on the system.
It could be easier to give insight into what type of line parsing is used for specific documents in a company-managed environment and/or show ways to gain the insights needed.
I would like to see ways to anonymize specific data for shared reports without pre-formatting this in a dashboard on which reports could be based.
Mostly we will be renewing unless the strategic direction changes drastically or there are other complelling external circumstances. We've been on a multi year project to modernize our legacy applications and that effort will continue for the foreseeable future.
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
Consumers can purchase individual components as well as unlocking new bundles with special features and services including the extensive data management governance capabilities of the Automation range. Kubernetes containerizing for effective service implementation and an agile, flexible multi-cloud data program help both utilization expansion and deployment to be improved by this architecture.
WebSphere Application Server is used across our organization. Most projects use this for Java products and applications. Being robust and scalable makes it even more usable. We love using WebSphere Application Server due to its configuration management ability made simple and vast across all java related parameters. It is dependent on the features and upgrades and IBM releases some great upgrades to WebSphere Application Server.
When there is an issue, it’s a win if one can easily identify the root cause. To do the same, it should allow the user to dig deep with multiple data points and compare the data and identify the anomaly. In this use case, it’s good to drive from Splunk 011y.
IBM was quick to respond when we had an issue with our specific infrastructure. We raised a PMR, which they picked up quickly and updated us about every step of the way. We had an appropriate fix for quite a business critical issue within a fortnight, which was impressive!
What impresses me most about IBM Cloud Code Engine is the container workload management capability and the Cloud services and dataflow monitoring functionalities. Data security and network security control via IBM Cloud Code Engine is quite excellent and very responsive data integration functions and the first deployment is not very technical.
Cleo Integration Clould has many bells and whistles; however, when we added more maps and trading partners, it really slowed down. We found that the Cleo support was very slow to respond and there was a language barrier. IBM Websphere had better customer support and its processing was much faster than Cleo Integration Cloud
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 of servers and agents residing together within a single data centre, but modern apps are no longer like this.
Continuous uptime of the business applications we manage
It's now much simpler for me to build and deploy cloud-native applications.
Because it can offload for me management and maintenance of the application server to IBM I can focus on the development, deployment and testing of the applications which is more important
