I understand your point. :) I think the api encourage to serialize the whole PersistentRepr, as the ddvore mongo plugin does. But I also clearly understand that's a plugin author choice and not yours. And using a plugin mechanism is a great choice, no one want to be coupled to specific database and/or data representation.
I'll investigate to write a plugin. And big THANKS for the TCK. Currently I'm prototyping, so the database choice is not definitive, but I go for mongo. (one of the reason is that good GUI tooling is required to allow less technical people to "see" very quickly what happened in case of "bad" business state) Yes your answers help. Thank you. Le mardi 5 août 2014 12:54:56 UTC+2, Konrad Malawski a écrit : > > By the way, implementing storage plugins is not so hard :-) > Take a look at the docs: > http://doc.akka.io/docs/akka/snapshot/scala/persistence.html#storage-plugins > (I'm linking to snapshot here because in in 2.3.5 (coming soon) > persistence includes an persistence plugin TCK – so you can verify if your > plugin really works with this out of the box set of tests :-)) > > > On Tue, Aug 5, 2014 at 12:51 PM, Konrad Malawski <[email protected] > <javascript:>> wrote: > >> Hi Yann, >> since we provide user implementable Journal APIs to which we send >> PersistentRepr we (as in Akka) don't really have control over the format of >> how a journal plugin will decide to store this data. >> This is by design, since we want to be de-coupled from any database >> specifics in the APIs. In HBase I store a whole lot of data in the row key, >> an SQL journal would probably utilise separate columns for the >> persistenceId and the sequenceNr etc. >> >> It is up to the journal plugin to decide how the data will be fit into >> the database ("if you're mongo, just slap a json document into the >> collection and it'll work fine" – etc) – which is why my answer here is to >> implement a Journal plugin that would store the data in a way you see fit – >> just setting the serialiser won't be enough since the plugin may still do >> wrapping, and we can't force people to not do so, since perhaps it's >> exactly what they need. >> If your case is strong enough to really need full human readability, >> writing a small plugin shouldn't be to big of a price to pay :-) >> >> Related question: which database are you targeting? >> >> I hope you see my point and this helps in the long run! >> >> -- >> Cheers, >> Konrad 'ktoso' Malawski >> hAkker @ Typesafe >> >> <http://typesafe.com> >> > > > > -- > 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.
