Replies: 4 comments
-
One account (admin) where you control billing, members(teams), resources, workspaces and roles. From your account you can manage/create workspaces(projects), allocate resources and invite teams(members). So basically, from my account which has the following llimits: 1m request per month, 2G of storage and 1000 usage i can manage/create two workspaces for example like this: 1. Workspace 1:
2. Workspace 2:
I can distribute my allocated resources defined in my account to my workspaces. |
Beta Was this translation helpful? Give feedback.
-
Just to add to what Daniel proposes above, you'd need to also allocate some M3O credits to each project for paid APIs |
Beta Was this translation helpful? Give feedback.
-
Some other things to think about assuming that projects is s a feature only available on paid tiers
|
Beta Was this translation helpful? Give feedback.
-
If projects is a paid only feature then I guess we'd have to stop you from downgrading until you deleted them.
Good question, we'd need to map out the scenario to understand if it makes sense but I guess why not right. |
Beta Was this translation helpful? Give feedback.
-
As per the discussion, we've been talking about how to incorporate projects into M3O for quite some time. The idea being projects serve as a way of separating resources for different apps/teams so you get isolated resources (users, databases, etc). This makes total sense for splitting working and also collaborating.
Prior Art
The feature is done differently in different places
Let's break it out into "account switching" and "projects or teams".
Account Switching
Currently I have two accounts; one is personal, the other is for work. Logically I should not have to logout to login into the other. So account switching would be a valuable feature which allows people to manage resources by creating separate accounts. I could imagine this implemented as a UI specific feature which uses cookies and session storage to deal with the switching.
Ideally there's some sort of drop down with the list of my accounts and "add another account". Simple yet effective feature.
Spec:
Projects or Teams
The next part is projects or teams with shared/isolated resources. I personally have a set of resources allocated to my account, I may then create a new project called "Micro" which has its own set of isolated. I can then switch from my personal project to Micro to separately manage its resources and keys. I should be able to invite other users to my project to collaborate on it aka invite my team to the project. It's not yet clear if billing has to be separated as well or better left at the account level.
It's likely that projects beneath the covers are just another Micro account since that acts a foundation for all that we already do. An account has an owner, scopes, keys, etc and we quite simply need to link this to multiple collaborators in a "projects" service in m3o/backend.
Spec:
Limits still TBD. Either limiting number of projects in total or aggregating resource limits based on the parent account. If one user has the ability to create multiple projects with separate limits then we're effectively giving away more for free. So potentially tying projects to subscriptions makes sense.
If projects are just logical then the resources are directly tied to an account, but far more work to isolate the resources per service.
Beta Was this translation helpful? Give feedback.
All reactions