Bigler On Code
My name is James Bigler. I am a software developer. This blog is mostly a collection of links related to software programming and technology.
Search This Blog
Friday, September 4, 2015
Akka.net bootcamp
Bounded Contexts
- Building Mircoservices - This was a really interesting read and I learned a lot of useful stuff
- Enterprise Integration Patterns - This one is considered the bible of integrating through messaging frameworks. It felt it bit like reading an encyclopedia. Maybe I shouldn't have tried to read it end to end and instead just used it as a reference.
- Patterns, Principles, and Practices of Domain-Driven Design - I am still reading this one. I would say this book is somewhere in between the other two books. Not a light fun read but full a useful stuff and not quite as heavy as an encyclopedia.
Saturday, April 18, 2015
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/
Saturday, March 7, 2015
Samza
Nativescript
http://docs.nativescript.org/getting-started.html
Would be interesting to compare this against
http://www.reactnative.com
Thursday, January 22, 2015
Riot – A React-like, 2.5K user interface library
Tuesday, November 4, 2014
Next Version of C#
Tuesday, April 8, 2014
CQRS Appendix
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.
Friday, March 28, 2014
Connecting people when they have no connection
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>
Monday, March 17, 2014
14 chapters down one appendix to go
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.