Oskar Gewalli's blog articles

0
comment
on 3/3/2015 12:38 PM
Trying out OrigoDb, I found it interresting to try out a more raw file store approach and NEvent Store. Why the connection Event Sourcing and In memory databse? Mostly because I tried out OrigoDb first. In memory database feels like a nice fit for Event Sourcing (since the log that can restore the database can be persisted in an append only manner). Many of us have heard or read Martin Fowlers Event Sourcing. He mentions in memory databases in the article as well. OrigoDb is a bit easier to setup compare[...]
>> Read the full article
.
0
comment
on 3/3/2015 12:38 PM
Trying out OrigoDb, I found it interresting to try out a more raw file store approach and NEvent Store. Why the connection Event Sourcing and In memory databse? Mostly because I tried out OrigoDb first. In memory database feels like a nice fit for Event Sourcing (since the log that can restore the database can be persisted in an append only manner). Many of us have heard or read Martin Fowlers Event Sourcing. He mentions in memory databases in the article as well. OrigoDb is a bit easier to setup compare[...]
>> Read the full article
.
0
comment
on 2/23/2015 1:50 PM
Turns out that svcutils does not report all the errors when running in visual studio. Some of the errors are reported (perhaps by the gui surrounding it), but not all. This makes it confusing when the tool fails for some reason.
>> Read the full article
.
0
comment
on 2/22/2015 3:30 PM
Dijkstra wrote the following. I agree with his reasoning. However, goto is useful in certain lower level domains. The difficulty of reading code with goto statements is that it’s hard to follow the program flow. The reasoning can also be applied to programming where you do not use goto. Consider the following code: someMethod(){ // some state label 1: doStuff(); goto end; label 2: if (condition){ goto 1; }else{ doOtherStuff(); goto end; } label 3: doSom[...]
>> Read the full article
.
0
comment
on 2/22/2015 3:30 PM
Dijkstra wrote the following. I agree with his reasoning. However, goto is useful in certain lower level domains. The difficulty of reading code with goto statements is that it’s hard to follow the program flow. The reasoning can also be applied to programming where you do not use goto. Consider the following code: someMethod(){ // some state label 1: doStuff(); goto end; label 2: if (condition){ goto 1; }else{ doOtherStuff(); goto end; } label 3: doSom[...]
>> Read the full article
.
IntelliFactory Offices Copyright (c) 2011-2012 IntelliFactory. All rights reserved.
Home | Products | Consulting | Trainings | Blogs | Jobs | Contact Us | Terms of Use | Privacy Policy | Cookie Policy
Built with WebSharper