June 10, 2015 / by Simplicity Itself Team / In Getting , Started , With , Microservices

Service Discovery Overview

When building microservices, you have to naturally distribute your application around a network. It is almost always the case that you are building in a cloud environment, and often using immutable infrastructure. Ironically, this means that your virtual machines or containers are created and destroyed much more often than normal, as this immutable nature means that you don’t maintain them.

Read more

June 04, 2015 / by David Dawson / In Microservices and Reactive

Microservices Security: OAuth vs Session

A question often posed to us during our research and project work is “how should I secure a Microservice?”

Read more

March 02, 2015 / by David Dawson / In Microservices and Reactive

Best Practice Developer techniques: The Hunt for The Silver Bullet

Over the past 15 years of software development, especially since the XP movement gained traction, a series of styles, techniques and processes have gained broad industry adoption. These are, at times, called ‘best practices’. At others times they are referred to as dogma or ‘cargo cult’.

Read more

February 16, 2015 / by David Dawson / In Microservices and Reactive

Retiring Microservices Using Strangulation

No programmer likes to plan for their work to be taken offline and shutdown, but part of good antifragile thinking is allowing things that aren’t successful, to end. Applying that to Microservices, one of the natural parts of that architectural style is creating and destroying instances of a service. As part of the lifecycle of services, you sometimes have to create different versions of a service, and so manage the retiring of a previous version (although we try to avoid versioning where possible).

Read more
Older Entries Newer Entries

2014 Simplicity Itself: Software that Thrives. All rights reserved.