Oracle WebLogic Server vs. TIBCO ActiveSpaces

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

TIBCO ActiveSpaces is useful for storing in memory data which enables fetching data quickly and efficiently. We can make use of TIBCO ActiveSpaces APIs for storing and retrieving data. In our organization, we store user session details in TIBCO ActiveSpaces and this session detail is used for authentication and authorizing user. We have integration TIBCO ActiveSpaces with React UI and TIBCO Business Works.

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

• Like all other IMDG solutions, Tibco ActiveSpaces provides a scalable and distributed cache solution, which is supposed to have high throughput and high availability.
• As it is under the Tibco umbrella, it is seamlessly integrated with other Tibco products.
• It breaks the traditional "local cache" boundary and limitation, instead unifies many "local physical memory" to create one huge "In-Memory Data Grid", and serves the data provider/consumer application logically as one "Memory Cloud."
• A lot of non-frequently updated data can be cached in this IMDG, to allow fast access, which saves the I/O latency caused by many traditional file system-backed storage solutions.

Incentivized

• 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

• ActiveSpaces 3.2 is not compatible with the latest version of TIBCO Business Event 5.x. And ActiveSpaces 2.x is not compatible with ActiveSpaces 3.x hence there is a big difference in the BusinessEvents supported version of AS and the latest.
• ActiveSpaces takes more disc space and TIBCO does not offer data compression logic out of the box. Developers need to do extra coding to use java snippets to compress and decompress the payload. Although the data compression gives must better performance and speed to the system.
• The compression and decompression API are not offered by TIBCO out of the box, which is a shame. These are so easy and simple to implement, still TIBCOdoes not provide them as an option out of the box.

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

TIBCO ActiveSpaces is easy to install and integrate with other product suites. It is easy to understand and implement as well. TIBCO ActiveSpaces supports multiple databases for storing the data(we are using Oracle Database). All the master data related to the users is being stored using TIBCO ActiveSpaces which keeps the data in memory and help to retrieve it quickly. It has helped to prevent concurrent login sessions by the same user as session details are stored in TIBCO ActiveSpaces and we override the existing user session with the new session details.

Incentivized

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

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

Actually, we are gradually replacing the Tibco ActiveSpaces with Redis (for caching purpose only) or Hazelcast (for embedded mode and also for in-memory distributed computation purpose + in-memory distributed IPC purpose).

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

• Developers with basic knowledge of TIBCO and general data knowledge can easily design and develop an ActiveSpaces based cached solution. As the ActiveSpaces concepts are very simple and easy to understand.
• Some business areas can predict the high influx of a service usage during a certain period. Business will be highly rewarded if they can identify these business areas and provide a cached solution using TIBCO AS.
• Again, this is not a TIBCO ActiveSpaces only advantage and this is true for any/all caching products.
• Some examples for the previous points are
• a. telecom company pre-loading (eager load) customer's usage for the last month, right before releasing/issuing the bills to the customers.
• b. Airline industry loading the customer's itinerary a week before his travel start date. Hence the last minute scrambling to fetch the customer's itinerary travel plans can be avoided.

Incentivized