3 ms·
Hi, I just discovered this yesterday and wanted to say thank you! It's exactly what I was looking for. I'd like to concur with the other commenters here: it wo
by vekker 7y ago
Hi, I just discovered this yesterday and wanted to say thank you! It's exactly what I was looking for.
I'd like to concur with the other commenters here: it would be great to have some more information about the architectural choices (especially the database... and how to backup or connect this with other data sources?), as well as who's behind the project & its roadmap.
- eldad_fux 7y agoHi Vekker, In a nutshell, I can say that Appwrite was designed for scale. It uses common MariaDB and Redis containers as storage engines and should support basic clustering out of the box, no hidden magic. Same goes for backups. All you need is to backup the MariaDB databases and the Appwrite storage folder, just like you would with any basic app architecture. We took great length to have the most simple setup possible. I do plan to release some tutorials covering our architecture and design decision. In the meantime, you can check our stack on StackShare (https://stackshare.io/appwrite/appwrite https://stackshare.io/appwrite/appwrite) and learn more about how we generate docs and SDKs (https://medium.com/@eldadfux/how-we-integrated-our-docs-and-sdks-as-first-class-citizens-of-our-coding-process-8e343def0e9 https://medium.com/@eldadfux/how-we-integrated-our-docs-and-...).