Meeting Notes (23.12.2014)

Meeting notes

Attendees: Andrija, Ofer, Ryan, Lior, Milos, Almog

State of 0.5

1. Db abstraction (for more info on this matter, consult Abstraction Layers and Engines). Abstraction layers for DB manipulation and the server instance (Express/Hapijs) still remain a proof-of-concept, but more work will be put on that side to support different DB systems and different application server frameworks.
2. Dependency injection. Currently the lazy-dependable performs this task in the ng branch, and the performance is still not an issue - especially with regards to possible optimizations in defining the dependency resolvers/consumers (prefer using the array notation over hardcoding the names of input parameters).
3. Aggregation changes. Aggregation is not a separate Core module any more, but a part of the Module Core module. Separating the Module handling from Aggregation was not a good software design choice ever. Finally these two software layers are put in the same logical unit - where they used to belong all the time.
4. Move to Object oriented. Andrija should post several Wiki pages describing the concept of using OOP techniques in order to turn mean.io into a framework.
5. "module" module. Now it supports the mean.json configuration file in terms of dependencies on other packages (another dependency mechanism that - now that lazy-dependable performs its job - seems quite redundant)
6. Performance boost (need to measure). Although an increase in speed of operation may be felt subjectively, measurement tests need to be built so that appropriate metrics may be taken on each further mean.io release. Tests need to include memory consumption tests paired with durability tests (measuring memory consumption and execution times on functions exposed by the mean.io Core and packages under heavy pressure/thousands of function calls)

What's missing

1. Decoupling the visualisations (ability to supply the front-end part as an optional package), which comes as a consequence of moving to OOP.

Notes

1. reduce use of scope. (Again an OOP based job)
2. Best practices standard - https://github.com/johnpapa/angularjs-styleguide - should be supported as much as possible.

ToDo

1. Profiling
2. Testing core
3. Security (get_config?)
4. Testing
5. mean.api Angular module that will introduce OOP for the client side