We are planning to use a database as the system of record beneath Gemfire 7 with write-behind on any creates or updates in our regions (both partitioned and replicated) and read through on cache misses. A further requirement of our datagrid is that every node be identical in terms of custom code and/or gemfire plugins that we have installed to facilitate easy scaling of the grid (for example we want to be able to have a VM gemfire node image that can essentially be copied and spun up on demand for horizontal scaling. We have done this successfully with gemfire datagrids where we have no write-behind requirement).
My question is what is the best way to accomplish write-behind in this scenario? I have looked at the recommended method for write-behind using the AsyncEventListener but this listener has the constraint that it cannot be installed on every node in the grid. Is it possible to use regular cache listeners to perform write-behind provided that we implement an asynchronous method within the listener? What are the advantages to using the AsyncEventListener instead of the regular cache listeners for write-behind?