Clustered Event Sourcing and CQRS with Akka and Java - Hugh McKee

[@jwj410]

Great talk. the example repos are awesome too, thanks

[@joeldsouzax]

Thanks Hugh!! you really helped me in getting a perspective of how simple it is to build CQRS project in AKKA!

[@alexiskylo8916]

Sorry to be off topic but does anybody know a way to get back into an Instagram account? I stupidly forgot the login password. I appreciate any help you can offer me!

[@zanderraylan8518]

@Alexis Kylo instablaster :)

[@alexiskylo8916]

@Zander Raylan thanks so much for your reply. I found the site thru google and im trying it out atm. Takes a while so I will get back to you later with my results.

[@alexiskylo8916]

@Zander Raylan it did the trick and I now got access to my account again. I am so happy:D Thanks so much you saved my account!

[@zanderraylan8518]

@Alexis Kylo Happy to help =)

[@abelgerli]

Event sourcing CQRS are still underappreciated. Actually I have seen projects mixing up the meaning of command and events in the understanding how it's used and what it represents. If you mix them up you get a big mess without defined information flow. So watch out to get in a zen state in your team to see the flow of the data clearly structured. If you start to get questions how the flow from commands to events and the events to different read side stores goes you just have a problem. So it is time to talk to show the simple but powerful architecture. By the way there are people in every job doing it because it's their job and there are people that are just convinced what and how they do things. ;-) Just like his professional but quite attitude about it respect.

[@ВикторМанзар]

Hello there! Could you share the code of presentation?

[@vadimprudnikov9072]

I didn't like the code: lots of if-else, instanceOf, null checks, many things in one class and so on. I consider it like a code I'm supposed to write. If it's true then I don't want to use this.

[@joeldsouzax]

Akka has two types of libraries for this, the one which is best in my opinion is the typed one, in which you specify the actor and bind the type of messages it can receive, so it can take away a lot of instance of keywords out of it. other thing is this is just a demo app, on a normal app, you would be really mindful of the plumbing. so try it out,

[@abelgerli]

Actually Akka was originally written in scala if you use it with pattern matching in scala it gets much clearer. The point with a actor system is also to do multi thread programming in a safe non blocking way. That's way actors are the default way to programm multi threaded applications in scala.

[@vadimprudnikov9072]

@@abelgerli Thank you for the answer! My point is that the author should consider preparing a cleaner example. I believe that the first impression is very important, and people expect to see something nice and simple, so you will get better retention. Thank you.

[@LusidDreaming]

@@vadimprudnikov9072 I agree to some degree, but often in examples for a framework this is more helpful. When you write cleaner code, it's easier to understand from a high level, but it becomes difficult to understand how to implement it yourself because there are many utility classes involved. It's a double edged sword: on one hand, like this presentation, you get to see everything needed to implement the solution in one place, but it does look messy because there's not a lot of separation of concerns. The other extreme is that the code is very clean and easy to understand, but then when you go to imement it yourself you have trouble finding all the little utilities you need. I also agree with the previous comment that scala is much cleaner. If you go look at scala examples the actors are typically much smaller and easier to understand.

[@hotplugin]

Boring presentation.