update deprecation date; WIP on aws appsync migration guide

mongodb · Jan 21, 2025 · 7e15162 · 7e15162
1 parent 6334005
commit 7e15162
Show file tree

Hide file tree

Showing 13 changed files with 87 additions and 11 deletions.
diff --git a/source/deprecation.txt b/source/deprecation.txt
@@ -28,7 +28,7 @@ Previously Deprecated Services
 
 As of March 12, 2024, GraphQL and Static Hosting are deprecated for Atlas App
 Services. GraphQL and Static Hosting services will be discontinued on
-**March 12, 2025**.
+**September 30, 2025**.
 
 To learn more about these deprecations, refer to the :ref:`Migrate Static
 Hosting and GraphQL From App Services page <migrate-hosting-graphql>`.

diff --git a/source/graphql/migrate-apollo.txt b/source/graphql/migrate-apollo.txt
@@ -62,7 +62,7 @@ following steps:
       Once you have verified that your GraphQL API endpoints are fully migrated
       and operational on Apollo Server, you can delete your MongoDB Atlas App
       Services app to avoid unnecessary costs. As a reminder, Atlas GraphQL
-      endpoints will no longer be supported beginning March 12, 2025.
+      endpoints will no longer be supported beginning September 30, 2025.
 
 Next Steps
 ----------

diff --git a/source/graphql/migrate-hasura.txt b/source/graphql/migrate-hasura.txt
@@ -191,4 +191,4 @@ Shut down MongoDB Atlas App Services Endpoints
 Once you have verified that your GraphQL API endpoints are fully migrated
 and operational on Hasura, you can delete your MongoDB Atlas App
 Services app to avoid unnecessary costs. As a reminder, Atlas GraphQL
-endpoints will no longer be supported beginning March 12, 2025.
+endpoints will no longer be supported beginning September 30, 2025.
diff --git a/source/graphql/migrate-wundergraph.txt b/source/graphql/migrate-wundergraph.txt
@@ -186,7 +186,7 @@ your project and the technologies used.
       Once you have verified that your GraphQL API endpoints are fully migrated
       and operational on WunderGraph, you can delete your MongoDB Atlas App
       Services app to avoid unnecessary costs. As a reminder, Atlas GraphQL
-      endpoints will no longer be supported beginning **March 12, 2025**.
+      endpoints will no longer be supported beginning **September 30, 2025**.
 
 Next Steps
 ----------

diff --git a/source/hosting/migrate-blob.txt b/source/hosting/migrate-blob.txt
@@ -59,7 +59,7 @@ below to migrate from using Atlas Hosting to using your own S3 bucket.
       Once you have verified that your files deploy successfully to your S3
       bucket, delete your hosted files from your Atlas App Services app.
       As a reminder, hosting domains on Atlas App Services will no longer run
-      starting on March 12, 2025.
+      starting on September 30, 2025.
 
 Access S3 Bucket from Atlas Functions
 -------------------------------------

diff --git a/source/hosting/migrate-netlify.txt b/source/hosting/migrate-netlify.txt
@@ -160,7 +160,7 @@ your site manually <https://docs.netlify.com/cli/get-started/#manual-deploys>`__
       Once you have verified that your application deploys successfully to
       Netlify, delete your hosted files from your Atlas App Services app.
       As a reminder, hosting domains on Atlas App Services will no longer run
-      starting on March 12, 2025.
+      starting on September 30, 2025.
 
 Next Steps
 ----------

