Thanks to Terracotta, the BookRepository will be actually created for the first time, and then always reused, even if we shutdown our application and restart: the bookRepository persisted/distributed state will be always there.
Well, this is IMHO an anti-pattern.
While it is true that Terracotta makes easy to access repositories from entities, it is IMO wrong because coupled to Terracotta itself: if you swap out Terracotta, that static variable will be always reset at every shutdown/restart, as you would expect in any Java application, and your data will be gone!
I hope it’s clearer now.
And if someone disagrees, or just thinks I misled the original quote, I’d be more than happy to hear his thoughts.
