Comments on: How we got rid of the database–part 6 http://lostechies.com/gabrielschenker/2012/06/30/how-we-got-rid-of-the-databasepart-6/ Blog about architectural patterns, best practices, coding principles and techniques Tue, 02 Apr 2013 00:12:00 +0000 hourly 1 http://wordpress.org/?v=3.4.2 By: Bono http://lostechies.com/gabrielschenker/2012/06/30/how-we-got-rid-of-the-databasepart-6/#comment-527 Bono Thu, 09 Aug 2012 23:58:00 +0000 http://lostechies.com/gabrielschenker/2012/06/30/how-we-got-rid-of-the-databasepart-6/#comment-527 Did I miss the follow up post? Did I miss the follow up post?

]]> By: C Granwehr http://lostechies.com/gabrielschenker/2012/06/30/how-we-got-rid-of-the-databasepart-6/#comment-526 C Granwehr Thu, 09 Aug 2012 08:23:00 +0000 http://lostechies.com/gabrielschenker/2012/06/30/how-we-got-rid-of-the-databasepart-6/#comment-526 Hello Gabriel,  thanks for the so far great introduction into CQRS an ES. After a summerday outside in the garden, watching Greg Young's  long video, your posts were very refreshing. I mostly appreciated the sample code you provided. Debugging working code helps a dummy like me a lot to  understand what your're talking about. Please also integrate this and further posts into your solution (and don't forget to spend your free time without a computer) Liebi Grües us de Schwyz von mir und dä Alex. Hello Gabriel,  thanks for the so far great introduction into CQRS an ES. After a summerday outside in the garden, watching Greg Young’s  long video, your posts were very refreshing. I mostly appreciated the sample code you provided. Debugging working code helps a dummy like me a lot to  understand what your’re talking about. Please also integrate this and further posts into your solution (and don’t forget to spend your free time without a computer)

