Nordlicht Reisen GmbH, a fictional travel agency, has four tasks that do not need compute around the clock: the thumbnails of uploaded photos (G-06), a workflow for partner quota requests (G-05), the nightly export for sales and partners (G-10), and a large forecast calculation every two weeks. This lesson asks which serverless solution fits the first three and which service carries the forecast as batch processing.
Prior knowledge. What serverless means and how it is billed is covered in "AZ-900 compact, lesson 1.2." How developers build Functions is shown in "K3, lessons 3.13.1 to 3.13.4" (the plans and the costs are in "K3, lesson 3.13.4"), Container Apps for background work in "K3, lesson 3.5.7," and serverless as an architecture style in "K4, lesson 4.11.3." Which service fits which part of the application is covered in lesson 4.1 of this course; events and messages follow in lesson 4.5. None of that is repeated here.
The requirement
The requirements sheet uses the template from lesson 0.2 and the starting situation G-01 to G-10. All numbers are assumptions of the exercise. The parts are called T3 (nightly job, from lesson 4.1), T4 (thumbnails, from lesson 4.1), T5 (workflow for quota requests) and T6 (forecast calculation) here.
| No. | Requirement | Type | Metric | Weight | Source |
|---|---|---|---|---|---|
| 4.4-01 | T4 creates a thumbnail shortly after the upload (G-06). | Q | in under a minute; assumption | Should | Partner care |
| 4.4-02 | On campaign days, T4 handles ten times the uploads without servers of its own (G-09). | Q | no server around the clock; assumption | Must | Sales |
| 4.4-03 | T4 reads the storage account only over the private network. | R | no public address of the storage account; assumption | Must | Security |
| 4.4-04 | Partner care staff change the workflow T5 (request, approval, email to the hotel) without programming. | F | workflow changeable in a designer; assumption | Should | Partner care |
| 4.4-05 | The data of T5 does not leave the region germanywestcentral, not even for backup (G-08). |
R | no replication to a paired region; assumption of data protection | Must | Data protection |
| 4.4-06 | T3 is finished by 06:00 every night (G-10) and costs only while it runs. | F | about 90 minutes, two processor cores; assumption | Should | Sales |
| 4.4-07 | T6 computes 2,000 independent tasks of 20 minutes each in at most 8 hours. | Q | every two weeks; each task may be repeated; assumption | Should | Sales |
| 4.4-08 | T6 costs as little as possible. | K | cost drivers instead of an amount | Could | Management |
Cost frame. The ranking of the starting situation applies: costs fall before operating comfort, not before availability at peak load. Cost drivers are listed below; amounts are on the pricing pages.