Resources organization for one app.

[mquinteiro]

I'm developing a SaaS where I will have clients, each client will have resources associated with it's account.

What best the best practices organizing the service? To have only one project and have all resources in the same project or to have one project by each customer?

I see some pros and cons in each structure.

With only one project pros:

- Console management could be cleaner as we don't have thousand of projects.

- Compute resources could shared between clients

- Maintenance of one computing resource is easier, multiple projects by client implies the maintenance in each project

cons:

- Can't evaluate individual cost by client

- Isolation of the data and processes reducing the data leak and security risks. 

[dionv]

Hello mquinteiro,

I agree to the pros and cons you listed and on my personal opinion, I would recommend having your clients on a per project basis to avoid issues of data leaks and wrong resources accessed and modified.

[mquinteiro]

Hi Dionv,

In the end, I went with a middle path, which is to create isolated resources with their own service account for each client. I don't want to have thousands of projects (hopefully) in my account. But I'm still not convinced.