archive: 2015

Microservice Sizing

As I mentioned in my last blog post Microservices and Boundaries, I regularly see the question “How big should my microservice be?” The fast answer, albeit not the easy one, is that they should be the

Microservices and Boundaries

One of the most common questions I’ve been getting asked about microservices is “How big?” I was recently down in Montevideo Uruguay speaking at the .NET UY Meetup speaking about microservices. As par

Task could not find sgen.exe using the SdkToolsPath

I spent the better part of this afternoon fighting with this error (and arguing Canadian voting rights with the Western Devs). I was trying to run our project’s build script which uses nAnt and MSBuil

Microservices and isolation

In my first post I made reference to the idea of microservice isolation a number of times. I figured that this is as good of a topic as any to start with. The concept of isolation and boundaries is co

Microservices; A Gentle Introduction

This past winter I started working on a project that was being architected with a mind towards using microservices. Prior to this I’d only seen the term ‘microservices’ floating around in the ether an

SaaS and Commodities

I’m doing some work right now that requires us to send SMS messages. The organization I’m working with has never had this capability before so we are starting at ground level when it comes to looking

Sharpening chisels

I’m working on a cedar garden gate for our back yard. It’s all mortise and tenon joinery which means I make a lot of use of my Narex bench and mortise chisels. The more you use chisels the

Choosing AOP technologies

I get asked how to pick an AOP technology on a pretty regular basis. The other day while I was answering the question I got to thinking that there is a pretty logical flow to selecting which technolog

Arduino and logging to the cloud

I participated in a lunch and learn today that demo’d the capabilities of logentries.com. It was impressive in the ease that you are able to parse, analyse and digest logging information. Once y