These are chat archives for DevrexLabs/OrigoDB

7th
Nov 2016
Alan Hemmings
@goblinfactory
Nov 07 2016 02:22
Hi Robert, there's this one phrase I dont quite understand in the documentation, describing the RoyalFoodTaster, If a command fails, the taster is discarded and replaced with a clone of the real model, without requiring full restore. More importantly, the real model is readable while the taster is being rebuilt.
if the real model is still readable, (and valid) then why bother with rebuilding?
Robert Friberg
@rofr
Nov 07 2016 06:12
The key here is that you have 2 identical models in memory.
If the royal food taster goes corrupt, you need to create a new one
Alan Hemmings
@goblinfactory
Nov 07 2016 11:33
Ok got it; I had a performance test that appears superficially to contradict this; and my problem was that my test model was wastefully keeping a transaction history in memory that was never being queried. This resulted in a linear growth of model size in memory, resulting in a long clone times. (That's my theory) going to remove the transaction table from memory, ... that can always be recreated by replaying all the messages (wow.. that's incredible! ) ...and that should = a test that proves how it all works. If this works, I'd like to offer it for consideration as sample code for the docs?
so far, it looks like the sample code is thin on 'best practice' examples, or examples that show with tests, why (and when) you'd choose A over B.
Alan Hemmings
@goblinfactory
Nov 07 2016 12:04
working on a small accounts demo.
Robert Friberg
@rofr
Nov 07 2016 13:36
awesome, appreciate the love
Alan Hemmings
@goblinfactory
Nov 07 2016 13:37
are there any open source projects or other samples that I can look at to glean some best practices; I'm quite in the dark and guessing, and writing very rudimentary tests, quite a slow process.
Robert Friberg
@rofr
Nov 07 2016 14:12
source is on github, link is on the about page
Alan Hemmings
@goblinfactory
Nov 07 2016 14:15
ah...fantastic
Harry McIntyre
@mcintyre321
Nov 07 2016 17:28
Is the blog engine.net provider around still? The post I googled is dead
Robert Friberg
@rofr
Nov 07 2016 18:13
eww, we did not maintain that provider. To be honest we learned that blogengine.net is a can of worms we wish we had never opened :)
Harry McIntyre
@mcintyre321
Nov 07 2016 18:16
😁
Robert Friberg
@rofr
Nov 07 2016 18:16
and there was no a great performance benefit compared to the xml provider because blogengine keeps loads it all into ram anyway
And by can of worms I mean the implemenation was messy, lot's of leaky abstractions
But i might be able to dig it out for you if you're interested in archaelogy :)
Harry McIntyre
@mcintyre321
Nov 07 2016 18:27
No, don't worry!
I do enough archaeology in the day job