Solution Architecture

Microsoft .NET Core based Microservice Architecture Solutions

Matt and Roland were present in Brisbane in October to deliver a talk entitled How Azure Service Fabric for .NET Core can simplify development of a microservice architecture.) The slides presented how a microservice architecture can be implemented using Service Fabric.

The talk went through all the benefits of Service Fabric, including performance savings for the developer, deployment and configuration) Service Fabric can even be used to support on premise services. (Be sure to watch the talk, as it is well worth a watch!)

Matt and Roland Kamsika discussed the advantages of the new .NET 5 framework which integrates all the existing diverse frameworks into a coherent whole.

The hypothetical application takes care of requests by implementing business logic, accessing data sources, and afterwards returning HTML, JSON, or XML actions. We will say that the application must sustain a range of clients, including desktop computer internet browsers running Single Web page Applications (Health spas), standard internet apps, mobile internet applications, as well as native mobile applications. The application could likewise subject an API for 3rd parties to consume. It must also have the ability to integrate its microservices or exterior applications asynchronously, to ensure that approach will assist resiliency of the microservices in the case of partial failures.

The application will include these sorts of parts:

Presentation components. These are in charge of handling the UI and also taking in remote solutions.

Domain name or service logic. This is the application’s domain name logic.

Data source accessibility reasoning. This includes data access parts responsible for accessing databases (SQL or NoSQL).

Application combination reasoning. This consists of a messaging channel, mostly based on message brokers.

The application will certainly need high scalability, while permitting its upright subsystems to scale out autonomously, due to the fact that particular subsystems will need even more scalability than others.

The application has to have the ability to be deployed in multiple framework environments (several public clouds and also on-premises) as well as ideally must be cross-platform, able to move from Linux to Windows (or the other way around) easily.

Advancement group context
We likewise presume the following regarding the growth process for the application:

You have several dev teams concentrating on different company areas of the application.

New team members have to become effective quickly, and the application must be easy to understand and customize.

The application will certainly have a long-term evolution as well as ever-changing business rules.

You require good long-term maintainability, which indicates having dexterity when executing new modifications in the future while having the ability to upgrade numerous subsystems with minimal influence on the other subsystems.

You wish to exercise constant assimilation as well as constant implementation of the application.

You wish to capitalize on arising innovations (frameworks, setting languages, and so on) while progressing the application. You do not want to make full migrations of the application when relocating to brand-new innovations, because that would result in high expenses as well as effect the predictability and also security of the application.

Selecting a design
What should the application release architecture be? The requirements for the application, together with the advancement context, strongly recommend that you must engineer the application by disintegrating it into independent subsystems in the form of working together microservices as well as containers, where a microservice is a container.

In this method, each solution (container) applies a set of cohesive and directly associated functions. For example, an application might include services such as the directory solution, purchasing solution, basket service, individual account service, etc

. Microservices communicate utilizing methods such as HTTP (REST), but also asynchronously (as an example, making use of AMQP) whenever possible, particularly when circulating updates with assimilation events.

Microservices are established and also released as containers separately of one another. This indicates that an advancement team can be creating and also releasing a certain microservice without affecting other subsystems.

Each microservice has its very own data source, allowing it to be completely decoupled from other microservices. When required, consistency between data sources from various microservices is attained utilizing application-level integration occasions (via a rational occasion bus), as managed in Command and Question Duty Partition (CQRS). As a result of that, the business constraints need to embrace ultimate consistency between the several microservices and relevant data

Useful Links