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 it and more precisely I am already working on it but I have my own doubts like this post which I want to clarify. Let me give you a small gist, hope I should be able to put my point clearly this time. My query is regarding akka persistence in highly oltp apps backed by no sql db for maintaing events and state. Akka persistence maintains changes to state as stream Of events to system. RDBMS maintains just the state as relational tables. Oltp apps with millions of transaction will create lot of changes to state. Obviously these state changes have be saved as events in akka persistence. If we use akka persistence with no sql for storing events and state, dont you think so disk will take up more space compared to RDBMS? As we have to store events plus state(if required)?Disk space requirement in no sql db will increase further if durability is required. I meant disk usage of akka persistence will grow faster wrt to oltp application? In my post I never referred akka persistence as bullet, hoping you will not feel the same again. -prakhyat m m -- >>>>>>>>>> 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.
