Backend and APIs
On this page
The backend applies business behavior and serves the data the interface needs. OwlMeans Common provides conventions for services, requests and access checks.
Libraries by purpose
| Library or standard | Purpose | Public OwlMeans package |
|---|---|---|
| Fastify | Serve HTTP APIs. | @owlmeans/server-api |
| Ajv and format extensions | Validate structured request and configuration data. | @owlmeans/entrypoint |
| Fastify CORS and Helmet plugins | Support browser-origin controls and security-related HTTP headers. | @owlmeans/server-api |
| Fastify multipart support | Handle supported file-upload requests. | @owlmeans/server-api |
These are public ecosystem dependencies and standards. The exact dependency set of an app depends on its generated project and developed features; not every library listed here is required by every application.
Use this in a project
- Describe the behavior you need in the specification or story.
- Ask the agent to use the project’s existing OwlMeans Common conventions.
- Review the related public package documentation when you want to understand a dependency.
- Try the behavior in the preview and review its access rules.
Describe which users may create or update a contact. Ask the agent to implement validation and permission checks alongside the form, then test a denied request as well as a valid one.
An API is how the interface asks the server to do something. Validating a request checks its shape; authorization checks whether its sender may perform it.
Read OwlMeans Tech Concept for the application architecture and continue with another agent for the harness workflow.
Application example
Category: CRM and customer management. Example: a small team CRM with contact ownership and manager access.
Names and marks
Fastify, Ajv names and any associated marks remain with their respective owners or project maintainers. References identify products, standards or source examples. OwlMeans documentation does not imply sponsorship or endorsement by those owners.