The requirement is to cache a large number (from 100,000 to 1,000,000) of small objects and control the expiration of individual objects based on future events. There is no time component for expiration.
The cache should be accessible across multiple application servers (SpringSource dm Server) and ideally should be distributed and self-contained for errors.
I consider Terracotta as a possible solution. Is this a good way to go down? Is there a better one?
We use Terracotta and we are very pleased with this. Its distributed Evictors cached caches were a great solution to our problems.
I think the best option for you is JBoss Infinispan ( http://www.jboss.org/infinispan ). The cache is very stupid, easy to install, supports replication, eviction, persistence, among many other things. More importantly, the cache runs on your application server. You can also access the cache using REST, and there are abstractions for connecting Hibernate to it.
( ) . , memcached , . .
Redis, , , . , Redis (, , ...)
Memcached? : memcached . , , , , API- Java: Danga Spy.
, memcached , - . , , , 30 . YMMV.
Source: https://habr.com/ru/post/1718062/More articles:How to create ctags file for docset? (For vim) - vimTransactions from TransactionScope to Sql Compact Edition 3.5 - sql-server-ceHow can I verify my SSL-required ASP.NET MVC website in Visual Studio? - debuggingParse wiki markup using state machine - javaИзменение расположения символа валюты в System.Globalization.NumberFormatInfo - c#Equivalent to the “defined” in Mathematica - wolfram-mathematicaCan SqlServer be configured to not execute stored procs represented as strings? - securityServerside Solution to Convert SWF File to VIDEO File - flashT-SQL: convert datatime2 to datetime for all datetime2 columns - sqlMaximum Reference Range Intersection (in T-SQL) - algorithmAll Articles