You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: tutorial/markdown/mobile/couchbase-edge-server/edge-server-demo-meal-app.md
+2-10Lines changed: 2 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -85,7 +85,7 @@ At the end of the setup, your Capella Setup looks like this:
85
85

86
86
87
87
### Capella App Services
88
-
Although instructions are specified for Capella App Services, equivalent instructions apply to self-managed Sync Gateway as well.
88
+
App Services acts as our cloud sync layer - it will validate and route data between Edge Server and Capella while enforcing security rules. Although instructions are specified for Capella App Services, equivalent instructions apply to self-managed Sync Gateway as well.
89
89
90
90
* Follow [instructions](https://docs.couchbase.com/cloud/get-started/create-account.html#app-services) to create a free tier App Services that links to the free tier cluster created in previous step.
91
91
* Create an *App Endpoint* named "american234" by following these [instructions](https://docs.couchbase.com/cloud/get-started/configuring-app-services.html#create-app-endpoint). When you create the App Endpoint, link it to the bucket named "mealordering", the scope named "AmericanAirlines", and the collection named "AA234".
@@ -207,16 +207,8 @@ To place an Order:
207
207
};
208
208
```
209
209
210
-
The below api is used to handle real-time changes to orders using the Edge Server's changes feed API. Let's break it down:
211
210
212
-
-`_changes?feed=continuous` - This establishes a continuous feed connection that stays open to receive updates in real-time
213
-
-`include_docs=true` - Includes the full document content with each change notification
214
-
-`heartbeat=600` - Sends an empty line every 600ms to keep the connection alive
215
-
-`since=now` - Only get changes that occur after the feed is established
216
-
-`filter=doc_ids&doc_ids=businessinventory` - Filter to only receive changes for the businessinventory document
217
-
- The request includes basic authentication headers and uses an AbortController to allow canceling the feed
218
-
219
-
This allows the web app to react immediately when inventory changes occur from other seats placing orders.
211
+
The web app uses Edge Server's real-time _changes API to instantly reflect inventory updates across all seats. When business class seat 4A orders steak, other seats see the remaining count update without refreshing:
0 commit comments