Hi guys, We're currently on the verge of refactoring a traditional CRUD based application into a reactive one. We're planning to apply event sourcing with Akka Persitence in order to put in practice CQRS/ES principles. In general terms, we know how to apply this principles when it comes to solving typical business use cases, i.e., adding a new client, managing user accounts, and so on. But, we're not sure whether we should apply this principles and Akka Persistence when it comes to dealing with time series data.
For example, suppose that we need to deal with meteorological data which is captured every hour in the form of batches. Every batch contains data in 10-second intervals. Is event sourcing and Akka Persistence also suitable to solve this kind of scenarios?. How would you model the events?. Would every piece of data be an event or it would be every batch?. Thanks in advance for your thoughts and ideas. Regards, Juanjo. -- >>>>>>>>>> Read the docs: http://akka.io/docs/ >>>>>>>>>> Check the FAQ: >>>>>>>>>> http://doc.akka.io/docs/akka/current/additional/faq.html >>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user --- You received this message because you are subscribed to the Google Groups "Akka User List" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
