Architecture

The classic implementation of the application persistence layer is ORM. Its advantages and disadvantages have long been known and described many times, for example, by Martin Fowler. In short, the main problem with ORM is that OOP objects describe the behavior of entities, while ORM attempts to work with the data inside them. However, the ORM lacks information about which class fields represent the entity’s state that needs to be saved. To provide this information, you must mark these fields or describe the persistence logic elsewhere in the code. Often, ORM is used incorrectly due to a misunderstanding of its specifics and the universal nature of its implementation. ...

Many years ago, when I was a first-year university student learning to program, I studied mostly on my own because the university course at that time didn’t offer anything new to me. I tried writing in Assembler, creating a graphical interface in Pascal, and even learned Prolog. I didn’t have access to the Internet at that time, and there weren’t many books on programming. This led me to believe that there was some secret knowledge on how to write programs correctly, and I just hadn’t found the right book. ...