Book Image

Hands-On Microservices with C#

By : Matt Cole
Book Image

Hands-On Microservices with C#

By: Matt Cole

Overview of this book

C# is a powerful language when it comes to building applications and software architecture using rich libraries and tools such as .NET. This book will harness the strength of C# in developing microservices architectures and applications. This book shows developers how to develop an enterprise-grade, event-driven, asynchronous, message-based microservice framework using C#, .NET, and various open source tools. We will discuss how to send and receive messages, how to design many types of microservice that are truly usable in a corporate environment. We will also dissect each case and explain the code, best practices, pros and cons, and more. Through our journey, we will use many open source tools, and create file monitors, a machine learning microservice, a quantitative financial microservice that can handle bonds and credit default swaps, a deployment microservice to show you how to better manage your deployments, and memory, health status, and other microservices. By the end of this book, you will have a complete microservice ecosystem you can place into production or customize in no time.
Table of Contents (16 chapters)
11
Trello Microservice – Board Status Updating
12
Microservice Manager – The Nexus

Building your microservice – part two

In the second half of our chapter, we will create another FileSystemWatcher for you, but this time we'll approach it a bit differently. As with all our other microservices, the first thing we need to do is create our console application. In this instance, we will name it FileSystemMonitorMicroService as follows:

With that being done, and our template project in place, we now need to add the NuGet package, Topshelf.FileSystemWatcher. This is a very simple, yet powerful, library that is specifically designed to monitor filesystem change events on Windows and will save us a lot of work from writing our own.

Here's what it looks like from within NuGet:

Our message

The following...