4 ms·
> You may find a a bit more what's behind the demo... That only says "the engine is a Java-based proprietary solution which was about 20x faster than comparabl
by tyingq 3y ago
> You may find a a bit more what's behind the demo...
That only says "the engine is a Java-based proprietary solution which was about 20x faster than comparable implementations in Coherence, Ignite or Hazelcast. (Yes, we tested it.)".
So, comparable to those. Some sort of Java friendly in-memory cache. Perhaps, for this specific kind of data (dates/location/room-type/price/availability), you've figured out an optimal storage/retrieval layout that's fast. That seems plausible. What doesn't seem plausible is that your cache is generally 20x faster than every other cache in the space.
- mgl 3y agoThe combination of storage/retrieval/calculation, executed close to the actual data, is what gives 20x advantage. CPU cache is hard-to-believe fast, see: https://stratoflow.com/latency-numbers-every-java-developer-should-know/ https://stratoflow.com/latency-numbers-every-java-developer-...