Sorry to be pedantic. Thats the example which confused me most. That says a async profile is setup .
" Spring Data JPA Repository is used to access the database. The 'async' command line argument enables the 'async' Spring profile which enables the asynchronous behavior in ProductDBWriter." What I am confused is , we need to set up event queues etc for backup, we can make them persistable ensuring no data loss, where are those done? Regards On Sat, Dec 10, 2016 at 9:04 PM, Nilkanth Patel <[email protected]> wrote: > Have a look at following if that helps! > > https://github.com/spring-projects/spring-gemfire-examples > > Nilkanth Patel. > > On Sat, Dec 10, 2016 at 7:24 PM, Amit Pandey <[email protected]> > wrote: > >> Thanks I understood this. >> >> I want to know how to do this with Spring Data geode? >> >> On Sat, Dec 10, 2016 at 6:24 PM, Avinash Dongre <[email protected]> >> wrote: >> >>> This should help. >>> >>> http://geode.apache.org/docs/guide/developing/events/impleme >>> nting_write_behind_event_handler.html >>> >>> Thanks >>> Avinash >>> >>> >>> On Sat, Dec 10, 2016 at 4:22 PM, Amit Pandey <[email protected]> >>> wrote: >>> >>>> Hey Guys can anyone please provide a link? >>>> >>>> On Fri, Dec 9, 2016 at 8:24 PM, Amit Pandey <[email protected]> >>>> wrote: >>>> >>>>> Hi Guys, >>>>> >>>>> Is there any geode example of write behind with Spring Gemfire or even >>>>> without it using reliable event queue (which persists to disk ) ? >>>>> >>>>> Looking at this example what config changes will enable write behind >>>>> keeping write order and not write orders with a reliable event queue. >>>>> >>>>> Regards >>>>> >>>>> >>>>> >>>> >>> >> >
