Comments on: Exploring Terracotta tim-async – Scalable way to off-load DB updates from App Transaction http://www.ashishpaliwal.com/blog/2010/01/demystifying-terracotta-tim-async-scalable-way-to-off-load-db-updates-from-app-transaction/ From Programmer, For Programmers Tue, 17 Aug 2010 12:04:21 +0000 hourly 1 http://wordpress.org/?v=3.0 By: Caching and Database Offloading - Best of both worlds with Terracotta Darwin Release | Ashish’s Tech Blog http://www.ashishpaliwal.com/blog/2010/01/demystifying-terracotta-tim-async-scalable-way-to-off-load-db-updates-from-app-transaction/comment-page-1/#comment-12744 Caching and Database Offloading - Best of both worlds with Terracotta Darwin Release | Ashish’s Tech Blog Wed, 24 Mar 2010 11:20:56 +0000 http://www.ashishpaliwal.com/blog/?p=373#comment-12744 [...] Write-Behind feature of Ehcache for DB offloading. I will rewrite the code of one my previous post Exploring Terracotta tim-async - Scalable way to off-load DB updates from App Transaction, to use the write-behind [...] [...] Write-Behind feature of Ehcache for DB offloading. I will rewrite the code of one my previous post Exploring Terracotta tim-async – Scalable way to off-load DB updates from App Transaction, to use the write-behind [...]

]]> By: ashish http://www.ashishpaliwal.com/blog/2010/01/demystifying-terracotta-tim-async-scalable-way-to-off-load-db-updates-from-app-transaction/comment-page-1/#comment-11124 ashish Mon, 25 Jan 2010 16:45:49 +0000 http://www.ashishpaliwal.com/blog/?p=373#comment-11124 Well there are multiple ways to achieve this. BTW, the example shown there works across multiple JVM. That's the beauty. And with Terracotta your Threads in different JVM's can coordinate as if they were in same JVM. In the next release write behind is the feature in-built in the product :-) Also, with TC things are a little different with TC, redis saves ur data periodically, but with TC works a little different way. I encourage you to try Terracotta, and see for yourself. Well there are multiple ways to achieve this. BTW, the example shown there works across multiple JVM. That’s the beauty. And with Terracotta your Threads in different JVM’s can coordinate as if they were in same JVM. In the next release write behind is the feature in-built in the product :-)

Also, with TC things are a little different with TC, redis saves ur data periodically, but with TC works a little different way. I encourage you to try Terracotta, and see for yourself.

]]> By: Shantanu Kumar http://www.ashishpaliwal.com/blog/2010/01/demystifying-terracotta-tim-async-scalable-way-to-off-load-db-updates-from-app-transaction/comment-page-1/#comment-11123 Shantanu Kumar Mon, 25 Jan 2010 16:36:32 +0000 http://www.ashishpaliwal.com/blog/?p=373#comment-11123 Why shouldn't I consider using a message queue for write-behind? MQs expose manageability and configuration that can get one up and running very fast. If all I need is in-memory async operations, why not something like redis[1] or an in-memory queue data structure upon which two threads (1. customer-facing write response and 2. DB-facing write-behind operation) operate? [1] http://code.google.com/p/redis/ Why shouldn’t I consider using a message queue for write-behind? MQs expose manageability and configuration that can get one up and running very fast.

If all I need is in-memory async operations, why not something like redis[1] or an in-memory queue data structure upon which two threads (1. customer-facing write response and 2. DB-facing write-behind operation) operate?

[1] http://code.google.com/p/redis/

]]>