Architecture Guiding Principles
These principles guide our ambitions for how we intend to design, build, scale, and evolve the system landscape across the Computational Sciences Center of Excellence (CS CoE). They reflect our shared architectural commitments and guide the direction we collectively agree to pursue; deviations should be reviewed through the exception process to ensure consistency and good decision-making.
Each principle includes a Description (what we commit to), a Why (the underlying rationale), and an Impact (the outcomes we expect when we apply it effectively).
1. Principle: Start with Business Impact – Deliver, Measure, and Scale What Works
1.1. Description
We begin by aligning our deliverables to the business objectives defined by the REDs. We deliver iteratively, incorporating continuous customer feedback, and validate our outcomes against the business’s success criteria, scaling only what creates proven value.
2. Principle: Design for Reuse – Modular and Integration-Ready by Design
2.1. Description
We prioritize reuse by evaluating existing solutions, starting with open-source products, then commercial off-the-shelf solutions, and only considering building from scratch as a last resort, while articulating the architectural rationale when reuse is not viable. Evolving towards modular, loosely coupled, and interoperable components that can be reused and composed ensures accelerated delivery across domains.
2.2. Why
Reusability mindset reduces duplication and improves ROI, while modular design enables agility, interoperability, and long-term scalability.
2.3. Impact
-
Faster delivery with the flexibility to adjust and iterate as needs evolve.
-
Reduction of duplicated systems and fragmented tooling - more harmonized landscape.
-
Independent evolution of services, enabling easier deprecation and consolidation
-
Greater consistency and architectural coherence data across teams and domains
3. Principle: Innovate at the Core
3.1. Description
We strive for applying cloud where it makes sense, i.e. cloud-first, cloud-native, SaaS-first, AI-enabled, API-driven architecture that enables rapid innovation and scalability. * Cloud-first means we prioritize the cloud, but are not cloud-only. * Cloud-native means we leverage cloud-providers specific capabilities as an accelerator, rather than being cloud agnostic. * AI-ready means we increasingly embed AI into how we design, build, operate and govern our systems, while also ensuring our systems are AI-ready.
| While our current state does not yet fully achieve this principle, this is the direction we are intentionally moving towards. |
4. Principle: Automate for Scale with Embedded Observability
4.1. Description
We automate repeatable, manual, labor intensive work across infrastructure, applications, data, and processes to scale reliably. We design systems with built-in observability, which includes usage monitoring of applications, so we can continuously debug, understand, and improve them. Our scientific stakeholders rely on our solutions and data, making it essential to build and maintain their trust - critical for the ultimate outcome: delivering medicines faster to patients.
5. Principle: Collaborate to Elevate
5.1. Description
We collaborate, communicate transparently and share knowledge, designs, code, and decisions to achieve collective outcomes and foster trust. We will work in the open (e.g. documented designs and code, documented decisions, peer reviews) and ensure artifacts are searchable. This is critical as we create the CS CoE organization, and we bring together different cultures, geographies, ways of working, approaches, and strengths.
6. Principle: Secure & Compliant by Default
6.1. Description
We embed security, privacy, and compliance into every design — not as an afterthought - in alignment with Roche corporate guidelines. This includes patient data, licensed/purchased data with contractual restrictions, and data subject to geographic or jurisdictional regulations. At the same time, we design access models that enable appropriate, governed sharing.
7. Principle: Design for Resilience and Adaptability
7.1. Description
We architect solutions with modularity and flexibility, embedding fault tolerance as a core design tenant. In research and early development, our business priorities shift rapidly, data modalities evolve, and workflows and technologies are constantly changing and improving. Our systems must keep pace with this and scale, pivot, or recover without major redesign.
7.2. Why
In gRED and pRED, business priorities, technologies, and regulatory landscapes continuously evolve. Systems that cannot adapt quickly or recover gracefully from disruptions slow down innovation, productivity and increase operational risk.
7.3. Impact
-
Lower cost for adapting to rapid changes to business processes
-
Higher uptime and resilience during scientific experiment cycles that cannot be disrupted or delayed
-
Reduce downtime, minimizes cost of change
-
Ensures technology investments remain relevant and dependable even under constant evolution
8. Principle: FAIR Data By Design
8.1. Description
We ensure all systems, applications, pipelines, and processes are designed to enable Findable, Accessible, Interoperable, and Reusable (FAIR) data from creation through consumption. Data is core to everything we do in the CS CoE.