hbpoison
commented
6 years ago Module Concept
Context
In the context of the whole software industry finishing this wave of technology rotation. I am quite excited to try integrating all of these new tools, architectures, methods to a whole new application life cycle.
Data Engine
SQL Database -> Object Database -> DataStore Service
Data Connectivity
SQL Interface -> Native Interface -> API (SOAP -> REST -> WebSocket -> GraphQL)
Response Model
Response on request -> Fixed time refresh -> Event driven
Application Logic / Support middleware
Native code -> Reusable module/library -> Micro-service
Front-end
Native/Static -> Dynamic -> Server side rendering
User State
Local -> Server -> Atom sync
UX Design/ Prototype Tools
Paper -> Image -> Pro software
Concept
Contenz suppose be a CMS module of the TeamZoon software ecosystem. It act as a micro-service to provide central control of all purpose contents use in any other modules, like website, blog, application, etc.
In order to achieve its functionality, there would be generally two main parts of contenz.
- A Content provider (API)
- A set of component/page generators for different use case
Features
- One central place to control all purpose contents for all nodes of business
- Easy to build up any kind of page from scratch
- Blade fast revealing with pre-fetched server rendering page nodes
- Seamless interaction, page updates push on event
- Low cost deployment
- full scalability
Module product concept will be added to README.md.