Chapter 9. From the Outside Looking In
In addition to the standard native client access to the cluster, Hazelcast provides a few generic interfaces itself so that our application can be powered by a technology stack that isn't necessarily Java-based and we can still take advantage of some its capabilities:
- Memcache-compatible access to the default map
- RESTful access to map and queue collections
What about the rest of us?
One limitation of Hazelcast is that because it is a Java-based technology, it is mostly focused on supporting applications build around the stack. While we do have some degree of flexibility in that other JVM byte-code-based languages (such as Groovy or Scala) can utilize the standard Java client driver, there is still a rather large ...
Get Getting Started with Hazelcast - Second Edition now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
