@Mahesh,
Thanks for asking.
- Please google it for details or read it on open.sap.com.
- Tibco Analytic product Tibbr / Tableau [Not exactly middleware but part of it]
- Same as 1.
@Mangat:
webMethods heavily rely on RDBMS for its functioning of reporting [unstructured data] and PRT/TN [Structured Data+Unstructured], which force you to run archive, maintain, monitor DB for performance. [I know a few customers who having tough time in maintaining product databases due to size of data in RDBMS]
This audacious thought came after knowing the capabilities of HANA. My thought process is to build / provide a capability to run webMethods on HANA.
If you read the technical reports of webMethods under Empower > Products & Documentation > Technical Reports. RDBMS is a big bottleneck, [Ref: https://empower.softwareag.com/images/Process_Engine_95_Windows_TechnicalReport_tcm121-114537.pdf].
In short: The HQoS tests with small documents (1KB and 10KB) were limited by the database hard disk being overloaded.
For each process instance, all the process-related data (step executions and transitions) had to be stored in the
database. The MQoS tests with small documents (1KB, 10KB, and 50 KB) were limited by the DB server CPU.
Hope I have put my thoughts clearly.
Regarding Terracotta and Apama: They are different products with different purposes.
Thanks,
Rankesh
#webMethods-General#webMethods-Architecture#Integration-Server-and-ESB#webMethods