Is the architecture of the cloud service correct?

Question

JavaScript

Good afternoon, for several years we have been developing online stores, blogs, etc. for clients, recently the idea arose to develop our own cloud platform with rest api for our clients, but so far I can’t figure out how to organize everything correctly.

There are two thoughts about this.
- All client site data is stored in one database, and each of them is given only its data by api key. This method is the easiest to implement, I see several advantages and disadvantages.

• Data security of neighboring customers
  
• more complex implementation of dynamic fields, since each client needs to generate its own post type with its own unique fields
  

- Organize everything through a docker container, then immediately the disadvantages from the previous paragraph disappear, but another disadvantage appears, this is a significant increase in resource consumption.

Advise how to do it right, and maybe throw a reading on this topic. Thanks in advance.

Answer 1

Of course, as always, everything depends directly on the project, I would advise you to read about the multi-tenant architecture, in my opinion, this is the most preferred way to implement the SaaS service architecture.
Links:

• habr: Multi-tenant architecture for SaaS applications
  
• youtube: (Panda Meetup): Multi-tenant architecture in Saa...
  
• youtube: (Alexander Belotserkovsky) Principles of cloud architecture -SaaS, Multi-Tenant
  

off topic, but you may be wondering

Вообще, разработка SaaS сервиса очень трудоемкая задача, если есть желание скооперироваться, мои контакты в профиле, там же ссылка на сайт проекта:) Мы ищем фронтендера на Vue или React, делаем платформу для электронной коммерции, если будет интересно, напишите любым удобным способом расскажу подробнее

Answer 2

Imagine that the base has collapsed. If it was the base of one client, then only his data would be lost. And you have all your eggs in one basket.