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.
Before using TIBCO ActiveSpaces, we were storing all the data in Oracle database and due to large volumes of data response time was more and overall performance had reduced. With the introduction of TIBCO ActiveSpaces, we moved the master data to TIBCO ActiveSpaces for storing …
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).
One biggest advantage of the Tibco ActiveSpaces is it's ease of integration with the TIBCO suite of products. Hence it is more suitable to TIBCO AS in conjunction with the TIBCO suite of products.
All products could offer the same or different level of advantages. For the …
Red Hat JBoss Enterprise Application Platform (JBoss EAP) is well suited for deploying high transaction Java EE based applications. It supports many popular Java EE web-based frameworks such as Spring, Angular JS, jQuery Mobile, and Google Web Toolkit.
TIBCO ActiveSpaces is only suited in the company where Tibco suites have been already used, the license cost is not a concern, it is only required for data caching purposes and only works in the client/server mode for middle-sizes of data. If the expectation is data cache + distributed computation or embedded IMDG is also one requirement or the data cluster needs span multiple data centers, other light-weight OpenSource IMDG solutions should be considered
MOD_CLUSTER integration. JBoss EAP integrates pretty well with mod_cluster. This is an intelligent load balancer especially useful in highly clustered environments.
Supports enterprise-grade features such as high availability clustering, distributed caching, messaging etc.
Supports deployment in on-premise, virtual and hybrid cloud environments.
Jboss CLI is a great tool but we had trouble using it to get values that are displayed on Jboss GUI. It also has limitations parsing the applications.xml files and we had to use a mix of jboss-cli and linux bash commands to automate certain application administrative tasks.
JBoss doesn't really provides performance tuning recommendations. It would have been nice if it could learn from the current demand vs current settings for things like connection pool, server configurations, garbage collection etc.
TIBCO ActiveSpaces Tuple-based data structure is not flexible enough to support customized native data objects.
There is no secondary index option.
Doesn't provide "predicate based In-Grid distributed search and result aggregation."
only can be used as data cache, the node's only contribute memory but can not use the data partition owner node's computation power to apply the distributed computation customized by the user.
Cross data center replication (geographically) is a pain.
Encounter the performance issue when the data volume is huge, even according to the architecture design, linear scaling up should not have that issue.
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.
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
Before using TIBCO ActiveSpaces, we were storing all the data in Oracle Database and due to large volumes of data response time was more and overall performance had reduced. With the introduction of TIBCO ActiveSpaces, we moved the master data to TIBCO ActiveSpaces for storing data which needed frequent access in memory for faster retrieval. This improved the performance significantly and also made managing data easier.
Jboss EAP is easy to deploy and configure. This lead to lower cost and faster delivery.
Even though we have large number of machines running JBoss, we have only two Jboss Administrators. It doesn't requires too much administration and maintenance on daily basis and reduces number of administrators required for large implementations.
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.