Posted: Thu May 07, 2009 10:39 am Post subject: Database node
Centurion
Joined: 10 Oct 2002 Posts: 136 Location: California
Hi,
I have kept away from Database node as far possible. If I need to update a database I put the relevant message to queue and then use JDBC adapter to update database based on message in queue. This provides loosely couple integration with database.
But I am curious to know what is the best practice around this? Would calling database from WMB 6.1 impact Broker perfromance ?
There is always some broker perf impact while using databases since it includes calls over the network (db is mostly remote), processing time at the database end.
But with a well defined database (indexing etc) and a robust infrastructure ensures that the perf impact is really minimal.
IMO, the best practices involves using proper sql isolation levels (like not locking db when not required) if required, proper design of msg flows/esql and foremost a well designed database.
This link though is for V5, it talks about optimizing DB2 for Broker.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum