Documentation on Palmyra

Overview

Mon, 01 Jan 0001 00:00:00 +0000

Palmyra at a glance#

Palmyra is a rapid-development framework for building database-driven web applications. Describe your data as annotated Java classes, compose the API surface you need, and wire it to ready-made React screens — the framework handles the SQL, the HTTP plumbing, the paging, the forms, and the grid refresh so your team focuses on features.

What it means for the business#

Faster time to market. A new entity (screen + API + database wiring) takes hours, not days. The cost per feature stays flat as the application grows.
Lower development cost. One developer can cover both backend and frontend. No separate teams for REST controllers, data-access layers, and UI state management.
Consistent quality. Pagination, sorting, validation, access control, and audit trails are built in — not reimplemented per screen.
Flexible UI. Swap between Mantine and MUI without rewriting business logic. The same API serves web, mobile, and third-party integrations.
Enterprise-ready. Multi-database support (MariaDB, MySQL, PostgreSQL, Oracle, DB2), role-based permissions, data-level security, reactive streaming for large exports, and a pluggable auth layer that works with any identity provider.

What it means for developers#

Backend developers#

Write a POJO, add a few annotations, implement one or two interfaces — and you have a working, paginated, filterable REST API. No controllers, no SQL, no DTO mappers.

Use Cases

Mon, 01 Jan 0001 00:00:00 +0000

Use Cases#

Business problems Palmyra solves#

Palmyra is built for organisations that need internal, data-heavy web applications delivered fast — and that keep needing more of them. The framework is not a product; it’s the machinery that makes products like these cheaper to build and maintain.

Beyond basic CRUD, Palmyra’s advanced patterns cover approval workflows, child-entity handlers with nested URLs, email notifications, row-level security, filterable dashboards, i18n, and in-app discussion threads — all documented with worked examples.

Comparison

Mon, 01 Jan 0001 00:00:00 +0000

How Palmyra compares#

An honest side-by-side with the frameworks teams typically evaluate alongside Palmyra. Every tool has a sweet spot; the goal here is to help you decide, not to sell.

Palmyra’s frontend works with any backend. Implement a custom StoreFactory and the same grids, forms, and lookups talk to REST, GraphQL, Firebase, or any legacy API — no component changes needed. See Connecting to a custom backend.

Backend comparisons#

vs Spring Data REST#

Spring Data REST auto-publishes JPA repositories as REST endpoints — conceptually the closest alternative.