Posts by Stefan Bergfeldt
Cloud isn’t easy
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…
Läs merAin’t nothin’ gonna break my stride
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…
Läs merImprove the architecture
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…
Läs merUsing the stressor analysis to rate flows
We have a central flow in the system, the generate report flow, that’s quite interesting from an architectural perspective. The report is generated in the desktop application given to us, and using a Windows desktop application in a Cloud environment is, let’s say interesting. I’ve designed three different versions of the flow, calling them A,…
Läs merDrawing flow charts
So I’ve started drawing some flows with more detail. First out is the login flow. We needed this because we started talking about what would happen if one User would need access to more than one Agency. With the decision based on Agencies Count, I got some UX design included in the architecture. We do…
Läs merMore stressors
The title of this post is “More stressors”, since I’ve already done an initial Stressor analysis. I’ve realized two things, the initial stressors aren’t random enough and also I’ve deliberately skipped stressors that my current idea of architecture will hold for. Both are obviously mistakes on my part. This is my attempt to fix it,…
Läs merDomain Language Vocabulary for SEO SaaS
We’ve already had confusions in the team, based on what we call things. I decided we need a vocabulary, and here is the first version. AgencyAn organization or company that provides SEO services to multiple clients using the platform.CustomerThe paying entity or organization that purchases the SaaS service, typically the SEO agency itself.ClientThe end business…
Läs merStressor analysis
Why did I decide to do my Arch Stream in English when the project is in Swedish, Swedish is my native language, all my colleagues and the client is Swedish, and Barry, tho not Swedish, is fluent? Oh well, practicing my English is also useful I guess. I’ve been thinking about some stressors, and figured…
Läs merMore flows
I’ve drawn two more flows, that’s related to each other. The first is when the user gets the result of a crawl (crawl flow described here). From the frontend, the user clicks a link to show the results from a crawl (results are shown per site). As shown in the graph, this is a really…
Läs merFirst flow chart
So I’ve finally drawn my first flow chart, and I must say I really love having a large whiteboard in my home office. Today I realized why it’s so hard for me to draw this. I see improvements all over the place, and why would I want to draw something I “know” could be better.…
Läs mer