I Rewrote Spring PetClinic Without Spring Boot. It Used 59% Less RAM.
A Spring PetClinic rewrite with 59% lower measured application RSS: explicit SQL, familiar architecture, and more work around forms.
Practical notes, release announcements, and engineering deep-dives from the projects built at PVR Labs.
A Spring PetClinic rewrite with 59% lower measured application RSS: explicit SQL, familiar architecture, and more work around forms.
Shared services across Javalin, Jex and Micronaut, with Spring JDBC and Micronaut Data references: two HotSpot and native runs per stack on a 512 MiB VM.
A database-backed service on a 512 MiB VM: comparing optimized Spring Boot with Javalin and Jdbi on HotSpot 27 and Oracle Native Image 25.
On a 512 MiB VM, the same Spring Boot service used 212 MiB as a JAR, 187 MiB on optimized HotSpot 27, and 107 MiB as Oracle Native Image on JDK 25. Startup went from 11.91 s to 3.79 s to 0.183 s.
On a 512 MiB VM, a combined deployment change cut startup by 68% and app RSS by 25 MiB. MyBatis and embedded H2 follow-ups explore the costs of going further.
A scheduled shell check turns StatLite application health into Telegram alerts and recovery messages. Remembered state avoids repeated alerts and false recoveries when health data is missing.
Use Caddy's per-host metrics to follow HTTP requests, errors and response latency across applications without changing their code.
Reuse existing SwiftBar scripts with a lightweight native macOS menu-bar app. One local comparison recorded a 12 MB physical footprint versus 59 MB for SwiftBar.
A million typed CSV rows. Batched Scriptella took about 15 seconds on PostgreSQL and 10 on MariaDB. JDBC was a few seconds faster, which may be worth a declarative ETL file for an occasional job.
Two pools released 18 idle connections. PostgreSQL cgroup memory was approximately 29 MiB lower. Recorded timelines show retirement and the latency cost of reopening.
Equivalent JDBC applications on Java 25, with measured startup, resident memory, and CPU. Quarkus and Micronaut converge near the end of this small-VM run.
A hypothetical slow API on a small VPS shows how application and host metrics can point to CPU contention from another process.
Try practical FastAPI monitoring locally, then run the same small StatLite and SQLite setup alongside an application on a VPS.
A small Express helper exposes /statlite/metrics so StatLite can chart traffic, errors, latency, and Node.js memory without a Prometheus and Grafana stack.
The same Star Pulse workload, JDK 25, and 80 MiB heap. Quarkus started larger, then had the smaller resident set, while RSS hid swap and the box later ran out of headroom.
A successful test run produced 1,476 lines. The agent needed roughly one.
The agent already explored the repo and understands the task. Hand off that session state instead of reconstructing it somewhere else. Or import a local Codex or Claude Code session directly.
A JDK 25 Alpine follow-up completed the hour on a nominal 256 MiB VPS, but high swap use and a long scheduling delay kept the result firmly in stretch-test territory.
A Spring Boot 3.5 app with JPA, Tomcat, and Actuator ran on 512 MB plus a small swapfile. The monitor stayed around 12 MiB.
Review complete Git changes in VS Code, then use focused repository context when an AI reviewer needs more evidence.
How a small Bash wrapper reduced successful Maven output by more than 99.7% while preserving useful diagnostics for coding agents.
Use AI coding assistants without granting them repository access: map locally, disclose only reviewed context, and confirm every proposed write.
Turn Spring Boot Actuator data into a focused dashboard for a few applications on a VPS, without operating a full Prometheus and Grafana stack.
Autonomous coding agents consume tokens rapidly during reviews by rescanning projects and pulling broad context. Learn how to map locally, extract precise snippets, and review efficiently in any web chat.