A long time ago, a fork of Django called “Django-nonrel” experimented with the idea of using Django’s ORM with a non-relational database; what was then called the App Engine Datastore, but is now known as Google Cloud Datastore (or technically, Google Cloud Firestore in Datastore Mode). Since then a more recent project called "django-gcloud-connectors" has been developed by Potato to allow seamless ORM integration... - Source: dev.to / 12 months ago

In that case use Cloud Datastore (aka Firestore in Datastore Mode). It's a NoSQL db that was initially targeted just for GAE (you needed to have a GAE App even if empty to use it) but that requirement has been relaxed. Source: about 2 years ago

As u/SierraBravoLima said - If you don't really need containerization, you can go with Google App Engine (Standard). If you need to store data, GAE will work with cloud datastore which has a large enough free tier. Source: about 3 years ago

Datastore mode had its start in App Engine's early days (launched in 2008), where its Datastore was the original scalable NoSQL database provided for all App Engine apps. In 2013, Datastore was made available all developers outside of App Engine, and "re-launched" as Cloud Datastore. In 2014, Google acquired Firebase for its RTDB (real-time database). Both teams worked together for the next 4 years, and in 2017,... Source: about 3 years ago

Database: datastore should be very cheap, or you could just output as csv text and copy into Google Sheets (free!). Source: over 3 years ago

So I started designing the DB using this cool tool. The project has 2 tables, users and categories . The user can create many categories as he wants so the first approach I took was creating a third table, a union table to store user_id and category_id. With this solution the users are able to create x numbers of categories and we can see assign the category to the user. - Source: dev.to / 2 months ago

Once you have generated the SQL code, you can convert it into a relational schema (the graphical table model) using DrawSQL. This tool offers:. - Source: dev.to / 3 months ago

DrawSQL makes it easy for teams to collaborate on creating and maintaining schema diagrams. With a single source of truth, there's no need for manually syncing diagram files between different developers and offline tools anymore. Source: almost 2 years ago

To be honest, since you are just getting started, I think you should reconsider simplifying this app to begin with. Built something easier and get some more experience before jumping in the ocean. Maybe start by focusing only on the parent company and sub-companies. However, I strongly recommend you to try and make a diagram of your database with relations and columns as it can you a lot of time. I personally use... Source: almost 2 years ago

After googling some, I found DrawSQL, which is a start. But I don't like its interface, and the inability to download the schemas in any form (at least not from what I can see). Source: over 2 years ago