Core Development Principles

Appendix DMIA Development Principles

Design systems as highly modular and loosely coupled services.

Create flexible, independent components that can be easily combined, replaced, or updated, promoting adaptability and maintainability across the entire system.

Design systems' components with smallest blast radius in mind

Minimize the potential impact of failures by isolating and containing issues, ensuring that a single component's failure won't lead to widespread system disruption.

Build to support zero-downtime deployments

Implement strategies such as rolling updates, blue-green deployments, or canary releases to minimize disruption and downtime during application updates and maintenance.

Use distributed architectures

Leverage multiple nodes or clusters across different geographical locations to enhance resilience, fault tolerance, and availability of the system.

Expose services, including existing ones, through APIs

Facilitate seamless integration and interoperability between services by using well-defined, standardized APIs, enabling easy communication and data exchange.

Ensure automated testing is possible through good design

Develop systems that support test automation, ensuring robustness, reliability, and faster feedback cycles during development and deployment.

Design for cloud mobility

Create portable and cloud-agnostic solutions, making it easier to migrate applications and services across different cloud providers or on-premise environments if needed.

Prioritize open source

Opt for open-source technologies and platforms that offer flexibility, community support, and lower costs while encouraging collaboration and innovation.

Enforce service models in order of preference: SaaS, PaaS, IaaS

SaaS, PaaS, IaaS: Prioritize cloud services that offer the highest level of abstraction and management, reducing operational overhead and simplifying deployment.

Create reusable components that support accessibility

Develop modular, accessible components that can be easily reused across different projects, ensuring consistent user experiences and reducing development time.

Prioritize function over form without losing sight of elegance

Focus on building practical, efficient solutions that fulfill their purpose while maintaining a clean, user-friendly design.

Zero trust all the things -- assume breach perspective

Implement a security approach that assumes no trust by default, requiring continuous authentication and authorization for all users, devices, and services, minimizing the potential impact of security breaches.

🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧

Under Development

This wiki and the documents being developed under it are living documents.
They are all pre-decisional.
Some of these documents were generated using chatGPT or were developed by other organizations for reuse and adaptation.
Some of the documents in this wiki are in early early drafts, they make reference to things that do no exist or to process not yet being used.
The Center of practice(COP) is best effort and will be developed iteratively. This includes the technology supporting the COP
At the early stages of the COP expect change; short life cycles and rapid changes. Plan accordingly.
Stability in the COP will materialize over time.
For immediate reference engage your COP support channel, use the documentation as a secondary source.
There is reference to the COP and PDCP in the documentation, these are the same entity. We haven't picked a name yet :)

All of the pages in this wiki should be considered draft, underdevelopment and needing review. None of these pages are official documentation. All of the pages are a work in progress and discussion is encouraged via the GitHub issues mechanism.