Skip to main content

I. Windows Azure - prezentare generala

In urmatoarele saptamani o sa scriu o serie de posturi despre Windows Azure. O sa prezint pe scurt notiunile generale, impreuna cu exemple unde o sa fie cazul. Postarile nu o sa fie una dupa alta, dar o sa incerc ca macar doua posturi pe saptamana sa fie pe aceasta tema.
Iar acuma sa trecem la subiect.

Ce reprezinta cloud computing? Reprezinta un set de servere interconectare intre ele unde dezvoltatorii pot sa:
  • Instaleze si sa ruleze servicii;
  • Sa stocheze si sa acceseze informatii;
Windows Azure reprezinta o platforma de servicii pentru cloud oferite de catre Microsoft. Aceste servicii sunt oferite prin data centerele din toata lumea, prin intermediul cărora se ofera o metoda simpla, sigura si puternica pentru a crea aplicatii web si servicii.
Windows Azure este un sistem de operare creat special pentru cloud. Este de fapt un Windows 2008 Server fara interfata grafica la care au fost adaugate si alte functionalitati. Ca si o curiozitate, acest sistem de operare poate sa se instaleze si sa porneasca in mai putin de 10 secunde.
Dezvoltatorul poate sa dezvolte intr-un mediu sigur o aplicatie, sa o hosteze si sa faca management pe ea, fara sa isi puna probleme precum ce diferente exista intre sisteme de operare sau modul in care trebuie instalat sistemul de operare.
Daca sunteti curiosi sa vedeti cum arata un data center, va invit sa vizualizati urmatorul filmulet:
How a data center look like.
Beneficiile care le aduce Windows Azure sunt:
  • Scalabilitate instant;
  • Scalabilitate pe orizontala aproape nelimitata;
  • Spatiu de stocare care poate sa fie extins in orice moment;
  • Managment la aplicatie si resurse;
  • Downtime aproape 0 absolut;
  • Low-friction provisioning;
  • Deployment se poate face in orice moment si dureaza doar cateva minute;
  • La deployment in orice moment se poate revenit la versiune anteriora aproape instant;
  • Licentiere soft = 0, nu este nevoie sa cumparati licenta pentru Windows Azure sau SQL Azure;
  • Solutie de racire si de administrare a serverelor;
  • Securitate;
Ce ne ofera Windows Azure:
  • SaaS: Software ca si serviciu;
  • PaaS: Programele ca si serviciu;
  • IaaS: Infrastructura ca si servciu;
Pe scurt, cand folosim Windows Azure platim exact ce folosim in acel moment si atat. De exemplu putem sa platim pentru 3 instante computationale, apoi pentru doua ore sa crestem la 30 de instance, iar apoi sa revenim la 3 instante. O sa platim cele 30 de instante doar pentru cele 2 ore si atat. Prin acest mod, avem o granulatie mult mai fina pentru scalabilitate, putînd sa controlam de la numarul de instante si puterea acestora, ca capacitatea de stocare.
Toate aplicatiile ruleaza independent, iar in cazul in care o instanta cade, ea o sa fie preluata automat de catre o alta instanta, nici un request nu se pierde, iar clientul nu sesizeaza ca s-a intamplat ceva.
Trebuie stiut ca in orice moment, informatia exista in trei copii separate. Fiecare copie este pe o masin diferita, astfel se reduce aproape la minim riscul ca informatia sa se piardă. Doar in cazul unui 11/9 aceste date se pot pierde din nou.
Cand sa folosim Windows Azure? Cand avem nevoie sa dezvoltam o aplicatie pentru nevoile si cerinte zilei de maine, nu de astazi. Nu trebuie doar sa dezvoltam o aplicatie, trebe sa oferim si un mediu unde aplicatia poate sa se extinda si sa creasca.

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...

Can User Technical Profile Influence AI Architecture Decisions?

In the last few days, I ran a small experiment on Devin/Windsurf/Cascade, BMAD, and LLM-based architecture decisions. The initial concern was simple: if an AI coding assistant knows something about the user, for example, that the user is a Java developer or a .NET developer, can this information influence the architecture and technology stack that the AI will propose? This question is important because many companies are starting to use AI tools not only for coding but also for product discovery, architecture, documentation, and technical decision-making. If the AI is influenced by the developer's personal profile, the result may not be fully neutral. It may look like a business or architecture decision, but in reality, it may be partially shaped by the context of the person using the tool. The test was done using BMAD with Devin/Windsurf/Cascade. The scenario was a unified field service operations platform. The task was to let BMAD refine the product, define the architecture and s...

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

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...