ASP.NET Core ships with Kestrel server, which is the default, cross-platform HTTP server. Deploying a .NET 8+ with Angular 18+ is possible on different scenarios and we can also think of using a sort of encapsulation for rendering the front-office app, containing the bare minimum to serve a Web-based app with HTML, JS and the minimal backend features, to render the app on a web browser. We can use Kestrel with a reverse proxy server such as Nginx.

Ah, the ever-evolving landscape of databases. As technology marches forward, we find ourselves facing a new contender: NoSQL databases. The world of NoSQL brings forth a plethora of options, each with its own unique characteristics and strengths, demanding greater responsibility from software architects right from the project’s inception.

We’ve already gone through the introduction of what is actually a Monad in a previous article and we discovered that all the classes that share the same functionality form a sort of Category. Now I want to show you how to apply those functionalities to a wide range of other classes without the need of using OOP style or either touching pre-existent code. How can I do that? It’s simple, using Type Classes, so let’s dive in!

And here we are, facing the deaf stone in front of us. We want to go functional and to do that we have to face the most important concept that we must embrace: Monads. In this post I’m going to show what is a Monad in Scala in a very pragmatic way, so you won’t have to worry about strange definitions taken from the category theory or things like that. The goal here is to understand and use monads in Scala.

In this tutorial I’ll try to enlist a series of steps that have to be taken in order to deploy a new app onto Amazon Kubernetes Service, which requires more effort than one could think of at first glance. I spent a lot of time to move an app from Google Kubernetes Engine (GKE) to AWS EKS and it’s quite clear to me that this is not as simple as it should be.