Architecture & security
This section is for people evaluating jtWMS, such as architects, security reviewers and IT teams. It describes how the platform is put together and the guarantees it makes, without the detail of how each part is implemented.
jtWMS is a multi-tenant warehouse management platform. It is made of separate services, each responsible for one area such as identity, warehouse configuration or the product catalog, and each with its own database. Every request enters through a single gateway, which authenticates it before passing it on. The warehouse configuration and catalog services announce their changes as events, and those same events are what webhook subscribers receive.
Each organisation is a tenant, and its data is kept apart from every other tenant’s: the tenant a request acts for comes from its credentials, never from the request itself. Access within a tenant is controlled by roles built from fine-grained permissions, and changes to data are recorded in an audit trail.
- Platform overview: what jtWMS covers, the API-first approach, and how the parts fit together.
- Service domains: the services, what each one owns, and the gateway in front of them.
- Multi-tenancy and data isolation: how every request is held to one tenant, and how plans and features apply per tenant.
- Security model: sign-in and sessions, API keys, roles and permissions, the audit trail, rate limits and signed webhooks.
- Integration model: the REST API, events after changes, the versioning policy, webhooks and correlation IDs.
- Data lifecycle and consistency: soft deletes, active and inactive records, concurrent writes and cascade deletes.
- Deployment: container images, the gateway in front of the services, health endpoints and configuration.