I've really become intrigued by Microservice architecture. So much of it feels like a natural progression of many wonderful development practices, techniques and tools – a natural evolution.
Microservices are quite a hot topic currently - moving to fine grained, small, distributed services from “monolith”. I’d expect it to be an important topic for the next 3-5 years.
I wanted to spend some time exploring the pros and cons of the architecture. I’ve started to blog about this and will be providing sample code via my Github account and a management tools via this website.
I've been getting very excited recently about Microservices. It seems a natural progression, and culmination, of multiple architectural ideals. For me, Microservices are more a state of mind at the moment rather than a practical implementation. This will be the first of a series of posts as I start to explore the the architecture.
In this post I shall be concentrating on how I shall be managing the source code. For any development project, it is important to setup your source control. This should be the first step in any development project. I plan to discuss how I want the source management to work and how I'm going to achieve it.
In this article I make some predictions for the coming year.
This week I take a look at Microservices, Event Sourcing, CQRS, Agile, Scrum and Azure/ AWS mapping.
A quick article looking at the options for simple stateful MicroService on the Azure platform.
With the previous release of Visual Studio tools for Azure functions, I wanted to take a look at Continuous Delivery using Visual Studio Team Services and Octopus Deploy
This week I give up an update on my blog re-development, Health Check Product, TypeScript and current learning.
In this article, I provide a method to include additional projects in Azure Functions. This is part 1 - the depreciated version.