Confused about feature implementation idea
Hey everyone,
This is more of an engineering question than a SaaS business question and I am confused about what solution is the correct one. I am building something that allows fellow SaaS developers to do Quota Enforcement in ther saas apps easily via SDK and a cloud platform to manage it.
What I am currently implementing is quite simple.
You as the dev know what your SaaS entities/resources are
(eg,
projects
- has notes
- has tasks
- has uploaded_pdf_files
imagine a tree like strucutre from the user as the root. when you build your pricing plans you will want to set quotas on some or all the resources for eg.
starter plan
- 5 projects
- 2 notes / project
- 3 tasks / project
- 10 uploaded files / project
my question is I am allowing the developer to build this tree on the platform, and then attach quota limits per plans. but now the question is once the dev goes to production with a let's call it tree V1, and then decides that "hey uploaded_pdf_files needs to be per user and not per project" and wants to move that out, then there's already production data generated for the users based on tree V1. how can I provide the dev a clean way to do this. or this is something that should not be my concern as the quota enforcement service? Any advice? maybe my idea of resource tree is wrong or I am looking at it the wrong way and it's too much tricky work to do migrate from tree v1 to v2