Showing posts from April, 2016

Microservices are about applying a group of Best Practices

Microservices Denial A number of times clients have said; they can’t imagine their organisation using Microservices. I found this surprising as I know those people are using many of the principles of Microservices already. I can understand that they feel no need to join the hype around microservices, but the reality is, like it or not, you are most likely using some of the best practices Microservices advocates. Stages of denial It all seems like hype, we don’t go in for that. Perhaps not all hype, but does it really mean anything. It all sounds pretty familiar. It sounds like what we are doing already. Formally or informally, most likely you have been following some best practices already. Adopting Best Practices. Perhaps you don’t like the name Microservices, and perhaps not all the different things people associate with Microservices are right for your team, your projects. Instead lets consider how do you formalise what you are trying to achi

Bad String abuse

In this Java Puzzler, it has some serious abuse of Strings, but what is going on?

An Interveiw on my talk for Low Latency Microservices at QCon New York

Key Takeaways Learn  lessons on developing low latency microservices with Java. Understand  how you can make asynchronous messaging simplier. Gain  practical advice on handling failure from large scale, low latency JVM based microservice implementations. Abstract In this talk we will look at the differences between micro-services and monolith architectures and their relative benefits and disadvantage. We will look at design patterns which will allow us to utilize these different strategies as a deployment concern without significant changes to the business logic. We will look at how micro-service architecture can be implemented under low latency constraints of 10 - 100 micro-second latencies, in Java in particular, and how these strategies reduce the impact of serializing data and logging.

Turning JDBC into a Micro Service

A deep dive into a low latency microservice We look at a microservice which can run in it’s own JVM, can perform JDBC updates and queries via a persistent queue for in bound request and a queue for results. In previous posts I looked at the theory behind there low latency micro-services so lets have a look at a micro-service which can do something useful. I would consider this a Gateway Service as it interacts with a system which is outside the microservice model.

Low latency Microservices

Overview In these articles I look at how we can use micro-services are yet have ease of testing, and low latency performance.  In the last of these I look at restarting a service after a failure. Microservices for Performance Microservices is a buzz word at the moment. Is it really something original or based on established best practices. There are some disadvantages to the way micro-services have been implemented, but can these be solved? Microservices in the Chronicle World - Part 1 At a high level, different Microservices strategies have a lot in common. They subscribe to the same ideals. When it comes to the details of how they are actually implemented, they can vary Microservices in the Chronicle world - Part 2 In this part we look at turning a component into a service.