Syn framework 4.0 and sql server
4 likes1,848 views
The document provides an overview of building offline applications using the Microsoft Sync Framework, SQL Server, and SQL Azure, focusing on the advantages of offline architecture. It highlights the capabilities of the Sync Framework in enabling synchronization across various platforms, enhancing user experience through lower latency, and managing data access efficiently. Additionally, it outlines key components, participant types, and synchronization flow while encouraging developers to explore further through provided links and examples.
Syn framework 4.0 and sql server
- 1. Building Offline Applications using Sync Framework, SQL Server and SQL AzureEduardo Castro Martinezhttp://ecastrom.blogspot.comhttp://comunidadwindows.orgtwitter: edocastro
- 2. Session Objectives and TakeawaysObjectives:Learn about the advantages of offline application architecture Learn how to build offline applications to synchronize data across different client platforms using Sync Framework Learn about developer choice and interoperability for 3rd party endpointsKey Takeaway:Offline applications have lots of benefits comparing to online applications, especially for mobile devices and cloud services Sync Framework, SQL Azure and Windows Azure provide a data platform that makes it very easy to build offline applications and sync services.Sync Framework caters for offline clients on any client platform, and provides better end-to-end support for Windows, Silverlight and Windows Phone 7 clients.
- 3. Why Build Offline Capable AppsServer / ServiceOffline/Cached mode apps enjoy lots of value Client apps get better UX through Lower latency – data access doesn’t require round tripsHigher availability – app still runs if server is unreachableReduced network utilization – most data access is localServers gain better ability to schedule work asynchronouslyBenefits of cached mode are magnified on the InternetServer/service is further awayNetwork is less tuned/reliableRemote StoreSyncOffline ClientClient AppQuery / UpdateLocal Data Cache
- 4. LinksSync Framework 4.0 Downloadhttp://bit.ly/syncfr40 Developer Centerhttp://bit.ly/syncdev Sync SQL Server http://bit.ly/syncsql
- 5. Windows- SQL Server Express- SQL CompactEasy to develop the sync endpointsSync smarts on server, not on clientClient Offline AppsSyncEndpointsSyncFxClient APIsupportClient APIsupportSilverlightIsolated Storage - Other stores - Auth / Mgmt / Bus LogicSync ServiceSQL ServerWindows Phone 7Isolated Storage
- 6. Other storesSimple protocol(OData& Sync)Windows Server / IISCloudSyncWindows MobileSQL Compact - On-PremisesSyncEndpointsSyncFxBrowser / HTML5- HTML5 storesAuth / Mgmt / Bus LogicSQL AzureMinimal client & store requirementsiPhone / Any ClientSQLite / Any store - WindowsAzureSync Framework v4 Overview
- 7. Introduction to Microsoft Sync FrameworkMicrosoft Sync Framework is a comprehensive synchronization platform enabling collaboration and offline for applications, services and devices. Developers can build synchronization ecosystems that integrate any application, any data from any store using any protocol over any network.
- 8. Introduction to Microsoft Sync FrameworkA key aspect of Sync Framework is the ability to create custom providers
- 9. Included ProvidersDatabase synchronization providers: Synchronization for ADO.NET-enabled data sourcesFile synchronization provider: Synchronization for files and foldersWeb synchronization components: Synchronization for FeedSync feeds such as RSS and ATOM feeds
- 10. Participant TypesFull participants are devices that allow developers to create applications and new data stores directly on the devicePartial participants are devices that have the ability to store data either in the existing data store or another data store on the device.
- 11. Participant TypesSimple participants are devices that are only capable of providing information when requested. These devices cannot store or manipulate new data and are unable to support the creation of new applications
- 12. Core ComponentsA provider built using Sync Framework communicates with a data source and retrieves state information from a metadata store
- 13. Core ComponentsData SourceThe data source is the location where all information which needs to be synchronized is stored. Could be a relational database, a file, a Web Service or even a custom data source included within a line of business application. As long as you can programmatically access the data, it can participate in synchronization.
- 14. Core ComponentsMetadataAbility to store information about the data store and the objects within that data store with respect to state and change informationThe metadata for a data store can be broken down into five key componentsVersions KnowledgeTick count Replica IDTombstones
- 16. Conflicts are Detected and Resolved or DeferredSource Wins: Changes made by the local replica always win in the event of a conflict.Destination Wins: Remote replica always winsSpecified Replica ID Always Wins: No matter who changes an item, the replica with the designated ID always wins.Last-Writer Wins: Based on the assumption that all replicas are trusted to make changes and wall clocks are synchronized, allow the last writer to win.Merge: In the event of two duplicate items in conflict, merge the information from one into the other.Log Conflict: Choose to simply log or defer the conflict.
- 17. Sync Framework Database Synchronization
- 18. Always Connected major disadvantagesNetwork RequirementsData Access SpeedsSingle Point of FailureServer Scalability
- 19. Occasionally Connected Application (OCA)
- 20. Support data collaboration between databases
- 21. Database Synchronization and the Microsoft Sync FrameworkComprehensive synchronization platform that enables developers to add synchronization capabilities to applications, services, and devices. Sync Framework solves the problem of how to synchronize any type of data in any store using any protocol over any topology
- 24. HTML5iPhoneSyncSync ServiceSync+Windows Mobile 6.5 SyncWindows Phone 7SyncSummarySyncSilverlight
- 25. Offline applications on Silverlight desktop and Windows Phone 7
- 26. Offline Applications Architecture - ServerSilverlight Offline ApplicationSilverlight Offline ApplicationWindows Azure ApplicationCache ControllerOData Sync EndpointSyncOData Sync ProxyIsolated Storage ProviderBusiness LogicSQL AzureProviderSync LogicCollectionsIsolated StorageSQL Azure
- 27. Sync Service OverviewData StoreExpose data from SQL Azure or SQL Server HostHosted on Windows Azure or IIS/Windows ServerExposed using a WCF sync endpoint ProtocolExpose data for synchronization via a protocol and allow 3rd parties to build offline clientsFeaturesSupport business logic extensity Custom authentication / authorizationFiltering ToolingProvide a Tooling Wizard experience to configuring server and client
- 28. Offline Applications in Silverlight Silverlight Offline ClientSilverlight Offline ApplicationWindows Azure ApplicationCache ControllerOData Sync EndpointSyncBusiness LogicSQL AzureProviderSync LogicOData Sync ProxyCollectionsIsolated Storage ProviderIsolated StorageSQL AzureSync LogicSync Logic Moves to Server/Service
- 29. Enables Offline In Isolated Storage with Silverlight 3 & 4
- 30. Extensibility to allow 3rd party storage to be hooked in Offline Applications for all platformsOffline application on any platformSync ApplicationWindows Azure ApplicationOData Sync ServiceOData Sync ProxySyncBusiness LogicSQL AzureProviderSync LogicCollectionsStoreSQL AzureClient Needs To:Track changes on local store (samples for common stores).
- 31. Implement client side sync proxy (samples for common platforms)Offline Application on HTML5 across browsers
- 32. Offline Applications Architecture - Protocol Simple protocol (OData & Sync)Offline application on any platformSync ApplicationWindows Azure ApplicationOData Sync ServiceOData Sync ProxySyncBusiness LogicSQL AzureProviderSync LogicCollectionsStoreSQL Azure
- 33. OData Protocol & SyncApply the principals of OData to the problem of data-syncStandardize on protocol not on componentsMinimal client sync logic or algorithmsService manages sync keeping client simpleProvide samples to show how to consume protocol for any platformProvide components for richer experience in Silverlight& WP7Full interop details defined in SDK
- 34. SQL Azure Data Sync CTP1(Available now from http://azure.com)Sync End to End ScenariosOffline ApplicationsSyncSyncSyncSyncOn-Premises ApplicationsSyncSyncSyncSQL Azure DatabaseSyncSyncSyncMicrosoft Sync Framework 4.0 CTP available now! Retail & Remote OfficesSQL Azure Data Synchttp://azure.comSQL Azure Data Sync CTP2(Coming in near future)
- 35. Sync Framework – Offline SupportReleases and Roadmap
- 36. Sync Framework – Offline Support Call to ActionFor more information on Sync Framework 4.0 CTP MSDN Developer Center: http://msdn.com/sync/Try it outDownload “Sync Framework 4.0 October 2010 CTP” from Microsoft Download Center The sync service sample for Windows Azure or on-premises Client samples for Silverlight, WP7, WM6.5 & iPhone, HTML5Give feedbackScenarios to support, capabilities or feature requests, preview release problems, etc…
- 37. Building Offline Applications using Sync Framework, SQL Server and SQL AzureEduardo Castro MartinezArquitectohttp://ecastrom.blogspot.comhttp://comunidadwindows.orgtwitter: edocastro
- 39. © 2009 Microsoft Corporation. All rights reserved. Microsoft, MSDN, the MSDN logo, and [list other trademarks referenced] are trademarks of the Microsoft group of companies. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED, OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.