This is going to be the first post in a series of articles about modern tooling and techniques for building distributed systems. In this post, I will show how to use Docker for Windows to set up an ELK (Elasticsearch, Kibana, Logstash) server that we are going to use in future articles. The series is particularly geared toward traditional .NET developers. Let’s get started…
We’re excited to announce the release of a new, free white paper on the Microservices software architecture style.
Microservices is an architectural pattern gaining steam in the development community. A Microservices architecture addresses problems that modern enterprises often face, including responding to market demands, handling spikes in traffic, and being tolerant to failure. These benefits are achieved by functionally decomposing a business’ domain into microservices, services that handle only a single responsibility.
In this white paper, we discuss how Microservices came to be, contrasting architecture patterns, features of a Microservices architecture, established patterns, how to get started with Microservices, and suggestions for Microservices adoption.
Download the free Keyhole Software white paper today!
We have consultants who specialize in moving old to new, renovating dilapidated code bases, and designing brighter futures for enterprises who have been vendor-locked for most of their existence. We have come across some repeated patterns and strategies for how to approach modernization of legacy systems. In this blog, we will cover a strategy that is very popular right now, Re-Platforming.
The basic flow of this post will be:
Introduction to Modernization
High-level definition of the Re-Platforming Strategy for Modernization
Sample of Re-Platforming using Keyhole Syntax Tree Transformer, COBOL –> Java
Additional thoughts on the value/risk of this strategy
Let’s get started…
In part two of this series, we create a microservice architecture using JHipster’s available options for doing so. There is quite a bit more work to do with this approach as compared with the monolithic approach. But, in the end, it pays off. You will see the benefits and flexibility in decoupling our different layers of our architecture. Each layer will not be dependent upon another to run. Let’s get started…
So, you want to stay on the leading edge of technology, but feel overwhelmed by all the moving parts. You’re in luck! jHipster aims to make setting-up an app fairly painless.
In this jHipster series we are going to take you through, first, creating a monolithic application. Secondly, we will make an app in the microservices style. Last, we’ll give you some tips and tricks for jHipster best practices. Let’s first begin with Part One…