Skip to main content

Sistem stateless si sisteme stateful

By
Citeam un articol ce descria paraller programing. Si am ajuns la doi termeni care desi imi pareau cunoscuti nu imi erau foarte clar definiti.
Cei doi termeni sunt
  • stateless system;
  • stateful system;
Un sistem stateless este un sistem inchis, unde output-ul depinde doar de input si atata. Rezultatul obtinut nu este deloc influentat deloc de alte valori pe care sistemul le poate stoca intr-o forma sau alta.
In cazul acesta un exemplu ar putea sa fie:
Console.WriteLine(DateTime.UtcNow.ToString());
Oriunde pe glob ne-am afla si orice setare am aveam la masina( regional settings), valoarea returnata o sa fie aceiasi in orice locatie de pe glob. Acest sistem poate sa fie numit stateless din punct de vedere a regional settings.
Un sistem stateful este un sistem deschis, unde outpu-ul nu depinde doar de input. Pentru calcularea output-ului se i-au in considerare si alte valori. Poate fi vazut intr-o oarecare masura ca o masina de stari, care poate sa isi pastreze ultima stare.
Un bun exemplu este:
Console.WriteLine(DateTime.Now.ToString());
In functie de regional settings, o sa putem avea valori diferite afisate in zone diferite ale lumii, deoarece propietatea statica Now tine cont de regional settings.
Din punct de vedere a rularii in paralel, un sistem stateless este cel mai usor de implementat. Oricate thread-uri ar exista, acestea nu trebe sa partajeze/sincronizeze informatii. Fiecare isi poate face treaba cu input-ul pe care il are.
In cazul unui sistem stateful, programarea in paralel nu mai este atat de simpla. Pot sa apara cazuri cand mai multe resurse( stari ale masinii sau sistemului) sunt partajate intre mai multe theaduri, caz in care apare lucrurile se complica.
Labels:

Comments

Post a Comment

Popular posts from this blog

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

By
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(
Post a Comment
Read more

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

By
Today blog post will be started with the following error when running DB tests on the CI machine: threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See http://go.microsoft.com/fwlink/?LinkId=260882 for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration: TeamCity .NET 4.51 EF 6.0.2 VS2013 It see
8 comments
Read more

Navigating Cloud Strategy after Azure Central US Region Outage

By
 Looking back, July 19, 2024, was challenging for customers using Microsoft Azure or Windows machines. Two major outages affected customers using CrowdStrike Falcon or Microsoft Azure computation resources in the Central US. These two outages affected many people and put many businesses on pause for a few hours or even days. The overlap of these two issues was a nightmare for travellers. In addition to blue screens in the airport terminals, they could not get additional information from the airport website, airline personnel, or the support line because they were affected by the outage in the Central US region or the CrowdStrike outage.   But what happened in reality? A faulty CrowdStrike update affected Windows computers globally, from airports and healthcare to small businesses, affecting over 8.5m computers. Even if the Falson Sensor software defect was identified and a fix deployed shortly after, the recovery took longer. In parallel with CrowdStrike, Microsoft provided a too
Post a Comment
Read more