Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Lock in Initial MVP Requirements for the Data Sync Service #14

Closed
patniko opened this issue Jan 27, 2019 · 8 comments
Closed

Lock in Initial MVP Requirements for the Data Sync Service #14

patniko opened this issue Jan 27, 2019 · 8 comments
Assignees
Labels
plan item A piece of work planned for an iteration. storage

Comments

@patniko
Copy link
Contributor

patniko commented Jan 27, 2019

To complement the new identity service and enable developers to easily manage end-user data we'll be developing a new Cosmos DB backed solution over the coming months. This will be initially targeted towards on-line first apps before layering in additional off-line capabilities. We'll share initial API's and screenshots over the coming weeks.

@patniko patniko added the feature request New feature request label Jan 27, 2019
@patniko patniko added this to the February 2019 milestone Jan 27, 2019
@Zakeelm Zakeelm changed the title Create initial designs for new data service Lock in Initial MVP Requirements for the Data Sync Service Jan 28, 2019
@patniko patniko added plan item A piece of work planned for an iteration. and removed plan item A piece of work planned for an iteration. feature request New feature request change-request labels Jan 29, 2019
@Zakeelm
Copy link
Contributor

Zakeelm commented Jan 31, 2019

As we're working to build our Data Sync service, we would love to get feedback on what we're doing to ensure we're solving the problems you really care about. Here is the MVP Technical Specification, which details what we've put together so far.

Feel free to comment on any of the our user scenarios or features in our PR and let us know if if we're missing anything!

@Zakeelm
Copy link
Contributor

Zakeelm commented Feb 4, 2019

Added information regarding our Token exchange service to our PR, which will serve as the foundation for security for Data Sync. This service will allow the exchange of an app secret + an optional AAD B2C token for a CosmosDB resource token.

@myokeeh
Copy link

myokeeh commented Feb 13, 2019

Is this to replace what used to be Azure Mobile Services with Offline Syncing using SQLite?

@RichiCoder1
Copy link

^ Same question. How does this compare to Azure Mobile Services?

@patniko
Copy link
Contributor Author

patniko commented Feb 18, 2019

@myokeeh @RichiCoder1 this won't replace Azure Mobile Services in the preview release, but it is our intent to build something those developers will happily transition to over the course of the year.

@fileman
Copy link

fileman commented Feb 19, 2019

The "CosmosDB" backend could be reachable from external application? (as example ASP.NET or WPF)

@Zakeelm
Copy link
Contributor

Zakeelm commented Feb 22, 2019

@fileman Yes, this is possible using the official CosmosDB SDK, but not the App Center SDK. You will need to implement authorization yourself as well to determine which users can read/write

@Zakeelm
Copy link
Contributor

Zakeelm commented Feb 22, 2019

We've updated our MVP Technical Specification to now include offline scenarios. We're going to do a basic "Store and Forward" implementation, which is outlined and defined in the updated spec.

In addition, we've also added mockups to our user scenarios! You can see a lot of the core user scenarios of the Data Sync service in these mockups. Feel free to comment on any of this and let us know your thoughts!

@patniko patniko closed this as completed Feb 28, 2019
@patniko patniko modified the milestones: February 2019, March 2019 Feb 28, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
plan item A piece of work planned for an iteration. storage
Projects
None yet
Development

No branches or pull requests

6 participants