Today, I’ll be continuing the tour of my self-registering API architecture by taking a look at the authentication API and the mechanics of how a service registers itself. This will be a more practical dive than the previous post’s theory-heavy chit-chat.
Several months ago, I started working on a new desktop application project that was to be backed by an microservice ecosystem. I ended up designing an API where the only well-known service is the one that handles authentication, and all other services register themselves with the authentication API and only access each other via service discovery. This yields extensibility: a new service doesn’t need to be explicitly set up in the ecosystem; just add it and go.
Yeah, you read that right. We’re gonna break some rules!
…One Converter to bring them all and in the XAML bind them…
Last time, I briefly mentioned a WPF converter that I created that helps solve the Cambrian Explosion problem that comes with creating specialized converters. Today I’ll go over that converter and what makes it tick.
At work I was recently assigned to a UWP app. This post chronicles my discoveries over the first couple days. Continue reading “A Brief Start with UWP”
I ran across an interesting scenario at work today that I think merits some discussion. In this post, I’ll cover what DRY is, and when following it religiously may actually cause problems.