About projectsManage how your Serialized data and configuration is organized using Projects.
Projects are the main entry point for all Serialized APIs. Your API keys are connected to a single project and your data is stored in a single project.
Projects are the container for all your configuration. This includes:
Regular projects provide one isolated data store for your data. Aggregates, events, projections, reactions and logs are all separated between projects. It is for example not possible to set up a projection definition in one project that subscribes to a feed in a different project.
Multi-tenant projects provide a separate data store for each tenant in the project. This means that in such projects there can be many data stores, each containing individual aggregates, projections, reactions.
There are many scenarios where using multiple projects can be useful and in most cases you will want more than one project in your account.
You can use different projects for separating data in different development environments (development, test, production) .
In some applications it can be useful to use a regular project for storing some data and a multi-tenant project for storing customer data. Your application can then use different API keys for the different projects, just like accessing different databases.
You may have different internal development projects that should not be dependent on each other or interfere with each other, but you may still want to keep them under the same Account to collect your billing in an aggregated way.