Improve 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 mer

Using 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 mer

Drawing 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 mer

More 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 mer

Domain 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 mer

Stressor 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 mer

More 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 mer

First 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

Todays reflections

Started the day listening to the Swedish podcast Kodsnack, where they talked about Barry‘s theories. They talked about the difference between complex and complicated, and stated that the software itself is never* complex. Code will always behave predictable (but definitely not always as predicted). I had a meeting this morning, with the developers, and only…

Läs mer

The naive architecture

My first instinct is that we need a frontend, an API and a database, but for this project I knew from the start that this wouldn’t be enough. A key component to the application is that Windows desktop application, that we need to scale. Containers came to mind early, and with that, the dreaded Kubernetes.…

Läs mer