Geek Answers Handbook

Migrating from Parse-Server to dynamoDB. What are the foreseeable obstacles?

As we all know, I am one of the thousands of developers who have relied on Parse and are now forced to look for an alternative to Parse. When passing Parse-Server to AWS + MongoDB, I discovered DynamoDB. I think I just pass all the logic on the server side of DynamoDB. What are some of the problems that Parse does not have that might exist for DynamoDB?

+4
source share
3 answers

Since Parse includes a web server, you can interact with it through simple HTTP requests. DynamoDB is just a database, so you will need to directly connect via the AWS SDK or create an API in front of it, possibly using the Gateway and Lambda APIs.

In addition, since Parse is a full-featured Backend as a service, and DynamoDB is just a database, there are some features in Parse that won't be available if you just use DynamoDB directly from the iOS app. For example, to reset a user’s password, you need to send an email to the user. DynamoDB does not have a "password reset" function and cannot send emails directly. You will need to create this function yourself, using something like Lambda and SES.

Parse , , DynamoDB iOS. , , S3.

Parse , DynamoDB , , , , MongoDB NoSQL. , DynamoDB , , .

+4

AWS + DynamoDB .

DynamoDB MongoDB .

MongoDB , .

DynamoDB , ( ) , . , master/slave .

DynamoDB, .

+1

Parse AWS Dynamo ( : https://www.linkedin.com/pulse/parse-aws-migration-server-less-mobile-backend-mike-kirkwood?trk=prof-post

, DynamoDD Parse. , DynamoDB , Parse. , , DynamoDB. .

DynamoDB .

DynamoDB , Parse.

+1

More articles:


All Articles