DB Connection VS REST Connection
Dear All,
Can you please tell us that Pega Connection with PEGADATA (Pega database) is efficient or connection of Pega with Gridgain with a REST will be efficient .
PS:
- Gridgain: Is a external system or a Cache. (Uses Non Relational Database)
- PEGADATA: Is a relational Database.
- We are using Pega Marketing on top of Pega.
Keeping in mind that we have to do transaction with a huge amount of data say 60 Million .
we are on websphere
We got some POC at our end and found out Gridgain over REST is much much more faster than Pega Db.
Reason :
1. Gridgain follows Non relational DB model.
2. Gridgain doesnot maintain Logs
3. Gridgain don't bother about Locks
4. There is no I/O Operation.
5. JVM Heap is any day anytime faster than JDBC.
6. GG is uses Cache data, which may not be real time but extremly fast as they have In-Memory architecture.
Also if the GridGain is configured in the AppServer inside the Organization then only it will act faster. And Our GridGain will be inside the Organization Network where Pega is also Installed. If Not PegaDB wins as there comes the following : As there will be additional layers of Firewall and Routers and other N/W related latency .
Which application server are you on? The answer to your question will be specific the the connection pooling implementations in WebSphere, Tomcat, JBoss, etc. Pega uses GridGain in its DSM product.