Are infoblocks needed if there is EF for ASP.NET MVC?

Question

CMS

Greetings people.
I write my bike on ap.net MVC. Before that, I worked with Bitrix on php. In Birrix, I really liked the thing called infoblocks. So actually the question. Is it worth bothering with infoblocks if there is orm EF and with its help you can easily work with the database and not write api?
On the other hand, I don’t want to make tables for new data every time, but I want it to be possible to create a new entity from the admin panel.
Give advice.
And of course I want to hear the pros and cons of each of the approaches.
Thanks in advance. Sincerely yours asp.net junior developer.

Answer 1

EF is an ORM framework. Infoblocks in Bitrix are not just a wrapper for data access, but a higher level of abstraction. In particular, infoblocks: -
allow you to flexibly configure access rights
- create new blocks and properties in them "from the admin panel"
- have some kind of standard editor
But at the same time they are less flexible than their own database structure, and traditionally an additional level of abstraction does not add speed . In particular, the requests that Bitrix generates are often very suboptimal.
Answering your question: depending on what you need. These are not mutually exclusive entities, but entities of different logical levels. In particular, if you really want to implement infoblocks, then it makes more sense to work with the database using EF.