pelle.io

Keeping up with recent technology developments was already hard before AI.

During a recent cloud migration project that had Scaleway as target cloud I stumbled upon their Dedibox Start-9-M dedicated server offering, delivering an AMD Ryzen™ 5 PRO 3600 (6C/12T, 3.6 GHz) machine with 32 GB of memory and two 1 TB NVMe disks for a p…

A central aspect of the infrastructure deployed by Solidblocks cloud is the reduction of moving parts to minimize the potential attack surface.

Although AWS S3 buckets are as stable and easy as it gets, sometimes you might not want to have an AWS dependency at all, or you expect a lot of egress traffic, making it a potentially costly choice.

April 2026 has not been kind to someone who is responsible for maintaining and securing online services, Copy Fail and dirtyfrag kept everyone busy with updating machines and making sure no data was lost or exfiltrated.

Most of the projects I work on nowadays are hosted on GitHub.

For let’s say “geopolitical reasons” (I’ve always wanted to justify something with geopolitical reasons) I have been involved in quite a few Hyperscaler exits in the past year.

As the number of ready-to-use Terraform modules included in my open source infrastructure components suite slowly grows, ensuring quality has been a constant topic during development.

A common obstacle I encounter when building deployments outside the typical hyperscalers like AWS or Azure is the issue where to store the initial artifacts needed to bootstrap the new deployment.

As laid out in my previous post “out of cloud” migrating applications from the big-hyperscalers to smaller (and cheaper) alternatives sometimes comes with the challenge to figure out alternatives for features that may be missing in the target environment…

If you are using Terraform (or Tofu nowadays) you might already have run into the chicken-and-egg issue that comes with the infrastructure state storage.

This post will detail and summarize the key architectural considerations and findings based on the experience of moving several environments from one of the usual hyperscaler-suspects like AWS/Azure/GCP to a self-managed, but still cloud hosted solution b…

If you are ready for another instance of me rambling about developer experience, this post will detail a Gradle pattern to ensure that secrets for Java or Kotlin integration tests are readily available locally and in CI, without the need to manually set up

When selecting a tech stack for my personal backup needs, I aim for the most boring but still supported software that is available.

Just in time for the public holiday in Germany, the Solidblocks infrastructure components collection got another addition. solidblocks-dns is a Kotlin library that lets you interact with the Hetzner DNS API to easily manage DNS zones and records.

One of the main benefits of using infrastructure-as-code is the reproducibility of your environments.

As time goes by and a project grows, ideas and concepts that initially seemed like good and pragmatic solutions can sometimes deteriorate into a convoluted mess.

Providing test utility classes or test fixtures for other projects in Gradle environments can be an annoying and cumbersome endeavor.

I just want to parse a timestamp on the JVM If you are in a hurry and just want to know which JVM (Java/Kotlin) library can parse which date formats look –>here<– for an overview.

Solidblocks RDS PostgreSQL is a ready to use, all-batteries included Terraform module for deploying PostgreSQL databases to the Hetzner cloud.

An often overlooked and admittedly cumbersome topic when developing infrastructure as code (IaC), is the testing of the resources that were created from said infrastructure code.

If you are part of a platform team or develop libraries or SDKs that are used by other people, a small detail from my previous post of the developer experience series might have caught your eye.

This post is a part of my series about project developer experience, for the other posts have a look here.

Imprint Christian Pelster Querkamp 13 25451 Quickborn Responsible for content Christian Pelster Querkamp 13 25451 Quickborn Contact Telefon: +49 176 23 81 7001 E-Mail: pelle@pelle.io Liability for content The content of this site has been created with the…

Angaben gemäß § 5 TMG Christian Pelster Querkamp 13 25451 Quickborn Telefon: +49 176 23 81 7001 E-Mail: pelle@pelle.io Haftungsausschluss – Disclaimer: Haftung für Inhalte Die Inhalte unserer Webseite wurden mit größtmöglicher Sorgfalt erstellt.

After years of shifting workloads to the big cloud providers like AWS or Azure, I am now more often confronted with situations where the deployed cloud infrastructures become unmanageable cost and complexity wise.

Although the situation greatly improved over the last 10 years, with very new hardware under Linux you sometimes may run into hardware compatibility issues.

A personal pet peeve of mine when joining a new project or environment is the overall developer experience (DX).

Being a freelance consultant for some time now, I find myself frequently coming back to one of my older posts on how to run a PostgreSQL database in the cloud, where the cloud is not one of the big ones that already offer a dedicated managed database serv…

One of the many fun aspects when taking over an existing codebase is that you inevitably learn something new - if you want or not ;-).

For projects with roots in the Java ecosystem the combination if Liquibase and Jooq is a popular approach on creating and evolving database schemas, as well as interacting with the created data afterwards.

I am a Freelance Software Developer and Infrastructure specialist with a strong background in system administration and software development.

An often overlooked alternative to the big players in the cloud market is the Hetzner Cloud, developed by the well known German hosting company Hetzner.

This post will show you how to use vault, signed SSH keys and some bash glue code to secure SSH connections, make them more verifiable and allow flexible access to your SSH servers.