.Net Core Microservices using MVC
If nothing else, ASP.NET Core is a concentrated in and built around microservices, which is a fantastic way to ground your application in domain-specific code that you can easily plug and play as you need. Are you working in a company that cares about .Net Core Microservices? Is your domain team hooked into having access to Enterprise’s Domain Hub and Domain Service APIs, and will benefit from being able to tightly integrate ECM / ECD / CBT / CBTL / DLM etc. This means you will be able to hugely speed up how fast your applications are before any downtime occurs.
What are microservices
Microservices are simple, autonomous, self-service software services which can be implemented on standard computing platforms (e.g. .NET). Microservices can have their message routing happen on an HTTP-based system like Apache Kafka, and generally they are loosely coupled and allow any number of independent components within them to have independent logics and are aggregated by large clusters to provide higher availability, scalability, and resilience to different failures.
Small discrete applications
Small discrete application is a great opportunity to really situate yourself and pick up a practical and silly solution for your problem as well as finding out how you can utilize current best practices to help you build a neat little thing.
In this post, part CRM (Customer Relationship Management) and part cloud robotics, I am going to focus on scaling organs. microservices are going to be added as I think they are an extremely interesting fit for this nicely thought through project.
Startup and release processes
My problem is about managing 3-5 animals in a fully autonomous way, which shouldn’t need more than a couple minutes per day, deploying to AWS, Java, and building Docker images from a set of Docker Containers on a box using a local controller node.
Before I go a little ways down in this halcyon land of fancy microservices, I want to remind you (hopefully!) that this architecture is what I have been after all along, The best possible microservice architecture is one that you can validate on and on by testing it carefully and independently from each other, not one that you have to test and parameterise.
Use Microservice Architecture and Get Fired Up
microservices when something is simple, lightweight, simple
So can you see the merit in microservices?