Magento’s (1+2) EAV (Entity-Attribute-Value) database model allows too much redundant data. This leads to an unusual large database and strains errors when working with that data in the backend. Taking care of the shop content is for most merchants a pretty huge task. In this post I would like to propose an overall fix to this problem with backwards incompatible changes to the database structure.
Statistics about Magento2 lines of code, comments and used languages. Updated from time to time and compared with different versions.
Ever wanted to send emails from your static website without depending on 3rd party services? Meet the mailout middleware for Caddy Server!