🏗️ Implementations

This page lists the available PetcliniX showcases as they’re built. Each one implements the same domain model and functionality requirements, but with a different paradigm, language, or architecture. Explore the repositories to compare trade-offs directly.

Building only a frontend or only a backend? You don’t need to build the other half from scratch — see the shared API reference for the contract you can build against (or implement).


At a Glance

Implementation Paradigm Stack Summary
java-springboot-react-mtier Classic layered monolith Java 21 · Spring Boot 3.5 · React 19 · MariaDB Spring Boot REST backend + React SPA frontend behind Nginx, with JWT auth and a Docker Compose setup.
php-twig-mtier Server-rendered MVC PHP · Twig · MariaDB (PDO) Classic server-rendered PHP MVC with hand-rolled PDO instead of an ORM, in a thin Controller → Service → Repository → Domain architecture.
rust-axum-vslice Vertical slices, no database Rust · axum · JSON files on disk Files-instead-of-a-database JSON API: each feature module owns its handlers and file I/O end to end, with flock (not a DB transaction) preventing double-booking.

java-springboot-react-mtier

A veterinary clinic management system implemented as a classic layered monolith: Spring Boot REST backend and React SPA frontend.


php-twig-mtier

A veterinary clinic management system implemented as classic server-rendered PHP MVC, with hand-rolled PDO instead of an ORM.


rust-axum-vslice

A veterinary clinic management system implemented as a files-instead-of-a-database JSON API, the deliberate opposite of the other DB-backed layered implementations.


Want to add your own paradigm to this list? See the rules for a showcase and the project goals.