ArchStream

I’ve already covered the flows I find interesting. The rest of the flows are basic flows that follows the same pattern. I’ll not cover all of them individually since they all have the same architecture and failure modes. The middlewares are already documented, and the basic flow is a request comes in from the Frontend,…

It’s not Monday Night Football, it’s Monday Night FMEA. Well, I’m behind on documenting and need to work on a monday night. No biggie. We’re doing the FMEA on the Report Generator now. I wrote about this in an earlier post, but not from a FMEA perspective. One thing this architecture handles, that the previous…

Let’s have a look at how we start a crawl. Not enough free vCores to start a container.Since we know this can, and most likely will, happen, we’re doing a check before even showing the “Start Crawl”-button. If not enough resources are available, we show a message to the user stating current high demand. If…

I’m learning a lot from this project, and most of all how hard it is to keep up with the documentation. Initial priority was hitting the market, and making the first customer. It was later changed to showing the product to investors, and then back to making customers again. In only two months. I’m having…

Figured the FMEA needs to be done on my flows rather than on my components, to better visualize the issues. I’m doing the login flow first. AuthProvier isn’t available, or can’t be reached due to a network problem.This would cause the login to fail, and stop the user from using the system.This is detected by…

Microsoft Entra ID Failure Modes: Google Authentication Failure Modes: Crawl Container Instance(s) Failure Modes: Report Generator Container Instance(s) Failure Modes:

Only two days ago I wrote about deciding to rewrite the Report Generator to be an Azure Function rather than a container. Today, I changed my mind. The issue we want to solve, primarily, is that generating a report takes too long. Secondary we want to get rid of the LibreOffice dependency. Turns out, the…

Putting together a multi-tenant cloud application with dependencies to external services and a Windows desktop application isn’t easy. And the cost-tools provided, well let’s just say they’re not really on the spot. One of our resources was listed as “about $6 per month”, but is actually close to 1000 SEK ($95, give or take) per…

Time to do a STRIDE threat analysis on the system. STRIDE stands for Spoofing, Tampering, Repudiation, Information disclosure, Denial of service and Elevation of privilege. Let’s talk about them one at a time. First, let’s look at the application infrastructure. We have an Angular frontend, hosted as a Static Web App in Azure, and we…

This week we addressed the fact that, by default, Azure only allows you to allocate 10 vCores per region. Each Container Instance needs one or more vCores, making it limiting the number of Container Instances we spin up. Another issue with the original architecture is that whenever we start a Container Instance, with the desktop…