Possible way to covert part of JS application piecemeal

I like how they limit to three components and limit how those components interact.
----
Introducing T3: Enabling Large Scale JavaScript Applications | Box Blog
https://www.box.com/blog/introducing-t3-enabling-large-scale-javascript-applications/

Samza

This article describes something that sounds like CQRS and Microservices in terms of database concepts.

http://blog.confluent.io/2015/03/04/turning-the-database-inside-out-with-apache-samza/

This is really smart since the people that would mostly likely resist this type of architecture change are the people that are most invested in relational databases.

Nativescript

This is allows you to write native apps with JavaScript. Very cool.

http://docs.nativescript.org/getting-started.html

Would be interesting to compare this against

http://www.reactnative.com

Riot – A React-like, 2.5K user interface library

I saw this posted on Hacker News.  Looks very nice and simple.

https://muut.com/riotjs/

Next Version of C#

Watched this video  about the next version of C#.

http://channel9.msdn.com/Events/TechEd/Europe/2014/DEV-B345

We could use the code introspection features to validate our coding standards.  Also the nameof operator could be used in FluentNhibernate for mapping properties so when you rename your properties your mappings update.

CQRS Appendix

I finished the Appendix on CQRS in the book Implementing Domain Driven Design.

I really liked the appendix. It was written by a different author, and he provided very detailed code and explanations. There is even an example project on github.

I searched for my more information about the author and found a blog post where he mentioned Greg Young's Event Store. I didn't know this existed but it sounds pretty cool.

Connecting people when they have no connection

This is an awesome idea.

http://www.wired.com/gadgetlab/2014/03/apple-multipeer-connectivity/



Viva JDA! Join us at JDA FOCUS April 27-30 in Vegas! Register now at jda.com/FOCUS<http://now.jda.com/2014-FOCUS-TextLink.html>

14 chapters down one appendix to go

I finished Chapter 14 on the Application of Implementing Domain Driven Design.

We have had the "What should go in a Application Service and what should go in a domain service" discussion here at work many times. At one point, the author claims I am going to clearly answer this question for you. I thought great I won't have to stress about that anymore. I feel like a broken record saying this but ... I was hoping he would give more details in his explanation because it still doesn't seem clear to me. What I got from what the book is that Application Services are for handling transactions and security. If you are doing more than creating an entity and adding it to a repository then you may have a "significant process" that needs to be modeled in the domain. He talked a little about Application Services that are for querying. I couldn't find any rules of thumb though about when your queries have too much business logic and should be domain services themselves. He did mention that sometimes you need to convert your application service into its own bounded context. I can think of one place in our code that might benefit from this idea.

There are no more chapters in the book. There is an appendix about CQRS written by someone else which I plan to read, but for the most part I am done with this book. I can't say I enjoyed reading it. I was really hoping it would answer a lot of questions for me, but I really don't think it did. I did some learn some things but not a whole lot. I guess the author's writing style just doesn't fit with how I learn. He probably knows a lot of stuff that can help me, but whatever reason I just didn't get that information from this book.

Bounded Context Integration

I finished Chapter 13 on Integrating Bounded Contexts of Implementing Domain Driven Design.

In our domain everything is jumbled together in one giant bounded context. Having never done what the author describes I found this chapter very interesting.

I liked the discussion about messaging. I had never thought about messages arriving out of order. I thought the author came up with a very simple solution to what could be a very complicated problem.

I also liked the discussion where he modeled a long running process as an entity and setup trackers to do automatic retries. I had to do something similar with a third party service our application integrates with. The code I wrote was very specific to the one area I was working on though. If you did this type of integration in multiple places in your application, then I could see that having more generic reusable components could be very helpful.

Article about Javascript Promises

This is cool.

http://www.html5rocks.com/en/tutorials/es6/promises/