Hi Konrad, thanks for your answer. Ok, then. I'll give you some numbers so that you might have a more complete business case. Our application is a multi-tenant SaaS solution. We plan to have around 200 active tenants where every tenant will generate some time series data. One of these time series will have around 10M events per year and tenant. So we'll end up with around 2B (U.S. billions) per year in our database for this kind of data. We'll have some others entities with similar properties and needs. I'm not sure if this is big data but it seems to me.
In terms of storing we have a Cassandra cluster and an in-memory datagrid solution (Hazelcast) to deal with master data and caching capabilities. We also have an Spark cluster for analytics that takes data from Cassandra and run some ETL processes in order to get aggregated data and useful insights. If we finally go with Akka Persistence we're planning to use the akka-persistence-cassandra driver [1] of course. WDYT?. [1] https://github.com/krasserm/akka-persistence-cassandra/ El lunes, 7 de julio de 2014 12:25:04 UTC+2, Konrad Malawski escribió: > > Hi Juan, > Glad to hear you've picked persistence :-) > > My immediate reaction would be to store each data point as an event - that > will make replaying and analysing the data simpler. It also means no need > to think about "oh yeah, we were getting the data in batches, so it's > batches stored in the db". > Having more insights into sizes of these events will influence the design > though. Count wise I understand you're getting 360 events in one batch? > That's not much by itself, but how many of these persistent entities will > you have in your system? > > Related question: which datastore are you looking into using to back your > system? > > > On Mon, Jul 7, 2014 at 12:14 PM, Juan José Vázquez Delgado < > [email protected] <javascript:>> wrote: > >> 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] <javascript:>. >> To post to this group, send email to [email protected] >> <javascript:>. >> Visit this group at http://groups.google.com/group/akka-user. >> For more options, visit https://groups.google.com/d/optout. >> > > > > -- > Cheers, > Konrad 'ktoso' Malawski > hAkker @ Typesafe > > <http://typesafe.com> > -- >>>>>>>>>> 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.
