Skip to main content

Cum putem sincroniza un director cu un blob din cloud.

Ieri am vorbit despre modalitatea prin care una sau mai multe instante de SQL Azure se pot sincroniza.
Astazi o sa incerc sa o ofer o solutie pentru cazul in care un client adauga in mod deconectat date pe blob, pe care noi vrem mai tarziu sa le le sincronizam cu blob-urile din cloud.
Problema: Se da un client care lucreaza cu date din blob-uri in mod deconectat. Se doreste ca la reconectare sa se sincronizeze cele doua storage-uri.
Ati spune simplu, ne apucam sa ne scriem un mecanism prin care sa putem sincroniza cele doua containere de date. Da, e si asta o varianta, dar oare merita sa implementam de la zero acest mecanism. Ati putea spune ca putem vedeam cele doua storage-uri ca si doua directoare si atunci sa folosim un mecanism de sincronizare a directoarelor. Suna bine, dar am o solutie mult mai curata - Microsoft Sync Framework.
Se bazeaza pe idea de a vedea cele doua storage-uri ca si doua directoare( partitii). Folosindu-ne de Microsoft Sync Framework putem sa sincronizam aceste date fara nici o problema.
  FileSyncProvider localfileSyncProvider = new FileSyncProvider(localPathName);
AzureBlobSyncProvider cloudSyncProvider= new AzureBlobSyncProvider(containerName, blobStore);
SyncOrchestrator syncOrchestrator = new SyncOrchestrator();
syncOrchestrator.LocalProvider = localfileSyncProvider;
syncOrchestrator.RemoteProvider = cloudSyncProvider;
syncOrchestrator.Synchronize();
Mai sus am dat un exemplu rudimentar la modul in care se poate face o sincronizare intre un directoru local si un blob folosindu-ne de acest framework. Ce mi-a placut pana acuma este ca nu mai este nevoie sa imi bat capul cum sa detectez modificările. Exista deja implementat un mecanism pentru acest lucru, iar in cazul in care dorim unul custom, putem cu usurinta sa inseram mecanismul nostru propriu.
Zilele astea o sa studiez acest framework si o sa revin cu alte posturi. O prezentare interesanta gasiti aici: http://www.microsoftpdc.com/2009/SVC23

Comments

Popular posts from this blog

How to audit an Azure Cosmos DB

In this post, we will talk about how we can audit an Azure Cosmos DB database. Before jumping into the problem let us define the business requirement: As an Administrator I want to be able to audit all changes that were done to specific collection inside my Azure Cosmos DB. The requirement is simple, but can be a little tricky to implement fully. First of all when you are using Azure Cosmos DB or any other storage solution there are 99% odds that you’ll have more than one system that writes data to it. This means that you have or not have control on the systems that are doing any create/update/delete operations. Solution 1: Diagnostic Logs Cosmos DB allows us activate diagnostics logs and stream the output a storage account for achieving to other systems like Event Hub or Log Analytics. This would allow us to have information related to who, when, what, response code and how the access operation to our Cosmos DB was done. Beside this there is a field that specifies what was th...

Cloud Myths: Cloud is Cheaper (Pill 1 of 5 / Cloud Pills)

Cloud Myths: Cloud is Cheaper (Pill 1 of 5 / Cloud Pills) The idea that moving to the cloud reduces the costs is a common misconception. The cloud infrastructure provides flexibility, scalability, and better CAPEX, but it does not guarantee lower costs without proper optimisation and management of the cloud services and infrastructure. Idle and unused resources, overprovisioning, oversize databases, and unnecessary data transfer can increase running costs. The regional pricing mode, multi-cloud complexity, and cost variety add extra complexity to the cost function. Cloud adoption without a cost governance strategy can result in unexpected expenses. Improper usage, combined with a pay-as-you-go model, can result in a nightmare for business stakeholders who cannot track and manage the monthly costs. Cloud-native services such as AI services, managed databases, and analytics platforms are powerful, provide out-of-the-shelve capabilities, and increase business agility and innovation. H...

Cloud Myths: Migrating to the cloud is quick and easy (Pill 2 of 5 / Cloud Pills)

The idea that migration to the cloud is simple, straightforward and rapid is a wrong assumption. It’s a common misconception of business stakeholders that generates delays, budget overruns and technical dept. A migration requires laborious planning, technical expertise and a rigorous process.  Migrations, especially cloud migrations, are not one-size-fits-all journeys. One of the most critical steps is under evaluation, under budget and under consideration. The evaluation phase, where existing infrastructure, applications, database, network and the end-to-end estate are evaluated and mapped to a cloud strategy, is crucial to ensure the success of cloud migration. Additional factors such as security, compliance, and system dependencies increase the complexity of cloud migration.  A misconception regarding lift-and-shits is that they are fast and cheap. Moving applications to the cloud without changes does not provide the capability to optimise costs and performance, leading to ...