- Overview
- Alternatives
- Pros & Cons
- Compare
- Auto-generated GraphQL API and schema with the help of the "Shadow CRUD"
- Quick and easy installation
- Does not handle database migrations
Does not handle database migrations
Strapi is a fantastic open-source CMS and API creation tool for frontend developers. However, one of the biggest concerns I have with Strapi is that your application does not record nor manage database migrations after schema changes to your database. This is a crucial part of building a sound and future proof application, without a record of schema changes things can get hairy quickly. It's kinda like building an application without using Git to track code changes.
Auto-generated GraphQL API and schema with the help of the "Shadow CRUD"
Possibly the fastest way to create a basic GraphQL API. With the help of Strapi graphQL plugin you can have your GraphQL API up and running in a matter of minutes. Where all necessary types and resolvers are auto-generated by Strapi's Shadow CRUD system. Simply install the plugin, and you can start using your GraphQL API with GraphiQL interface at /graphql.
Quick and easy installation
I love the fact that Strapi is extremely easy to install. The Strapi CLI will guide you through the process of installing the headless CMS manually. A bunch of one-click-install's and containers are available for third-party platforms and hosting providers as well.
Information found on this page is crowd-sourced by the community and contains the most agreed upon Strapi Pros and Cons. Which allows you to determine advantages and disadvantages of using Strapi and pinpoint Strapi's strengths and weaknesses. Anyone that have used Strapi can post their own views of the software, vote on the accuracy of other users claims, and help more people is the process of doing so.
This page was last updated on Sat 05 Mar 2022 (2 years, 1 month ago).