Holy moly it’s been a while. Time for some more Orleans goodness, hopefully? Caches!

The package I wrote about in this post is now a part of the OrleansContrib organization!

With the publishing of Orleans.SyncWork, I’ve had the opportunity to explore GitHub actions - which is a way to automate workflows. Here’s some of my first experience into the “action” (groan).

I’ve been talking about the idea of long running, CPU bound, synchronous work for a long time. Now, I’ve finally taken the time to build it out into a NuGet package!

Updated hexo to the latest version, trying out a new post!

Blogging through medium hasn’t exactly been a cash cow, but so far it’s been much more lucrative than blog.kritner.com, in that I’ve never been paid for the latter!

In a previous post I talked about using variable for keeping NuGet packages across multiple projects; now there is a (potentially) better way.

All right! It’s been a minute! Tamperproof cookies, I needed one, it’s pretty simple after thinking it through.

One of the folks over at NDepend reached out to me to provide a license for their product; let’s do some exploring!

The decorator pattern is a structural design pattern that can be used to add functionality to classes without modifying the original class or its interface.

Previously I wrote about creating Health Checks for Microsoft Orleans, but the JSON response was too minimal. In this post we’ll see about prettifying that output!

In this world where most companies rely on technology regardless of their niche, it’s indispensable to hire top-notch tech professionals.

Health Checks are a means of seeing how a system is running at the time of performing the check. Let’s see how we can apply them to Orleans!

My notes about trying to get started with React.

In the last post we started talking about mTLS. In the post I pointed out that the client cert’s signing CA was not verified, let’s fix that!

Pretty sure everyone at this point knows what TLS is, but what about mTLS? How is it different from TLS, what’s it used for?

The builder is a creational pattern that can be used to construct “more complex” objects, without having to directly new them up in calling code.

Working with the IHostBuilder introduced to .netcore has been an overall pleasant experience… until I needed configuration from appsettings for app bootstrapping. Luckily, there’s still a way to do it!

The factory is a creational pattern that can be used to retrieve instances of objects, without having to new them up directly in calling code.

The strategy pattern is one of the first patterns I learned, and it leads into at least one other pattern that I used constantly! Let’s do this thing!