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

Overview of FileSystemWatcher

As C# developers, you may already be familiar with the Windows FileSystemWatcher object and its capabilities. Before we get into writing our FileSystemWatcher, let's talk a little bit about how Windows and you, as a C# developer, handle monitoring changes to the filesystem.

The FileSystemWatcher object in .NET is the object that you will use to monitor a filesystem. Like most other input and output items, it is in the System.IO namespace. The filesystem monitor allows you to monitor directories and file types for changes. You can use it to watch for changes to a specific directory, files and subdirectories of a specific directory, and you can do so on a local computer, remote computer, or networked drive.

You do this by supplying a filter to the watcher so it knows the types of files to monitor for. In many cases, this can be the *.* wildcard...