On Fri, Aug 15, 2014 at 5:50 PM, Prakhyat Mallikarjun prakhyat...@gmail.com
wrote:
Hi patrik,
Glad you understood my point.
Thanks for your suggestions and point of view. It will help me.
If old stock of events are removed it will save lot of disk space.
But I am curious,
How taking
Hi Olger,
My design involves maintaining state and also DDD.
Can you be more precise in your below inputs?
Although your story makes me wonder, when you are only interested in current
state another solution maybe a better fit. (Like state storage and pub-sub )
-prakhyat m m
--
Read
Hi Roland,
Thanks.
No doubt I got good responses and points. This discussion has helped me better
understand akka persistence and fill many gaps in my understanding.
-prakhyat m m
--
Read the docs: http://akka.io/docs/
Check the FAQ:
Hi,
Hi Team,
I an working on a solution involving akka persistence and DDD/CQRS. The app
is configured with cassandra journal plugin to source the events.Snapshots
will also be stored in cassandra. Application is designed to have sharded
single writers. These single writers will eventually
Hi Prakhyat,
Grow faster than what? Event sourcing is not a silver bullet. If it does
not fit your use case you should use something else. I don't have the
bandwidth to advice in application specific design question in this open
source forum, but Typesafe offers commercial support.
Regards,
Hi patrik,
Very unkind response...but let me clarify in interest of the discussion.
I am not discussing my application specific use case. It is totally akka
persistence related but taking no sql dbs sizing in picture.
My post is not a critic on akka persistence. Let me clarify I want to use
On Fri, Aug 15, 2014 at 4:08 PM, Prakhyat Mallikarjun prakhyat...@gmail.com
wrote:
Hi patrik,
Very unkind response...but let me clarify in interest of the discussion.
Excuse me. I guess I didn't read your questions literally as questions, but
as negative statements.
I am not discussing
RDBMS maintains just the state as relational tables.
This is false, most RDBMSes maintains transaction logs.
http://en.wikipedia.org/wiki/Transaction_log
On Fri, Aug 15, 2014 at 5:12 PM, Patrik Nordwall patrik.nordw...@gmail.com
wrote:
On Fri, Aug 15, 2014 at 4:08 PM, Prakhyat Mallikarjun
Hi patrik,
Glad you understood my point.
Thanks for your suggestions and point of view. It will help me.
If old stock of events are removed it will save lot of disk space.
But I am curious,
How taking snapshot will get rid of old events? When framework takes snapshots
does it delete old
Hi Prakhyat,
With DDD and CQRS, the state changes storage and publication are key part of
the architecture. When you don't need the DDD part, you could use a persistence
processor that handles the transactions (still possible to do cqrs in that way)
Although your story makes me wonder, when
Hi Prakhyat,
others have already provided good answers, I’d like to add one more point: if
you build an OLTP system for “millions of transactions” then you’ll have to
make a pretty big investment in case of an RDBMS solution just to cover the
license fees; with that kind of money you can buy a
11 matches
Mail list logo
