Qunfei@Data, ML and AI Architecture

Define a set of guiding principles is an important first step of any strategy

—- Cloud Strategy from Gregor Hohpe.

1. Agile manifesto

We are uncovering better ways of developing
software by doing it and helping others do it.
Through this work we have come to value:

1. Individuals and interactions over processes and tools
2. Working software over comprehensive documentation
3. Customer collaboration over contract negotiation
4. Responding to change over following a plan

That is, while there is value in the items on
the right, we value the items on the left more.

https://agilemanifesto.org/iso/en/manifesto.html

3. 21 principles of enterprise architecture

Four categories of principles

• General principles
• Information principles
• Application principles
• Technology principles

General principles

1. IT and business alignment
2. Maximum benefits at the lowest cost and risk
3. Business continuity
4. Compliance with standards and policies
5. Adoption of the best practices for the market

Information principles

1. Information treated as an asset
2. Shared information
3. Accessible information
4. Common terminology and data definitions
5. Information security

Application principles

1. Technological independence
2. Easy-to-use applications
3. Component reusability and simplicity
4. Adaptability and flexibility
5. Convergence with the enterprise architecture
6. Enterprise architecture also applies to external applications
7. Low-coupling interfaces
8. Adherence to functional domains

Technology principles

1. Changes based on requirements
2. Control of technical diversity and suppliers
3. Interoperability

https://developer.ibm.com/articles/enterprise-architecture-financial-sector/

3. 6 pillars of AWS Architectured framework

1. Operational Excellence
2. Security
3. Reliability
4. Performance Efficiency
5. Cost Optimization
6. Sustainability

https://aws.amazon.com/cn/blogs/apn/the-6-pillars-of-the-aws-well-architected-framework/

4. The Twelve Factors

1. Codebase
   One codebase tracked in revision control, many deploys
2. Dependencies
   Explicitly declare and isolate dependencies
3. Config
   Store config in the environment
4. Backing services
   Treat backing services as attached resources
5. Build, release, run
   Strictly separate build and run stages
6. Processes
   Execute the app as one or more stateless processes
7. Port binding
   Export services via port binding
8. Concurrency
   Scale out via the process model
9. Disposability
   Maximize robustness with fast startup and graceful shutdown
10. Dev/prod parity
    Keep development, staging, and production as similar as possible
11. Logs
    Treat logs as event streams
12. Admin processes
    Run admin/management tasks as one-off processes

https://12factor.net/

5. Manifesto for software craftsmanship

As aspiring Software Craftsmen we are raising the bar of professional software development by practicing it and helping others learn the craft. Through this work we have come to value:

1. Not only working software, but also well-crafted software.
2. Not only responding to change, but also steadily adding value
3. Not only individuals and interactions, but also a community of professionals
4. Not only customer collaboration, but also productive partnerships

That is, in pursuit of the items on the left we have found the items on the right to be indispensable.

https://manifesto.softwarecraftsmanship.org/#/en