Liebi Grües us de Schwyz von mir und dä Alex.

]]> By: Anonymous http://lostechies.com/gabrielschenker/2012/06/30/how-we-got-rid-of-the-databasepart-6/#comment-525 Anonymous Sat, 21 Jul 2012 10:40:00 +0000 http://lostechies.com/gabrielschenker/2012/06/30/how-we-got-rid-of-the-databasepart-6/#comment-525 Sorry for the delay, but I was just too busy lately. But the next post is nearly ready to be posted. Thus stay tuned :) Sorry for the delay, but I was just too busy lately. But the next post is nearly ready to be posted. Thus stay tuned :)

]]> By: Jiggaboo http://lostechies.com/gabrielschenker/2012/06/30/how-we-got-rid-of-the-databasepart-6/#comment-524 Jiggaboo Sat, 21 Jul 2012 09:06:00 +0000 http://lostechies.com/gabrielschenker/2012/06/30/how-we-got-rid-of-the-databasepart-6/#comment-524 Aaaaa. I 've read all 6 posts in 30 minutes and there is no next post and I have to wait (don't know how long) for post no 7. That's why I prefer books. Aaaaa. I ‘ve read all 6 posts in 30 minutes and there is no next post and I have to wait (don’t know how long) for post no 7. That’s why I prefer books.

]]> By: Dominic Delmolino http://lostechies.com/gabrielschenker/2012/06/30/how-we-got-rid-of-the-databasepart-6/#comment-519 Dominic Delmolino Thu, 05 Jul 2012 17:47:00 +0000 http://lostechies.com/gabrielschenker/2012/06/30/how-we-got-rid-of-the-databasepart-6/#comment-519 Looking forward to that post -- so far nothing I've read in this series explains why you needed to get rid of the database. You still have a database, you just call it a file store. Sounds like you *HAVE* gotten rid of the need for the application to be bound to a data model ala an ORM, which does sound good. Looking forward to that post — so far nothing I’ve read in this series explains why you needed to get rid of the database. You still have a database, you just call it a file store. Sounds like you *HAVE* gotten rid of the need for the application to be bound to a data model ala an ORM, which does sound good.

]]> By: Rinat Abdullin http://lostechies.com/gabrielschenker/2012/06/30/how-we-got-rid-of-the-databasepart-6/#comment-517 Rinat Abdullin Thu, 05 Jul 2012 02:17:00 +0000 http://lostechies.com/gabrielschenker/2012/06/30/how-we-got-rid-of-the-databasepart-6/#comment-517 @google-90a2a7eb05eb0368cb8169f319917d22:disqus having run ES-based for years in various environments (e.g. mixture of local servers and cloud deployments), I must admit that file-level problems are extremely rare. Mostly it is caused by the fact that we store SHA1 with each record, while verifying it on each operation.  Second, it is extremely easy to set up continuous and immediate replication to multiple secondary locations off-site, to reduce disk corruption risks. @google-90a2a7eb05eb0368cb8169f319917d22:disqus having run ES-based for years in various environments (e.g. mixture of local servers and cloud deployments), I must admit that file-level problems are extremely rare. Mostly it is caused by the fact that we store SHA1 with each record, while verifying it on each operation. 
Second, it is extremely easy to set up continuous and immediate replication to multiple secondary locations off-site, to reduce disk corruption risks.

]]> By: Rinat Abdullin http://lostechies.com/gabrielschenker/2012/06/30/how-we-got-rid-of-the-databasepart-6/#comment-516 Rinat Abdullin Thu, 05 Jul 2012 02:14:00 +0000 http://lostechies.com/gabrielschenker/2012/06/30/how-we-got-rid-of-the-databasepart-6/#comment-516 @google-90a2a7eb05eb0368cb8169f319917d22:disqus , in the case of thorough event sourcing, the simplest approach to versioning is to simply create a new event (_v2) with additional field. More complex scenarios involve, for example, use of Protocol Buffers (with their native ability to handle changes in serialization contracts) and use of in-memory upgraders to make sure that such events apply to the entire event history. Fortunately, when your aggregates are designed using DDD approach, events do not change that often. @google-90a2a7eb05eb0368cb8169f319917d22:disqus , in the case of thorough event sourcing, the simplest approach to versioning is to simply create a new event (_v2) with additional field. More complex scenarios involve, for example, use of Protocol Buffers (with their native ability to handle changes in serialization contracts) and use of in-memory upgraders to make sure that such events apply to the entire event history.
Fortunately, when your aggregates are designed using DDD approach, events do not change that often.

]]> By: Anonymous http://lostechies.com/gabrielschenker/2012/06/30/how-we-got-rid-of-the-databasepart-6/#comment-514 Anonymous Wed, 04 Jul 2012 18:42:00 +0000 http://lostechies.com/gabrielschenker/2012/06/30/how-we-got-rid-of-the-databasepart-6/#comment-514  I see, I have to write another blog post about why we do not use a database. A lot of readers do not seem to completely understand our motivations... Just as a short note: we do not trade in "the devil with the belzebub".  I see, I have to write another blog post about why we do not use a database. A lot of readers do not seem to completely understand our motivations…
Just as a short note: we do not trade in “the devil with the belzebub”.

]]> By: Etienne Tremblay http://lostechies.com/gabrielschenker/2012/06/30/how-we-got-rid-of-the-databasepart-6/#comment-511 Etienne Tremblay Tue, 03 Jul 2012 20:15:00 +0000 http://lostechies.com/gabrielschenker/2012/06/30/how-we-got-rid-of-the-databasepart-6/#comment-511 But I find this serie of post very interesting. But I find this serie of post very interesting.

]]> By: Etienne Tremblay http://lostechies.com/gabrielschenker/2012/06/30/how-we-got-rid-of-the-databasepart-6/#comment-510 Etienne Tremblay Tue, 03 Jul 2012 20:14:00 +0000 http://lostechies.com/gabrielschenker/2012/06/30/how-we-got-rid-of-the-databasepart-6/#comment-510 You got rid of the database, but switched it for more low level serialization file problems.  Plus you have to do the tooling to diagnose problems in your files. You got rid of the database, but switched it for more low level serialization file problems.  Plus you have to do the tooling to diagnose problems in your files.

]]>