Thanks for the comments. However, as I said I have decided that I do want
to use json asa format, so I'm really looking to see who has direct
experience of that.
The serialization format is less orthogonal that you might expect, given
that the database table layouts are all part of the plugin and as far as I
can see, all use blob rather than json format with no obvious way to change
And yes the json-ness does make a difference to me. Without going into
elaborate CQRS "Q" coding, it will enable the developers to find out about
how the system is being used, what sort of messages are being created with
what payloads, through simple sql. My increased data volumes are extremely
unlikely to burden a single server db in the short to medium term.
On Wednesday, September 21, 2016 at 2:58:27 PM UTC+1, Justin du coeur wrote:
> A few general reactions (personally, I'm using Kryo over Cassandra, so I
> can't address the direct questions):
> Keep in mind that json is a relatively bulky serialization format -- it's
> going to take rather more disk space than more typical options like
> In *general*, the serialization format and database are pretty orthogonal
> concerns. It's possible that json might have specific advantages when used
> with a json-native DB like Mongo, but AFAICT the Cassandra driver is the
> most mature in general. Are you planning on using the json-ness in some
> particular way?
> Finally, remember that json doesn't save you from all the complications of
> schema evolution: you're still going to need to think about how you deal
> with missing fields, name changes, and stuff like that. It's probably a
> bit easier than Kryo, but only a bit. Schema evolution is a real bear --
> making sure I can deal with it took most of my effort in getting
> Persistence up and running...
> On Wed, Sep 21, 2016 at 9:16 AM, Tim Pigden <tim.p...@optrak.com
>> and thinking about what we currently do, I've concluded that I'd like to
>> serialize my events as json.
>> The article suggests I should check the list of plugins to see which
>> specifically support json. But I can't find clear indications that any of
>> them do from the respective github pages (apologies if I've missed
>> something). Most seem to want the target database tables to be a BLOB with
>> no option of a native json type.
>> My current database target is Postgres (because we use postgis for
>> mapping and because I need a proper sql database for data warehouse).
>> However, for the event serialization I could certainly contemplate
>> something else if it made the current development path quicker and easier.
>> MongoDB or Cassandra are obvious possible targets.
>> So my question is: is anyone actually using json as a serialization
>> format, and if so
>> a) what database and driver?
>> b) is the database-native json support being used (if any?)
>> c) how much effort was it? I can already serialize everthing to json that
>> needs to go in the persistence journal or snapshots.
>> it's got to be something with active support/interest.
>> >>>>>>>>>> Read the docs: http://akka.io/docs/
>> >>>>>>>>>> Check the FAQ:
>> >>>>>>>>>> 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
>> To post to this group, send email to akka...@googlegroups.com
>> Visit this group at https://groups.google.com/group/akka-user.
>> For more options, visit https://groups.google.com/d/optout.
>>>>>>>>>> Read the docs: http://akka.io/docs/
>>>>>>>>>> Check the FAQ:
>>>>>>>>>> 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 post to this group, send email to firstname.lastname@example.org.
Visit this group at https://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.