diff --git a/source/hosting/migrate-vercel.txt b/source/hosting/migrate-vercel.txt
@@ -102,7 +102,7 @@ Vercel documentation: `Deploy from CLI <https://vercel.com/docs/cli/deploying-fr
       Once you have verified that your application deploys successfully to
       Vercel, delete your hosted files from your Atlas App Services app.
       As a reminder, hosting domains on Atlas App Services will no longer run
-      starting on March 12, 2025.
+      starting on September 30, 2025.
 
 When you create a deployment, Vercel automatically adds a new and unique
 generated URL. You can visit this URL to preview your changes in a live

diff --git a/source/images/migration/aws_appsync_architecture.png b/source/images/migration/aws_appsync_architecture.png
diff --git a/source/images/migration/device_sync_architecture.png b/source/images/migration/device_sync_architecture.png
diff --git a/source/migrate-hosting-graphql.txt b/source/migrate-hosting-graphql.txt
@@ -23,9 +23,9 @@ Migrate Static Hosting and GraphQL From App Services
 
    GraphQL and Static Hosting are deprecated.
 
-As of **March 12, 2024** , GraphQL and Static Hosting are deprecated for Atlas App
-Services. GraphQL and Static Hosting services will be discontinued after one
-year on March 12, 2025.
+As of **September 30, 2024** , GraphQL and Static Hosting are deprecated for Atlas App
+Services. GraphQL and Static Hosting services will be discontinued on September 
+30, 2025.
 
 If you use GraphQL or Static Hosting, you should migrate to other providers
 before the services are discontinued. Below, you can find migration guides

diff --git a/source/release-notes/backend.txt b/source/release-notes/backend.txt
@@ -22,7 +22,7 @@ Atlas App Services Changelog
 ~~~~~~~~~~~~~~~~~~~~~~
 
 - New Apps can no longer enable GraphQL or Static Hosting. Apps that already have these 
-  features will continue to have access until March 2025.
+  features will continue to have access until September 30 2025.
 
 .. _backend_20240807:
 

diff --git a/source/sync/device-sync-deprecation.txt b/source/sync/device-sync-deprecation.txt
@@ -24,6 +24,8 @@ and be removed before **September 30, 2024**.
 Refer to the :ref:`App Services deprecation page <app-services-deprecation>` for
 more deprecation information.
 
+.. _alternative_solutions:
+
 Alternative Solutions
 ---------------------
 

diff --git a/source/sync/migration/awsappsync.txt b/source/sync/migration/awsappsync.txt
@@ -0,0 +1,74 @@
+.. meta::
+   :robots: nosnippet
+
+.. _aws_appsync:
+
+============================
+AWS App Sync Migration Guide
+============================
+
+.. contents:: On this page
+   :local:
+   :backlinks: none
+   :depth: 2
+   :class: singlecol
+
+As of September 2024, :ref:`Device Services is deprecated <device-sync-deprecation>`. 
+There are many :ref:`third-party services <alternative_solutions>` you can use 
+to migrate your App Services app. This page provides guidance in using 
+AWS AppSync. 
+
+What is AWS AppSync?
+--------------------
+`AWS AppSync <https://aws.amazon.com/appsync/>`__ is a serverless platform that 
+you can use to keep your data synchronized between devices through GraphQL and 
+Pub/Sub APIs. Combined with MongoDB Atlas as the backend datastore, you maintain 
+many of the benefits of Device Sync.
+
+System Architecture
+-------------------
+
+Device Sync
+~~~~~~~~~~~
+
+The following diagram shows the typical Device Sync architecture:
+
+.. image:: /images/migration/device_sync_architecture.png
+   :alt: A diagram showing a typical Device Sync architecture.
+
+In this architecture, your app uses the Realm APIs to communicate directly with 
+Atlas App Services, which handles data storage, synchronization, and conflict 
+resolution.
+
+The data flow is:
+
+- Data is stored in each device’s local realm db.
+- A user makes changes on the device. 
+- Device Sync APIs send changes to Atlas App Services.
+- Atlas App Services performs any necessary conflict resolution, stores the changes 
+  in Atlas, and syncs the changes to the other devices.
+- Device Sync APIs updates the data in each device’s local realm.
+
+AWS AppServices
+~~~~~~~~~~~~~~~
+
+When you migrate from Device Sync to AWS AppSync, you will need to make the 
+following changes to your architecture:
+
+- Use AWS AppSync to handle data synchronization 
+- Use an AWS Lambda Resolver to send data to Atlas via the MongoDB driver SDKs 
+- Use AWS Event Bridge to listen for event triggers from Atlas 
+- Add a Database Trigger to Atlas 
+
+You will also change 2 parts of your client code:
+
+- Because AppSync uses GraphQL, you will use the AWS AppSync API to communicate 
+  with it AppSync
+- The local data store also changes from a Realm database to the default 
+  datastore on the device (typically SQLite), or another one of your choice.
+
+The following diagram shows a typical example of the new architecture:
+
+.. image:: /images/migration/aws_appsync_architecture.png
+   :alt: A diagram showing a typical Device Sync architecture.
+