architecture for a combined Backend

I am bit confused how to implement Appwrite with my own Backend... I want a single point of entry and Appwrite should handle all the user/session/permission stuff... but because I have to communicate with a PLC I have to have my own Backend... so my question is how should an architecture look like? I drew a little possible solution? maybe you can tell me what is the best practice for my needs 🙂 Also I have to know how calls my PLC (Permission stuff) so the user has to be authenticated :X Also I need realtime updates from my PLC so the user has to see that :X

TL;DR

Developers are seeking advice on integrating their own backend with Appwrite for handling user/session/permission management. They are unsure about the best practices for this architecture. The solution involves using the Appwrite Flutter SDK to connect Appwrite with the Flutter app, allowing the backend to communicate with Appwrite via the REST API. This setup enables a single point of entry with Appwrite managing user permissions while the backend communicates with external systems like a PLC for real-time updates.

I would do first one: backend to appwrite and appwrite to app

You can use the API rest to connect the backend to Appwrite and send data to it

And then the Appwrite flutter SDK to connect appwrite to the flutter app

The second one I think will make Appwrite useless? Since if you connect the flutter app to your own backend instead of Appwrite, then the backend will be the one that handles all permissions, etc?

do you have an example how do this? I could not find any example how this should work... or maybe I did not get that 😄

What do you want the example about, API?

Reply to this thread by joining our Discord

Reply on Discord

Need support?

Join our Discord

Get community support by joining our Discord server.

Join Discord

Get premium support

Join Appwrite Pro and get email support from our team.

Learn more

Recommended threads

Need support?

Join our Discord

Get premium support