Keyboard shortcuts

Press or to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

Develop Cloud Based Tool

IMPORTANT: REFER BACK TO THE FUNCTIONAL, NON-FUNCTIONAL and SECURITY requirements

Development Workflow

Use Azure DevOps to capture all the tasks, split these into sprints, create milestones and report against those. Architectural design docs and so forth get published in the Azure DevOps wiki

TODO: add a Gantt chart here?

TODO: Everything uses IaC - WHY?! (do we even have to explain this? It’s 2026)

Challenges encountered

Publishing events

Publishing from a pipeline run to an accessible but secure endpoint

Event Design

No-SQL dashboard design

Azure DevOps security

Who can publish what to where? Is sending a CURL event from a pipeline even a good idea?

Azure Function and Function App debugging

Testing Methodology

In order to meet the non-functional requirements (speed, security) etc. a tester was assigned to the project TODO: research testing methodologies - perf, resource utilization, COSTS - not just security.

Is scalability an issue? Azure functions/function apps are inherantly scalable.

Resilience and recovery from failure

TODO: come up with a better title for this section.

Alternative architectures

Containers

Work is only going to be carried out on a per-change basis and with containers there’s actually ‘too much’ network/infra overhead to justify this. We’d need a queue anyway so… might as well go full serverless…

Hosted Server

Let’s not host a website - that’s so 2010’s now (Function Apps FTW!!)