Why do we still need a DB for IS cluster ?

As companies and markets started looking at Terracotta as a Store while it is primarily a In-Memory Engine .
Also, when Terracotta is capable of handing TB data,Should there be DB still be required in future of IS cluster ?
What are the shortfalls of Terracotta in this context and what could go wrong in the Usability pattern ?

Hi Suresh,

DB is still required as the “IS Internal” part is shared between the instances like Scheduler definitions.