Atitit.attilax's software architecture philosophy. docx

Atitit.attilax's software architecture philosophy. docx


1.7c
1.1. Crossplatform Cross-platform,
1.2 Cross device across devices,
1.3 Cross Archi across architectures (BS CS Hybrid)
1.4. Cross Lang across languages (UAPI)
1.5 Cross screen across different screens
1.6. Component Modular,
1.7. Cba, Cap+base+acid
2.6s
2.1. Scalable Extensibility
2.2. Secury
2.3. Solid
2.4. Service Component Servicing
2.5. Socail Community
2.6. SD (software defined concept. Software definition "(software Defined
3.5M
3.1. Meta define meta definition
3.2. Multifun Multifunction
3.3. Microservice Micro-Service
3.4. Multi Lang Multi-lingual
3.5. Mobile Mobility
4.4d
4.1. DSL
4.2. Pre-planning of DNA.
4.3. Distributed distributed
4.4. Deploy friendly deployment-friendly
5. Other
5.1. All in one full-system
5.2. Func base unit function-based units
5.3. Furps model
5.4 Green
5.5. H5,ui h5
5.6. Hybrid,
5.7. IOC containerized
5.8. Integration of integrate
5.9. i18n
5.10. Open SYS Opening system
5.11. Plugin plug-in
5.12. Platform of the platform
5.13. Process Customiz Flow Customization
5.14. Rest interface Rest
5.15. Text protocol Literals
5.16. Third Api
5.17. Tmork Input Mode
5.18. VM, Quarantine again encapsulation






1.7c


1.1.Crossplatform Cross-platform,
1.2.cross device across devices cross device,
1.3.cross Archi cross-Architecture (BS CS Hybrid)
1.4.cross Lang Cross-language (UAPI)
1.5.cross screen across different screens
1.6. Component Modular,
Two is not a module, the granularity of the better control


1.7.Cba, Cap+base+acid
Author:: ★ (Attilax) >>> nickname: Old wow Paw (full name:: Attilax Akbar Al Rapanui Attilaksachanui) Kanji name: Ayron, Email:[email protected ]
Reprint please indicate source: http://www.cnblogs.com/attilax/


2.6s




2.1.Scalable Scalability
2.2.secury
2.3. Solid
Service of 2.4.Service Components
2.5.Socail Community
2.6.SD (software defined concept. Software definition "(software Defined


SDH SD Hardware, SDS SD SYS,SDW SD World
SDN SD Network
Sde enterprice software-defined storage


Software-defined world, software-defined everything! Say why do we need software definitions? Where is the power of software definition?
The value of software is undoubtedly, if the hardware analogy to the body, then the software is the brain, is the mind, is the soul! The field that the body can reach is limited, but the extension of thought is infinite.
Because the ability of the hardware itself is limited, unlimited demand. So need SD.


For the software itself, it is necessary to re-abstract a layer, similar meta-design meta define






3.5M


3.1.Meta define meta definition
SD in Software interface
3.2. Multifun Multifunction
3.3.Microservice Micro-Service
With the previous SOA, a better approach:
3.4.Multi Lang Multi-lingual
3.5.Mobile Mobile
4.4d


4.1.Dsl
4.2.DNA Pre-planning.
No features to hide, but to reserve


4.3.distributed distributed
4.4.Deploy Friendly deployment-friendly
5. Other
Author:: ★ (Attilax) >>> nickname: Old wow Paw (full name:: Attilax Akbar Al Rapanui Attilaksachanui) Kanji name: Ayron, Email:[email protected ]
Reprint please indicate source: http://www.cnblogs.com/attilax/
5.1.All in one full-system
。 Avoid the core technology cowgirl in one aspect. Be sure to complete the system
5.2.Func base Unit function-based unit
5.3.FURPS Models
is function, ease of use (usability), Reliability (reliability), performance (performance), and Support (supportability)
First presented by Hewlett-Packard Company Robert Gredy Robert Grady and Caswell (Caswell)
5.4.Green Green
H5 of 5.5.h5,ui
5.6.Hybrid,


5.7.Ioc containerized
5.8.integrate Integration
By integrating not a


5.9.i18n
5.10.Open SYS Open System
5.11.Plugin Plug-in
5.12.platform Platform-based
5.13.Process Customiz Process Customization
Workflow and other Technology Realization decision table
5.14.Rest Interface Rest
Rpc>>rest
5.15.Text protocol Text


Text of protocol


5.16.Third Api


5.17.Tmork Input Mode
Touch Mouse remoter key (scan er, password reader, card reader)




5.18.Vm, isolate and encapsulate again
Because the common class library is flexible, the granularity is small. Can not be a common API large granularity, so it is easy to use.










The review of several popular concepts of OA system software _ Collaborative OA run-and-run observation. html

Atitit.attilax's software architecture philosophy. docx