Skip to content

Category: Backend

Configure Spotify’s backstage with Keycloak OiDC as Auth Provider

Spotify’s backstage is a widely used developer portal framework. When properly configured, it is very powerful and integrates with dozens of other tools that are used daily by developers, managers and devops teams.

One of the first aspects to consider when setting up backstage is the user access and authentication. Although Backstage provides a few out-of-the-box identity provider integrations, Keycloak is not one of them, and the process to configure it can be a bit daunting, especially if one is new to Backstage and how it is structure.

This article aims to provide a step-by-step guide on how to create a Keycloak OiDC client and how to configure Backstage to use it.

Implementing the Worker Pattern / Competing Consumers Pattern with MQTT shared subscriptions – MQTT Series #3

Hi and welcome to the 3rd article of the MQTT Series. In this article we’ll start looking into more advanced, yet very commonly found scenarios in IoT workloads. We’ll discuss the scalability and availability of consumers and we’ll see different ways to implement a load balanced consumption layer, namely by implementing Worker Pattern / Competing Consumers Pattern with MQTT shared subscriptions.

SEQUELIZE AND TYPESCRIPT

As many .NET developers transitioning to the world of Node, I started looking for an ORM. After some research, I found sequelize which seems widely adopted by the community.

I’m using typescript, and I quickly found the way to define the model with sequelize a bit too verbose, and especially a duplication of the typescript class.

That’s when I discovered sequelize-typescript, which provides this bridge, and leverages typescript’s typings, so mapping can be transparent if so we wish. All it takes is to extend a base Model class, and some annotations.