Replies: 24 comments
-
|
Thanks, @hmmhmmhm. From a feature perspective, Prisma definitely could provide a powerful set of tools for managing, migrating, and querying data from Appwrite. I think myself and others in the community believe that Appwrite is suitable and proven to be used in production today also while being flexible enough to be integrated with a tool like Prisma. I think there's more exploration to be done on the integration side, as there is definitely a balance to be had in terms of what most users of Appwrite would use vs what's available out of the box in terms of database access. We are always looking to make development easier and faster with the Appwrite API, in addition to supporting more advanced use cases. And of course the community is always able to dig into the code and explore these types of integrations also. We will definitely keep this on our radar moving forward. |
Beta Was this translation helpful? Give feedback.
-
|
Any news on these? I was really keen on subscribing AppWrite cloud, been waiting for it for months, but then I discovered I "do not" have direct access to my database. I was subscribbing AppWrite cloud mainly for "managed user auth", "no infrastructure worries", "7 day log retention", "image transformation", "storage" all in one. But honestly, I really want to have full control of my model. I understand AppWrite provides alot of power mechanisms through abstraction. However, personally, I want that abstractions with other things. Database querying is bread and butter, I do woud not want to "learn" something new, which for my use-case is trivially solved with simple queries, that happens to vendor locks me! |
Beta Was this translation helpful? Give feedback.
-
|
Second this. |
Beta Was this translation helpful? Give feedback.
-
|
What is the update regarding this integration |
Beta Was this translation helpful? Give feedback.
-
|
Is there a solution yet everybody? |
Beta Was this translation helpful? Give feedback.
-
|
This would be just magic. An SDK agnostic tool for describing and managing the 'appwrite infra' not just databases would be amazing. But certainly starting at the db makes a lot of sense. Ideally we should be able to describe structure in a common DSL. I just wrote a bunch of python to set up my database. But there is a lot more todo. Many more collections, relationships, indexes and permissions. So I started abstracting. However it feels like I am re-inventing the wheel. Interestingly, Prisma has found it's way into the python ecosystem: https://prisma-client-py.readthedocs.io/en/stable/ |
Beta Was this translation helpful? Give feedback.
-
|
Is there any solution about this? I dont really grasp good side of appwrite SDK. Prefer prisma and directly to their database like prisma + supabase |
Beta Was this translation helpful? Give feedback.
-
|
+1 |
Beta Was this translation helpful? Give feedback.
-
|
+1 |
Beta Was this translation helpful? Give feedback.
-
|
+1 |
Beta Was this translation helpful? Give feedback.
-
|
Having an integration with Prisma would be great, even if it is just to get migrations and type safe queries. |
Beta Was this translation helpful? Give feedback.
-
|
Agreed here, writing a script to template out a Collection is not ideal. |
Beta Was this translation helpful? Give feedback.
-
|
+1 |
Beta Was this translation helpful? Give feedback.
-
|
+1 |
Beta Was this translation helpful? Give feedback.
-
|
+1 |
Beta Was this translation helpful? Give feedback.
-
|
yeahhhh, seconded. BTW weldone appwrite ;) |
Beta Was this translation helpful? Give feedback.
-
|
Even after three years, I still want this feature. And many developers in the community still want it too. @eldadfux would you be able to take another look at this feature..? 🥺 |
Beta Was this translation helpful? Give feedback.
-
|
+1 |
Beta Was this translation helpful? Give feedback.
-
|
Hey everyone, thanks so much for all the feedback and discussion around this. The team is still actively discussing the possibility of Prisma integration. Appwrite is built as an API-first platform to provide a consistent and secure foundation for building apps, and traditionally, direct ORM access hasn’t aligned with that model. That said, we completely understand why Prisma is appealing, and are open to exploring how it might fit into the ecosystem. In parallel, we're continuing to invest in expanding Appwrite's built-in database features to better support production use cases. Really appreciate all the input. These conversations are a big part of how we shape the future of Appwrite. |
Beta Was this translation helpful? Give feedback.
-
|
kinda make sense, whats the point of have appwrite sdk if you working again for prisma 😂 |
Beta Was this translation helpful? Give feedback.
-
|
I noticed this request has been around for years and keeps coming up as Prisma becomes more common. Is there any updated stance or roadmap item regarding Prisma integration with Appwrite? Many of us would appreciate clarity, even if it’s a “not planned” decision. |
Beta Was this translation helpful? Give feedback.
-
|
I don't know what Appwrite's internal plans are, but as of now (2026), Appwrite doesn't seem to be prioritizing this as a core feature. However, someone has created Appwrite ORM. |
Beta Was this translation helpful? Give feedback.
-
Thank you for sharing this Appwrite ORM link. Will look into. |
Beta Was this translation helpful? Give feedback.
-
|
Appwrite ORM interesting but i am still waiting for Prisma ORM & Drizzle ORM Integration |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
🔖 Feature description
Prisma is a ORM that has very strong automatic migration capabilities
and strong db accessibility. (Very convenient to build some raw query)
Prisma will also be able to support more complex DB features if Prisma is made available with Appwrite.
If we can make Prisma work with appwrite, It should be able to support much complex DB functions.
Regardless of Prisma's migration, being able to using some
prisma query build system will be a huge advantage.
Prisma already supports Supbase, Keystone, and many other frameworks.
And it is being used to increase their DB utilization.
( Supabase Prisma Guide: https://supabase.com/docs/guides/integrations/prisma )
( Keystone Prisma Guide: https://v5.keystonejs.com/guides/prisma )
🎤 Pitch
One of the main reasons why Appwrite is not applicable to main production
is that it does not take full advantage of the powerful features of DB.
With Appwrite, it is also impossible to inject data directly into the DB without going through the Appwrite API.
It requires need to change the Appwrite system,
which does not currently recommend direct query of mutation to DB.
( And it might be caused by redis caching.
I think we should provide some button to disable redis caching,
etc. that adversely affects direct data muate to db. )
If we can use proven ORM with Appwrite, we will be able to significantly
increase the number of Appwrite based productions.
👀 Have you spent some time to check if this issue has been raised before?
🏢 Have you read the Code of Conduct?
Beta Was this translation helpful? Give feedback.
All reactions