IntermediateAzure 305 project · about 12 hours

Data and application architecture

Design storage, database and app hosting for a web application with trade-offs.

The real-world brief

A retailer is moving its online shop to Azure.

What you will build

  • Options compared for hosting and data
  • A chosen architecture
  • A cost estimate
  • A proof of concept

Skills you will practise

Solution designData platform choicesCachingTrade-off analysis

Tools

Azure App ServiceAzure SQLAzure Cosmos DBAzure StorageAzure Cache for Redis

Project tasks

The detailed steps, checklists and trainer review open in the SOTT student portal for enrolled students.

1Options Steps in portal
2Design Steps in portal
3Build Steps in portal
4Cost Steps in portal

How companies use Azure 305

Travel: Staying online when a data centre fails. A booking site went down when one zone failed. The app was spread across zones with load balancing and managed databases. A later zone failure caused no outage.

Startup: Paying only for what is used. Servers sat idle most of the day. Event-driven parts moved to serverless functions and managed services. Monthly costs fell and scaling became automatic.

Manufacturing: Moving out of an old data centre. An ageing data centre needed costly hardware renewal. Workloads were assessed, grouped and migrated to the cloud in waves. The data centre closed on schedule.

Questions

Can I add the Data and application architecture project to my resume?

Yes. Once your trainer approves it, list it under Projects with the tools you used, one line on the problem it solves and a link to your repository and demo video.

How long does this project take?

About 12 hours of hands-on work, and it fits best after week 8 of the Azure 305 course.

Where do I get the step-by-step tasks?

Enrolled students get every task with steps, "done when" checks, the submission form and a trainer review in the SOTT student portal.