---
title: "Feroz Shah (@fsmutimeer) | Hashnode"
description: "Feroz Shah (@fsmutimeer) writes on Hashnode. Read their latest articles and follow their work."
url: "https://hashnode.com/@fsmutimeer"
---

@fsmutimeer

# Feroz Shah

@fsmutimeer · Joined October 2026

### [Spring Boot: migrations at startup, health checks and metrics](https://fsmutimeer.hashnode.dev/spring-boot-migrations-at-startup-health-checks-and-metrics?utm_source=hashnode&utm_medium=feed)

Migrations are written in development, but they have to run wherever the application runs: on a colleague's laptop, in CI, in staging, in production. The simplest way to get there is to let the applic

8 min read · [fsmutimeer.hashnode.dev](https://fsmutimeer.hashnode.dev/spring-boot-migrations-at-startup-health-checks-and-metrics?utm_source=hashnode&utm_medium=feed)

[Nov 8](https://hashnode.com/posts/spring-boot-migrations-at-startup-health-checks-and-metrics/6af01604a0f6b958de5c4ec7)

### [Generate and apply database migrations without leaving IntelliJ IDEA](https://fsmutimeer.hashnode.dev/generate-and-apply-database-migrations-without-leaving-intellij-idea?utm_source=hashnode&utm_medium=feed)

You rename a field on a JPA entity. Then you leave the editor to write the SQL, write the rollback script, check which database you are about to change, and run it. The Migrax plugin for IntelliJ IDEA

7 min read · [fsmutimeer.hashnode.dev](https://fsmutimeer.hashnode.dev/generate-and-apply-database-migrations-without-leaving-intellij-idea?utm_source=hashnode&utm_medium=feed)

[Nov 6](https://hashnode.com/posts/generate-and-apply-database-migrations-without-leaving-intellij-idea/6aee043acfbe29ded1e0368c)

### [Generated SQL migrations for Python, TypeScript and Go projects](https://fsmutimeer.hashnode.dev/generated-sql-migrations-for-python-typescript-and-go-projects?utm_source=hashnode&utm_medium=feed)

Migrax started as a tool for Java: it reads JPA entities and writes the SQL migrations that bring the database in line with them. But the idea doesn't depend on Java. Every ORM knows the tables it exp

10 min read · [fsmutimeer.hashnode.dev](https://fsmutimeer.hashnode.dev/generated-sql-migrations-for-python-typescript-and-go-projects?utm_source=hashnode&utm_medium=feed)

[Oct 31](https://hashnode.com/posts/generated-sql-migrations-for-python-typescript-and-go-projects/6ae5d96f289d59eaf0e9da87)

### [Migrax vs Flyway: generated vs hand-written migrations](https://fsmutimeer.hashnode.dev/migrax-vs-flyway-generated-vs-hand-written-migrations?utm_source=hashnode&utm_medium=feed)

Flyway and Migrax both keep a database schema in numbered SQL files, apply them in order and record what ran. The difference is where the SQL comes from. With Flyway you write every migration yourself

7 min read · [fsmutimeer.hashnode.dev](https://fsmutimeer.hashnode.dev/migrax-vs-flyway-generated-vs-hand-written-migrations?utm_source=hashnode&utm_medium=feed)

[Oct 31](https://hashnode.com/posts/migrax-vs-flyway-generated-vs-hand-written-migrations/6ae5d9073b11fe7ff9167cb4)

### [Catching schema drift before it breaks production](https://fsmutimeer.hashnode.dev/catching-schema-drift-before-it-breaks-production?utm_source=hashnode&utm_medium=feed)

Migrations only describe a database as long as nobody changes it any other way. Then someone adds a column during an incident, a DBA widens a type, a data import relaxes a constraint, and nobody write

8 min read · [fsmutimeer.hashnode.dev](https://fsmutimeer.hashnode.dev/catching-schema-drift-before-it-breaks-production?utm_source=hashnode&utm_medium=feed)

[Oct 31](https://hashnode.com/posts/catching-schema-drift-before-it-breaks-production/6ae5d86325ebfd4cb548e0b0)
