Your browser is blocking local storage, so your progress will be lost when you close or reload this page.

How software is organised, hosted and split into parts.

Topics

• Separation of ConcernsExpected level: Working

  Organise software by responsibility.

  Not reviewed
• Layered ArchitectureExpected level: Working

  Common ways to structure an application.

  Not reviewed
• Modularity, Coupling, and CohesionExpected level: Working

  Design parts that can change independently, and the trade-offs involved.

  Not reviewed
• Servers, VMs, and ContainersExpected level: Awareness

  How servers, VMs and containers differ, and why each exists.

  Not reviewed
• Cloud ConceptsExpected level: Awareness

  Regions, availability, scalability and managed services.

  Not reviewed
• Design Patterns OverviewExpected level: Awareness

  Recurring solutions to common design problems.

  Not reviewed
• Distributed Systems BasicsExpected level: Awareness

  Challenges when applications communicate over networks.

  Not reviewed

Self-assessment

You should be able to do each of these without help.

• Explain separation of concerns using an example. Show how mixing two responsibilities in one place makes a change harder.Related: Separation of Concerns
• Describe the layers of an application and what each is responsible for. Say where validation, business rules and database access belong, and why.Related: Layered Architecture
• Describe what a module is responsible for in one sentence. Point out a sign of low cohesion or tight coupling, and say how you would reduce it.Related: Modularity, Coupling, and Cohesion
• Describe the difference between a VM and a container. Say what each one isolates, how heavy it is, and when you would choose it.Related: Servers, VMs, and Containers
• Explain what to do when a call to another service times out. Describe a retry with a limit and a delay, and why a retried payment must not be charged twice.Related: Distributed Systems Basics