From 7074f62f595905af92f8ab154ff767a747088f9b Mon Sep 17 00:00:00 2001 From: Dominic Date: Thu, 12 Dec 2024 12:19:23 +0200 Subject: [PATCH] fix: doc loop --- .../app-backend-setup/writing-client-changes.mdx | 14 ++++++++++++-- 1 file changed, 12 insertions(+), 2 deletions(-) diff --git a/installation/app-backend-setup/writing-client-changes.mdx b/installation/app-backend-setup/writing-client-changes.mdx index 933458f5..9e2e44bb 100644 --- a/installation/app-backend-setup/writing-client-changes.mdx +++ b/installation/app-backend-setup/writing-client-changes.mdx @@ -3,14 +3,16 @@ title: "Writing Client Changes" description: "Your app backend needs to expose an API endpoint to write changes to your backend database that are received from the PowerSync client." --- + + The backend receives the changes from your `uploadData` function in the `PowerSyncBackendConnector` on the client. + + This could be: 1. A single endpoint accepting a batch of changes from the client, with minimal client-side processing. 2. Separate endpoints based on the types of changes. 3. A combination of the above. -For details of the client-side interface to your backend, see [Integrating With Your Backend](/installation/client-side-setup/integrating-with-your-backend). - It's important that your endpoint be blocking/synchronous with underlying Postgres or MongoDB writes. @@ -63,3 +65,11 @@ For details on handling write conflicts, see: horizontal /> + +### Example implementations + +We have some example backend implementations that you can use as a guide for your implementation: + +#### [NodeJS](https://github.com/powersync-ja/powersync-nodejs-backend-todolist-demo) + +#### [Django](https://github.com/powersync-ja/powersync-django-backend-todolist-demo)