In the last decades the management of large amount of data became a necessity. The needs were not only to store data but also to get quick access to it: the database and the database management system (DBMS) were born. In the last years Microsoft brought to the market a different way to approach data: Entity Framework.
In StarMe.io Entity Framework helps us to focus on the meaning of the data and not only on the technology needed to store it.
StarMe.io manages data, a lot of data!
Every single drop of information you see on the screen have a special meaning for us. Collecting large amount of data is like putting a lot of things in the closet… If you don’t take care of what you are storing it will be difficult to retrieve this or that shirt when you need it… So shaping data is like designing a closet… The dressing style of the customer changes the shelves and the drawers inside the closet.
Relational database speaks a language where the most meaningful words are: tables, attributes, keys and relationships. In this design level of the application you have to focus on the shape of the container of data. All the elements of the database shall be than converted in logic structure that fill the business logic layer of the application.
This was due to the procedural programming used in the past that found in the relational databases its natural companion for data storage.
Today the object oriented programming model is the mainstream for a lot of application, including StarMe.io. ORM (object to relation mapper), like Entity Framework, let designers and developers speak about “classes” and “objects” also for storing and retrieving data from the database.
Therefore, the process to translate an object’s data into table’s data and vice versa is accomplished by the Entity Framework.
With Entity Framework we can look at the data we are modeling always as classes and object focusing on what is meaningful for the user. Developers can write less code and designer can “forget” the limits of tables and relationships for a while.
StarMe.io is looking at data from the operator perspective: the meaning of the knowledge we store is way more important than the single data we need to store.
Theory of relational databases provides us solid rock rules like “normal forms”. But it’s not enough: good data design requires experience!
Good or bad designs are not universal principles: something that looks good in a project may look bad in another. Boundaries and requirements define the model. StarMe.io model is flexible and extensible!