Thank you for following through on the introduction, and I hope you enjoyed the reading.
One of the design goals of ZenStack is to package its features into loosely coupled components and let the developers choose what to use and how to mix and match them. For example, if your project is a monorepo one using one of the "meta-frameworks" like Next.js, you can use ZenStack across your entire stack like the following:
However, you can also only pick the parts that suit your needs best:
- Improved Prisma schema with features like multi-file support and model inheritance.
- Implementing multi-tenancy.
- A better way to achieve soft delete.
- Headless RESTful API over the Node.js framework of your choice, with Swagger documentation.