When comparing Back4App vs Prisma, the Slant community recommends Back4App for most people. In the question“What is the best GraphQL as a Service?” Back4App is ranked 1st while Prisma is ranked 2nd. The most important reason people chose Back4App is:
The platform is reliable allow to scale up the applications running on it.
Ranked in these QuestionsQuestion Ranking
Pros
Pro Open source
Back4app is an open source BAAS and Backend generator.
Pro Smooth migration from Parse
Back4App offers a smooth migration for all former Parse users who wish to migrate their data now that Parse has announced that it will stop soon.
Pro Great documentation
Pro Type safety
Prisma generates types out of a schema, enabling type safety across your application
Pro TypeScript native support
Pro VSCode plugin
Great support for VSCode with autocompletion, quick fixes, syntax highlighting of the Prisma schema
Pro Introspection
Introspects your database to generate a schema you can use to generate your client makes it simple to get started with existing databases.
Pro Declarative single source of truth for your database schema
Pro Integrated migration tool
Prisma Migrate makes it easy to create migrations for production.
Pro Great support
Actually responds on issues or the Prisma Slack with helpful answers.
Cons
Con Uses MongoDB for the backend, which is not considered very safe by many
Back4App uses MongoDB as the database where data is stored. Mongo has been known to have issues with data corruption and data loss.
Con No support for code first models
Can't add models in code first. You have to use Prisma's files to define your models and then let it generate the code for you.
Con Lack of NoSQL Support
Currently doesn't officially support NoSQL databases. There is a connector in preview for MongoDB, but no word on when it'll be fully released yet.