This document contains the Architecture Plans for FY20 (July 2019 -> June 2020)
...
Expand |
---|
Upgrades: Foundation for sustainable upgrades; Django2, Python3 Outcomes from doing upgrades: (1) Enable quality engineering with up-to-date technology standards, (2) avoid potential security risks by using only supported versions of the technology. Outcomes from having a foundation for sustainable upgrades: (1) Proactively keep the platform up-to-date with intentional resourcing and outsourcing, (2) Engineers who are focused on other critical functions are not interrupted for emergency upgrade situations. Plans: Foundation for future upgrades Empower multiple upgrade teams Automated reports on upgrade issues and deprecation warnings Standardize repos: OEP-2 (repo metadata) and OEP-18 (dependency tools)
Django: Django 2.2 Upgrade Plan Python-3: partner support of Code Jail upgrade Elastic-Search: cross-team discovery and alignment
Technical Ownership & Observability: Empower teams to be proactive business-aligned Tech Owners Outcomes: (1) Proactively and efficiently respond to user-facing issues that impact business metrics, (2) empower teams to make strategic technical decisions for the business features that they own, (3) empower teams to maintain and upkeep their own technologies according to agreed-upon SLOs. Plans: Owners assigned to teams for all repos. Owners assigned to teams for all apps in edx-platform. Develop and communicate ownership rollout plan Empower shared owners of edx-platform Define boundaries; define core versus extensions; define content versus features. With Alerting, Observability, etc.
Deprecation & Removal: Speed up development in inter-service authentication Backend Efficiency & Clarity: Initial plans to speed up & clarify backend development Outcomes: (1) Speed up backend development, (2) reduce and stabilize a defined core, (3) clarify architectural principles and vision. Plans: Design Sprint exercises to Tame the Monolith (docs, linting, tests, APIs, real-time eventing, decoupling, ???)
|
...
Expand |
---|
Upgrades Observability & Ownership Outcomes: (1) Proactively and efficiently respond to user-facing issues that impact business metrics, (2) empower teams to make strategic technical decisions for the business features that they own, (3) empower teams to maintain and upkeep their own technologies according to agreed upon SLOs. Ownership Plans: Clarify the granularity of Ownership Assignment (OEP-2 update) Comprehensively assign ownership to all edX technologies (code repositories), using business-aligned terminologies.
Deprecation & Removal of Old Superceded Implementations Micro-frontend (MFE) Runways |
FY20 Q1 (July 2019 → Sep 2019)
...