🎬 Serie de videos
117 videos (micro-learning, español docente) · duración total estimada ~5h 18min. Cada short explica un concepto; hacé clic para leer el concepto en la wiki.
Concepts (23) · ~65 min
Section titled “Concepts (23) · ~65 min”| Video | Cap | Duración |
|---|---|---|
| What is software architecture? | 1 | ~2:55 |
| Who are the consumers of software architectures? | 1 | ~1:50 |
| Software product lines | 2 | ~2:50 |
| Domain-driven design | 3 | ~3:00 |
| Quality attributes | 4 | ~2:50 |
| Software architecture design | 5 | ~2:50 |
| The importance of software architecture design | 5 | ~2:45 |
| Greenfield versus brownfield software systems | 5 | ~2:40 |
| Architectural drivers | 5 | ~3:00 |
| Software architecture patterns | 7 | ~2:45 |
| Cloud-native applications | 8 | ~3:05 |
| Cross-cutting concerns | 9 | ~2:45 |
| Types of cross-cutting concerns | 9 | ~3:00 |
| The importance of performance | 10 | ~2:55 |
| Defining performance terminology | 10 | ~2:50 |
| Securing software systems | 11 | ~2:50 |
| Cryptography | 11 | ~2:50 |
| Identity and access management (IAM) | 11 | ~3:10 |
| DevOps | 13 | ~2:55 |
| Deploying to the cloud | 13 | ~3:05 |
| Legacy applications | 14 | ~2:55 |
| Soft skills | 15 | ~2:30 |
| Change is inevitable | 16 | ~2:50 |
Principles (9) · ~25 min
Section titled “Principles (9) · ~25 min”| Video | Cap | Duración |
|---|---|---|
| Why is software architecture important? | 1 | ~3:00 |
| Designing orthogonal software systems | 6 | ~2:55 |
| Minimizing complexity | 6 | ~2:55 |
| Following SOLID design principles | 6 | ~3:00 |
| General guidelines for cross-cutting concerns | 9 | ~2:50 |
| Secure by design | 11 | ~2:55 |
| Architecting for DevOps | 13 | ~2:55 |
| Lehman’s laws of software evolution | 16 | ~3:00 |
| Taking responsibility for your work | 17 | ~2:20 |
Patterns (11) · ~31 min
Section titled “Patterns (11) · ~31 min”Practices (28) · ~78 min
Section titled “Practices (28) · ~78 min”Techniques (11) · ~32 min
Section titled “Techniques (11) · ~32 min”| Video | Cap | Duración |
|---|---|---|
| Requirements elicitation | 3 | ~2:50 |
| Top-down versus bottom-up design approaches | 5 | ~2:55 |
| Implementing cross-cutting concerns | 9 | ~2:55 |
| Aspect-oriented programming | 9 | ~2:55 |
| Server-side caching | 10 | ~3:00 |
| Improving web application performance | 10 | ~3:05 |
| Database performance | 10 | ~3:05 |
| Threat modeling | 11 | ~3:00 |
| Creating architecture descriptions (ADs) | 12 | ~3:00 |
| DevOps toolchain | 13 | ~2:35 |
| Migrating to the cloud | 14 | ~2:55 |
Processes (9) · ~26 min
Section titled “Processes (9) · ~26 min”Quality Attributes (6) · ~17 min
Section titled “Quality Attributes (6) · ~17 min”| Video | Cap | Duración |
|---|---|---|
| Maintainability | 4 | ~3:00 |
| Usability | 4 | ~2:55 |
| Availability | 4 | ~3:05 |
| Portability | 4 | ~2:50 |
| Interoperability | 4 | ~2:40 |
| Testability | 4 | ~3:00 |
Roles (2) · ~6 min
Section titled “Roles (2) · ~6 min”| Video | Cap | Duración |
|---|---|---|
| What is the software architect role? | 1 | ~3:05 |
| Types of software architects | 2 | ~3:00 |
Checklists (1) · ~3 min
Section titled “Checklists (1) · ~3 min”| Video | Cap | Duración |
|---|---|---|
| Most common web application security risks | 11 | ~3:15 |
Chapter Summaries (17) · ~31 min
Section titled “Chapter Summaries (17) · ~31 min”| Video | Cap | Duración |
|---|---|---|
| Summary | 1 | ~1:45 |
| Summary | 2 | ~1:45 |
| Summary | 3 | ~1:40 |
| Summary | 4 | ~1:45 |
| Summary | 5 | ~2:15 |
| Summary | 6 | ~1:35 |
| Summary | 7 | ~1:40 |
| Summary | 8 | ~1:55 |
| Summary | 9 | ~1:50 |
| Summary | 10 | ~1:50 |
| Summary | 11 | ~1:45 |
| Summary | 12 | ~2:20 |
| Summary | 13 | ~2:20 |
| Summary | 14 | ~1:45 |
| Summary | 15 | ~1:45 |
| Summary | 16 | ~2:05 |
| Summary | 17 | ~1:45 |