Brushstrokes of Conscience
I’ve been thinking a lot about multi-region systems lately, especially around Keycloak-style setups. And honestly, the more I worked with it, the more I realized something simple: Failover and replication are usually treated like database problems, but they’re actually system design decisions. The default standalone Keycloak setup in
This repository contains a set of Quickstarts for the Quarkus framework. Each of them has a Getting started guide. Requirements To compile and run these demos you will need: * JDK 17+ * Mandrel or GraalVM See the Building a Native Executable guide for help setting up your environment. Use alternative platforms
Design a production-ready IAM system using Keycloak, Django, Entra ID and eIDAS. Includes a live interactive simulator. Why this post exists. Most developers build authentication exactly once, and spend years paying for it you know what I mean 🕶️. The problem is not a lack of tools Keycloak, Django, Microsoft Entra
Nothing was installed. No browser automation tools were used. After inspecting Gmail and seeing that its class names change per session, the approach relied on that understanding. Everything was done directly through the browser console using JavaScript. This is a one-session cleanup trick that runs only in your open Gmail