I just got back from four conferences in Europe...and boy are my arms tired. One of the common themes of a lot of talks seemed to be the magic of microservices. I decided to give my 2 cents on the subject in this new rant:

Minimal APIs in .NET 6 aren't even released yet, but I want to start thinking about how to structure larger projects. While Controllers are still a valid option, for medium size projects, you have options on how to structure your APIs.

.NET 6 Preview 6 is here. One of the big changes I'm looking forward to is how startup is changing. With this change, comes "Minimal APIs" too. While getting rid of the Startup class is a welcome change, I'm a little less excited about how Minimal APIs might be over-used.

Another of my talks that were scheduled after offering my speaking skills on Twitter, I got to talk to a great group of developers in Sheffield England. I did a quick talk on using the Microsoft API Versioning system to version your APIs.

Writing APIs have been a big part of my career. I've written COM, DCOM, XML based APIs, ISAPI Filters, SOAP, REST, gRPC, and others. A lot of this time a new technology in writing APIs has been chasing the new ‘cool’ technology that would fix everything.

I had the opportunity to talk on the .NET Conf last week. Was fun to talk about .NET API Versioning. I love how much easier it is, these days, to be able to implement routing than it used to.