-
Notifications
You must be signed in to change notification settings - Fork 20
Orthogonal
Niels Braczek edited this page Dec 3, 2015
·
2 revisions
An orthogonal system is introduced, where two different kinds of components are distinguished:
- Vertical: Weblinks, Contacts, Users, Content, ...
- Horizontal: Versioning, translating, tagging, commenting, ...
Any horizontal component works with any vertical component out of the box being themselves agnostic about other components. This way, com_contact, com_weblinks, even com_users would automatically have ‘inherited’ tagging and versioning in 3.2 / 3.3 without the need to change a single bit of code in these components.
This approach allows any component to take advantage of new capabilities that are designed to be used across extensions. The orthogonal structure is a design supporting change.
Introduction
Development
Architecture
- Universal Content Model (UCM)
- Command Query Responsibility Segregation (CQRS)
- Database Abstraction Layer (DBAL)
- Dependency Injection (DI)
- Event Sourcing (ES)
- Filesystem Abstaction Layer
- Installer
- Data Definitions (JForms)
- Model-View-Controller (MVC)
- Orthogonal Component Structure (OCS)
- Routing
Features
Appendix