Objective
We meet every 3 weeks (off-weeks of Python Study Group and Frontend Study Group) to collectively learn about edX architecture principles and how to put them into practice in our daily engineering.
Why?
Each of us is an architect of every line of code we write, every module and abstraction we build, and every system component and service that we design. This study group allows us to learn from our past mistakes, learn from practices emerging from industry-wide experiences, and collectively align and develop our own architectural principles to follow at edX. Anticipated outcomes of edX intentional architecture include (1) sustainably accelerated development (2) improved developer engagement and (3) a more robust teaching and learning (Open) edX platform.
What?
We will begin by collectively writing and understanding more deeply the architectural principles proposed in Architecture Manifesto (WIP) (and maybe Architecture Principles (WIP)).
Schedule
Date | Topic | Presenter | Links |
|---|---|---|---|
| Data Redundancy beats Coupling across Distributed Services | ||
| Extensions beat Core Modifications | ||
| Extensions beat Core Modifications, extended | ||
| DDD Bounded Contexts beats Shared Business Logic | ||
| Domain-Driven Design | ||
| Bounded Autonomy beats Coordination | ||
Requested Topics
Loosely Coupled beats DRY