Planning the database schema for the new Plio infrastructure was easy. Or that's what I thought initially. The previous structure of Plio used to have various JSON files, each representing an entity on its own. For example, a typical user's JSON file would look like this:
Multi-tenancy in Plio
Multi-tenancy in Plio
Multi-tenancy in Plio
Planning the database schema for the new Plio infrastructure was easy. Or that's what I thought initially. The previous structure of Plio used to have various JSON files, each representing an entity on its own. For example, a typical user's JSON file would look like this: