Microservices - Page 1 - Vanilla Java

Microsecond latency Microservice Benchmarked

It is common for a vendor to publish benchmarks with synthetic loads and code. However, what can be reasonably achieve in a real application? In this post, I discuss what we achieve with

Getting Involved

Contributing to Chronicle

Looking to contribute to a high peformance Open Source library in Java. This may be a good place to start. There is a number of ways to contribute to OpenHFT/Chronicle Software. You

Batching and Low Latency

This is testing the next release of Chronicle Queue 4.5.0 Why batch your data? Batching of multiple messages or updates into a single transaction is a common technique for improving performance,

Goldilocks Microservices

How to structure microservices? When structuring microservices we have to consider; how fine grain should our components be? how distributed should they be? I believe it’s important to treat these as

Distributing Common Java APIs

Distributing data stores vs Private data stores in Microservices Distributing data containers e.g. Maps, can be a way of avoiding having to think too much about distributing your application. Your business logic

Modelling Microservice Patterns in Code

Service Interactions There is a number of simple interactions a service can support. Which pattern is best for your application can depend on what an existing application expects, and what latency requirements you

Simple Asynchronous Microservices using Lambda Architecture.

Lambda Architecture Lambda Architecture is a simple, powerful, though limited example of a Microservice. As it is so simple, you want to use it as much as possible, to expose the more complex

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

Light weight Microservices

What do we see as light weight Microservices? A key requirements for productivity is a short development lifecycle. Every time you have to wait between changing code and knowing there is an error

Microservice with a Websocket transport

In this post, we will look at a simple component to publish market data and accept orders. How can this be accessed using websockets as a transport? Our service Interface for messages from

A JDBC Gateway Microservice

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

Microservices in the Chronicle World - Part 5

In this part we look at putting a micro service together as a collection of services, and consider how we can evaluate the performance of these services. We introduce JLBH (Java Latency Benchmark

Microservices in the Chronicle world - Part 4

A common issue we cover in our workshops is, how to restart a queue reader after a failure. The answer is not a simple as you might think. We do an on-site one

Microservices in the Chronicle World - Part 3

One of the problems with using microservices is performance. Latencies can be higher due to the cost of serialization, messaging and deserialization, and this reduces throughput. In particular, poor throughput is a problem

Microservices in the Chronicle world - Part 2

In this part we look at turning a component into a service. In Part 1, we looked at how we can easily create and test components which expect asynchronous messages[1] in and

Microservices in the Chronicle world - Part 1

At a high level, different Microservice 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.

Micro-services for performance

Overview 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 microservices have been implemented, but can