High availability when creating "in memory" index without persisting the index into a storage

By "front-ending" he was referring to the option of using Hazelcast as your
memcache layer, and having it use ES for persistence. Hazelcast has a simple
MapStore interface you can implement to read/write objects from ES. Since
you don't need persistence, there is little need for that set up.