A Lazy Sequence

Microservice premium

17 May 2015

martinfowler.com

Martin Fowler:

The fulcrum of whether or not to use microservices is the complexity of the system you're contemplating. The microservices approach is all about handling a complex system, but in order to do so the approach introduces its own set of complexities. When you use microservices you have to work on automated deployment, monitoring, dealing with failure, eventual consistency, and other factors that a distributed system introduces. There are well-known ways to cope with all this, but it's extra effort, and nobody I know in software development seems to have acres of free time.

Alternate hard and soft layers

08 May 2015

www.c2.com

Still the one of the most valuable architectural patterns I have encountered. Just what it says on the tin.

What is the appeal of dynamically-typed languages?

08 May 2015

gist.github.com

Erik Osheim:

Obviously the biggest problem with writing Python compared to Scala is that you have many fewer static guarantees about what the program does. I'm not going to sugarcoat this — it's a big disadvantage.

Most of the other advantages have to be understood in terms of this. If you value compile-time guarantees you may be tempted not to acknowledge the advantages. I think this is a mistake. If you really want to understand what makes writing Python appealing (or even fun), you have to be willing to suspend disbelief.