Skip to main content

Cat de puternic trebuie sa fie un framework sau o tehnologie ca sa schimbe ceva?

Problema se pune in felul următor: ce trebuie sa contina un framework sau o tehnologie ca sa schimbe ceva si sa fie folosit la scara mare?
Pornim de la cazuri reale:
  • MEF nu a avut un impact foarte mare - este greu sa convingi lumea sa folosesca recomandările tale, mai ales ca in fiecare firma exista deja un framework ajutator;
  • EF nu a avut nici un impact major, NHibernate inca exista( NHibernate este deja un produs matur care a trecut de problema: ce a fost prima data. EF inca nu este un produs matur in totalitate, unele funcționalități inca lipsesc);
  • ASP.NET MVC a batut tot, proiecte de gen MonoRail au fost rase;
  • Prism - o aplicatie care a ajuns la o masa critica si incepe sa fie integrata de catre M$;

Exista proiecte care au nevoie de o masa critica pentru a reuși. De exemplu Oslo Project( cu limbaj M). Un proiect indraznet, in care M$ a investit foarte mult, dar din pacate a fost oprit. Acesta concureaza direct cu EF si nu a ajuns sa fie folosit atat de mult incat sa supraviețuiască.
Un lucru important este ca in ultimul timp M$ face parte din puținele firme care investesc bani in cercetare si vor sa aduca ceva nou pe piata( totul e marketing, dar avem si noi de castigat).

De ce am scris acest articol? Am fost implicat anul trecut într-un proiect care urma sa folosească limbajul M la baza unui DSL si am avut o mare dezamăgire sa aflu ca proiectul Oslo de la M$ a fost întrerupt. Daca s-ar fi ajuns sa se faca o implementare completa a limbajului M, s-ar fi ajuns intr-un moment critic, deoarece acest proiect are in momentul de fata cateva buguri destul de grele.

Comments

Popular posts from this blog

Why Database Modernization Matters for AI

  When companies transition to the cloud, they typically begin with applications and virtual machines, which is often the easier part of the process. The actual complexity arises later when databases are moved. To save time and effort, cloud adoption is more of a cloud migration in an IaaS manner, fulfilling current, but not future needs. Even organisations that are already in the cloud find that their databases, although “migrated,” are not genuinely modernised. This disparity becomes particularly evident when they begin to explore AI technologies. Understanding Modernisation Beyond Migration Database modernisation is distinct from merely relocating an outdated database to Azure. It's about making your data layer ready for future needs, like automation, real-time analytics, and AI capabilities. AI needs high throughput, which can be achieved using native DB cloud capabilities. When your database runs in a traditional setup (even hosted in the cloud), in that case, you will enc...

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

[Post Event] Azure AI Connect, March 2025

On March 13th, I had the opportunity to speak at Azure AI Connect about modern AI architectures.  My session focused on the importance of modernizing cloud systems to efficiently handle the increasing payload generated by AI.