Building Microservices with ASP.NET Core

Chapter 12. Putting It All Together

I started this book by showing you how to build a console application (“Hello, world!”) in Microsoft’s new cross-platform development framework, .NET Core. From there, you simply added package references and method calls to gradually progress from a console app to a fully functioning web server capable of hosting RESTful endpoints with the Model–View–Controller pattern fully supported.

While I don’t want to belittle the importance of learning syntax and the details of which lines of code to write and when, there is an important lesson to learn here: code won’t solve all your problems.

Building microservices isn’t about learning C#, or Java, or Go—it’s about learning how to build applications that thrive in elastically scaling environments, that do not have host affinity, and that can start and stop at a moment’s notice. In other words, it’s about building cloud-native applications.

As we’ve progressed from chapter to chapter, we’ve deferred some important discussions in service of explaining the details. Now that we’re done with the details, I’d like to use this chapter to revisit some patterns, discuss areas where we may have cut corners, and even present a few philosophical ideas likely to fuel debates that might cause riots within your development team.

Identifying and Fixing Anti-Patterns

Every author has to walk the fine line between providing real-world samples and providing samples that are small and simple enough to digest in the relatively ...