Hello, I’m new to Strapi and our team is currently evaluating it for our website. Due to certain constraints, we’re limited to using the open-source edition of Strapi rather than the enterprise version.
We’re considering a unique approach: reusing Strapi’s admin UI (including the Content-Type Builder and Content Manager etc) while developing our own custom backend that can communicate with the Strapi UI. Our plan is to maintain the same API request/response structure but implement it ourselves.
The primary reasons for this approach are:
- We need to implement extensive customizations on the backend (including security features, versioning, and workflow management).
- We aim to deploy the CMS in AWS environment while using native aws services such as Lambda, DynamoDB…etc.
Given these requirements, we believe it may be more efficient to build a backend from the ground up while preserving the existing API structure, rather than adapting the existing Strapi backend.
We’d appreciate your insights on this approach. Are there any significant drawbacks or potential issues we should be aware of? Is this strategy feasible? If not, could you explain why?