Skip to main content

AppFabric Cache - more than one writers in the same time

Intr-un post anterior am discutat despre AppFabric Cache, care are la baza mecanismul de DataCache pentru Windows Cache Server. Intr-un mediu in care avem mai multe masini care scriu pe acelasi cache trebuie avuta grija destul de mare la urmatorul caz:
In acelasi timp 2 sau mai multe masini doresc sa scrie acelasi element in cache( aceiasi cheie).
Cuvantul cheie la aceasta problema este "IN ACELASI TIMP". In mod normal am avea urmatoarea implementare pentru a scrie un obiect in cache:
DataCacheFactory cache = new DataCacheFactory();
cache.Put(key,value);
Totul ar functiona fara nici o problema pana cand 2 sau mai multe instante ar incerca sa scrie in acelasi timp un element cu aceiasi key in cache. In acest caz se arunca o exceptie de tip DataCacheException, cu error codul setat DataCacheErrorCode.RetryLater.
Pentru a rezolva aceasta problema avem doua solutii, in functie de cat de probabil e sa apara un astfel de caz putem sa folosim una din solutii, sau o combinatie din cele doua.
Prima solutie ar fi sa me folosim de mecanismul de lock care exista pentru cache.
DataCacheLockHandle lockHandle;
var value = cache.GetAndLock(key, TimeSpan.FromSeconds(1), out lockHandle, true);
cache.PutAndUnlock(key, value, lockHandle);
Avantajul la aceasta solutie este ca inainte sa se faca scrierea se face un lock explicit pe obiectul din cache, dar trebuie avut grija ca fiecare aplicatie care foloseste cache-ul sa foloseasca metode care fac lock - in caz contrat obiectul poate sa fie accesat chiar daca s-a facut lock pe acesta. Un alt dezantaj la aceasta solutie este ca trebuie facute doua requesturi la server. Unul care face GET si altul care face PUT si totodata in cazul in care se intampla ceva intre GET si PUT obiectul din cache poate sa ramana blocat din cauza lock-ului pe care il facem( trebuie sa ne implementam un mecanism de fallback.
Urmatoarea solutie pe care o propun este mult mai primitiva, dar care conserva atat conexiunea la internet cat si durata cat timp obiectul este blocat.
int retrys=5;
while(true)
{
     try
     {
          cache.Put(key,value)
     }
     catch(DataCacheException ex)
     {
          if(ex.ErrorCode == DataCacheErrorCode.Retrylater)
          {
               if(retrys <= 0)
               {
                     throw;
               }
               retrys--;
               continue;
          }
          throw;
     }
}
In cazul in care acest caz nu o sa apara foarte des as alege a doua varianta. Este mult mai simpla si mai sigura. Cand folosim a doua varianta trebuie sa avem grija daca exista si alte aplicatii care acceseaza cache-ul nostru - toti consumatorii trebuie sa foloseasca mecanismul de lock, deoarece altfel nu ar avea nici o valoare modul in care scrim noi in cache.


Comments

Popular posts from this blog

Windows Docker Containers can make WIN32 API calls, use COM and ASP.NET WebForms

After the last post , I received two interesting questions related to Docker and Windows. People were interested if we do Win32 API calls from a Docker container and if there is support for COM. WIN32 Support To test calls to WIN32 API, let’s try to populate SYSTEM_INFO class. [StructLayout(LayoutKind.Sequential)] public struct SYSTEM_INFO { public uint dwOemId; public uint dwPageSize; public uint lpMinimumApplicationAddress; public uint lpMaximumApplicationAddress; public uint dwActiveProcessorMask; public uint dwNumberOfProcessors; public uint dwProcessorType; public uint dwAllocationGranularity; public uint dwProcessorLevel; public uint dwProcessorRevision; } ... [DllImport("kernel32")] static extern void GetSystemInfo(ref SYSTEM_INFO pSI); ... SYSTEM_INFO pSI = new SYSTEM_INFO(

Azure AD and AWS Cognito side-by-side

In the last few weeks, I was involved in multiple opportunities on Microsoft Azure and Amazon, where we had to analyse AWS Cognito, Azure AD and other solutions that are available on the market. I decided to consolidate in one post all features and differences that I identified for both of them that we should need to take into account. Take into account that Azure AD is an identity and access management services well integrated with Microsoft stack. In comparison, AWS Cognito is just a user sign-up, sign-in and access control and nothing more. The focus is not on the main features, is more on small things that can make a difference when you want to decide where we want to store and manage our users.  This information might be useful in the future when we need to decide where we want to keep and manage our users.  Feature Azure AD (B2C, B2C) AWS Cognito Access token lifetime Default 1h – the value is configurable 1h – cannot be modified

What to do when you hit the throughput limits of Azure Storage (Blobs)

In this post we will talk about how we can detect when we hit a throughput limit of Azure Storage and what we can do in that moment. Context If we take a look on Scalability Targets of Azure Storage ( https://azure.microsoft.com/en-us/documentation/articles/storage-scalability-targets/ ) we will observe that the limits are prety high. But, based on our business logic we can end up at this limits. If you create a system that is hitted by a high number of device, you can hit easily the total number of requests rate that can be done on a Storage Account. This limits on Azure is 20.000 IOPS (entities or messages per second) where (and this is very important) the size of the request is 1KB. Normally, if you make a load tests where 20.000 clients will hit different blobs storages from the same Azure Storage Account, this limits can be reached. How we can detect this problem? From client, we can detect that this limits was reached based on the HTTP error code that is returned by HTTP