Ties together the four building blocks of the Dotkernel Headless Platform — API, Admin, Queue, and the Core submodule — and shows how they combine into a single platform.
The Headless Platform principle is to decouple the frontend from the backend services, so any number of outside systems can consume the same backend. Dotkernel implements this with four building blocks, each its own Git repository, which you combine based on your needs:
You don't need every piece from the start. You can begin with just Admin or just API and add the others later as requirements grow. Once you're running more than one application, pull the shared logic out into a Core submodule and include it in each one — a typical setup looks like API + Core, Admin + Core, and Queue + Core, each in its own repository, all reading from the same shared entities and services (see Using the Core Submodule).
Regardless of which pieces you use, every Dotkernel application and package boots the same way: through a ConfigProvider that declares its dependencies, handlers, and configuration, merged together by the framework at bootstrap time.
Q: What are the building blocks of the Dotkernel Headless Platform?
A: Dotkernel API, Dotkernel Admin, Dotkernel Queue, and the Core submodule.
Q: Do I need all four components to get started?
A: No, you can start with just Admin or just API and add the others as your requirements grow.
Q: How do multiple applications stay consistent with each other?
A: By sharing a Core submodule for entities and services, and by each bootstrapping through its own ConfigProvider.