Changelog

Product changelog

What’s new in AlveoForge: capabilities, rulings and fixes, newest first.

v1.0— Public launch

The first public release of AlveoForge: production-ready Java (Spring Boot 4.1) backends generated from your SQL schema. What v1.0 delivers, for every entity of every schema:

Architecture

  • Real hexagonal architecture (ports & adapters) with one self-contained vertical slice per entity, the domain isolated from database, framework and delivery.
  • Deterministic generation: the same schema always produces the same structure. Audit once, trust every build.
  • Deploy the same schema as a modular monolith or as microservices, with no rewrite.
  • The code is fully yours: standard, readable Java, no runtime dependency on AlveoForge.

Data model & persistence

  • Full standard SQL type coverage: arrays, enums, JSONB, UUID, timestamptz, numeric precision, binary, xml/citext, and more.
  • Composite, natural and generated primary keys; many-to-many modeled as first-class join resources.
  • PostgreSQL table inheritance and declarative partitioning.
  • Multi-store persistence: PostgreSQL, optional MongoDB, Redis cache, and a transactional outbox for cross-store propagation.
  • Soft-delete and audit fields (created / updated / deleted) managed automatically.

Database migrations & existing databases

  • Versioned migrations with your choice of Flyway or Liquibase, with full parity.
  • Brownfield adoption: point it at your existing production database and it adapts, without rebuilding your schema.
  • Your DDL is the single source of truth; the schema is validated against the entities at boot, so there is no drift.

API

  • Full CRUD plus batch operations: create-many, fetch-by-ids, bulk updates.
  • Relationship expansion on read (?expand=), up to two levels, without N+1 queries or a leaked ORM graph.
  • Framework-neutral pagination with configurable page and batch limits.
  • OpenAPI / Swagger documentation and request validation on every endpoint.
  • Public response DTOs to hide sensitive fields.

Authentication

  • JWT authentication (login / register) with refresh tokens and logout.
  • Email-verification flow on registration.
  • Works in-process (monolith) or across services (HTTP), from the same model.
  • Reference-data seeding and required-default handling, for a database that boots cleanly on first run.

Quality assurance

  • Test suite across all three layers plus end-to-end, covering success and failure paths (validation, auth, not-found, unsupported media).
  • Database integration tests for both PostgreSQL and MongoDB.
  • 95–100% coverage (methods, lines, branches), with HTML test and coverage reports delivered.

Scale & delivery

  • Validated on real 300+ table schemas.
  • Try before you buy: a live instance and the full Swagger preview, every endpoint testable, before any payment.
  • Delivered to a private repository with 30 days of post-delivery support; regenerated deterministically when your schema changes.
← Back to home