Architecture
Architecture is the path a request takes — not the logos on the slide.
August 23, 2026 · BytePresence
Frontend, backend, Docker, AWS, Kafka, and SEO are not separate products. They are rooms on the same path. If you cannot walk a click from the browser to the disk and back, you have a shopping list.
Photo: Scott Graham, via Unsplash
Most “architecture” conversations are a shopping list. React on the frontend. Node behind it. A database for the record. Redis if it has to feel instant. Docker so it runs the same way twice. AWS because that is where the machines live. Kafka when someone says scale. SEO as a leftover checklist after the site is already a single-page app.
That is a bill of materials. Architecture is what happens when a person taps Buy — or when Googlebot asks for the same URL. One request. Several rooms. If you cannot walk it, you do not have a system. You have tools.
Walk it once. The browser asks for HTML. A CDN or the origin returns the frontend. The page calls an API. The API checks who they are, applies the rules, reads or writes a database. Work that can wait — mail, search index, inventory, analytics — leaves the request and goes on a queue. The whole thing is a container on a machine you rent. Search engines see the HTML you actually shipped, not the Figma file and not the Kafka topic.
Six rooms on the same path
Frontend
What the person sees, and what the crawler can read. Routing, HTML, assets, the first paint. If the product only exists after JavaScript, you hid it from search on purpose.
Backend
The contract: auth, business rules, validation, the API the app and the website both call. This is where “it looked fine in the UI” becomes a real write — or a refused one.
Data
The record that has to survive a refresh: database, cache, files. Cache is a copy with a clock. The database is the thing you would restore.
Events
Kafka and queues are for work that should not sit in the click. Checkout returns. Email, indexing, and fan-out happen next. If nothing needs to fan out, you do not need a log.
Runtime
Docker is the same artifact from a laptop to staging to production. Same image, same process, fewer “works on my machine” debates. It is packaging, not architecture by itself.
Cloud
AWS is rooms: compute, storage, network, identity. You rent machines, disks, and a front door. You do not get a product because the logo is on the invoice.
Photo: Adrian Sulyok, via Unsplash
SEO is an architecture choice, not a plugin
Search is not a campaign you bolt on after the stack is frozen. A crawler asks for a URL and needs HTML that names the product, the title, the offer. Structured data, a sitemap, canonicals, and a server that answers quickly are the same system as the page the customer sees. If the important copy only appears after a client render, you chose an architecture that hides the business from search.
Speed is part of that path. A slow origin, an unbounded JavaScript bundle, or a cache that never warms shows up as bounce and as crawl budget — not as a separate “SEO workstream.” The dashboard is not a different product. It is the stack, measured.
Photo: Luke Chesser, via Unsplash
You do not need every logo
Kafka is the right call when an event must be durable and several consumers must see it without blocking the user. It is the wrong call on a brochure that sends one email. Docker is worth it the first time staging and production disagree. AWS is worth it when you need a region, a backup, and a boundary around secrets — not because a slide said “cloud native.”
- Name the request you care about: signup, checkout, search, or a crawler hitting a category page.
- Draw the rooms it visits. If two rooms never talk, they are not one product yet.
- Put slow work off the request. Keep the write you cannot lose on the request.
- Ship HTML the crawler can read. Treat metadata and sitemaps as part of the frontend, not as a marketing leftover.
- Run the same image everywhere you can. Then rent the smallest set of cloud rooms that keep it up.
The honest test is boring: can the team explain, in one sitting, what happens after the click? If the answer is a list of vendors, the architecture is still a slide. If the answer is a path, you can change a room without pretending the rest of the building does not exist.
