chore(radar): remove blips marked 'delete' in the blips review - #106
Merged
Conversation
Removes the 67 blips whose Conclusion column in the "INFO Tech Radar Blips Review Table" (working doc of the 'actualize tech radar' project) reads "delete". All versions of each blip are removed, so they disappear from the radar chart, the quadrant pages, the Technologies Overview and the sitemap — not just from the landing page. Cross-references from the remaining 34 blips to deleted ones are unlinked (link text kept as plain prose) so no dead internal links are left behind.
The current version of a few surviving blips still described removed technologies as INFO's live radar position, and two internal links were broken. Only the latest version of each blip is touched; dated historical entries are left alone, since they are a record of what we thought at the time. - aws: drop the paragraph trialling PaaS providers and Vercel - keycloak: no longer names AWS IAM, Amazon Cognito and Clerk as the preferred alternatives - graphql: drop the tRPC comparison, keeping the GraphQL-over-REST rationale - bdd: drop Cypress, keep Playwright - nodejs: drop the reference to our preferred serverless frameworks Broken internal links fixed along the way: - bdd: /tools/playwright.html -> /tools/playwright (no such route) - postgresql: /methods-and-patterns/database-as-s-service (typo, and the blip is gone) -> plain text - typescript: a link labelled JavaScript pointed at TypeScript's own page No ring, quadrant, featured flag or title is changed anywhere.
Keep the explicit Kotlin comparison the other bullets in the list draw, now that the reference to our preferred serverless frameworks is gone.
morrieinmaas
added a commit
that referenced
this pull request
Aug 14, 2026
Detail pages render every version of a blip stacked under its own date, so the new text has to read coherently next to the older entries. It did not everywhere. - domain-driven-design: the new version repeated the 2022 opening paragraph and goals list verbatim, which read as a copy-paste error with both on one page. It now carries only the C4 material, which is what actually changed. - event-driven-architecture: condensed. The 2021 version already explains producer/consumer decoupling and the 2022 version already lists when to consider it, so the new version now states the approach once and keeps only what is new: the framing, the stance, and the costs. - event-driven-architecture (2022 version): drop the recommendation to use Event Sourcing, a blip removed in #106, and fix the "Even-Driven" typo. - bdd (2023 version): drop Cucumber, which we no longer use. Playwright stays, since we still use it extensively and it has its own blip.
morrieinmaas
added a commit
that referenced
this pull request
Aug 17, 2026
* feat: 14-08-2026 release with the blip rewrites assigned to Moritz Adds a new radar/2026-08-14/ release folder with new versions of the eight blips assigned to @morrieinmaas in the Tech Radar Blips Review Table, so the previously published 2026-04-23 release and the older history stay intact. - bdd: rewritten around the collaborative practice; Cucumber and Playwright moved out of the blip as the review asks, title becomes "BDD" - databricks: trial -> adopt; adds vendor lock-in and US cloud provider dependency considerations, and an alternatives section covering our FOSS lakehouse work - domain-driven-design: gains a "Visualising the model with C4" section, so the C4 Model blip is folded in here rather than standing on its own - event-driven-architecture: reframed as an approach rather than a checklist, deliberately without vendor-specific examples - graphql: adopt -> hold; we still run it in production and can support clients who need it, but would not pick it for a new project - kubernetes: back on the radar (featured); containerising the stack as the baseline, then self-hosted to serverless containers on managed platforms - redis: Valkey becomes the preferred key-value store, Redis stays available where a client wants it; title becomes "Valkey / Redis" - tanstack-query: rewritten now that it is independent of React The C4 Model blip is removed and the link to it from the 2022-05-17 DDD version is unlinked, so no internal links break. * fix(radar): apply review feedback on the 14-08-2026 rewrites Detail pages render every version of a blip stacked under its own date, so the new text has to read coherently next to the older entries. It did not everywhere. - domain-driven-design: the new version repeated the 2022 opening paragraph and goals list verbatim, which read as a copy-paste error with both on one page. It now carries only the C4 material, which is what actually changed. - event-driven-architecture: condensed. The 2021 version already explains producer/consumer decoupling and the 2022 version already lists when to consider it, so the new version now states the approach once and keeps only what is new: the framing, the stance, and the costs. - event-driven-architecture (2022 version): drop the recommendation to use Event Sourcing, a blip removed in #106, and fix the "Even-Driven" typo. - bdd (2023 version): drop Cucumber, which we no longer use. Playwright stays, since we still use it extensively and it has its own blip. * refactor(radar): drop the C4/DDD fold and sharpen three rewrites - c4-model, domain-driven-design: reverted. Folding C4 Model into DDD touches Edgar's row, and he will pick that up himself, so it does not belong in this PR. C4 Model is restored untouched, as is the DDD link to it. This PR now covers 7 of the 8 assigned blips and no longer depends on anyone else. - tanstack-query: says why we rate it rather than only what it does, and notes that the other TanStack libraries are of the same quality and in use. - redis, kubernetes: both opened by restating their previous version's first sentence. They now lead with what actually changed.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Removes every blip whose Conclusion column reads
deletein the INFO Tech Radar Blips Review Table (working doc of the "actualize tech radar" project, 31-07-2026), and reconciles the prose left behind in the blips that survive.Two commits: the removal, then the reconciliation.
1. Removal
radar/<release>/folder). Removing only the latest version would have promoted the previous version back onto the radar.keep,rewrite,on hold, orleave as is.2. Reconciliation
Removing a blip does not remove the sentences elsewhere that treat it as INFO's live position. The current version of five surviving blips still did:
awskeycloakgraphqlbddnodejsOnly the latest version of each blip is touched. Detail pages render every version under its own dated heading, so older entries are a record of what INFO thought at the time and are left intact. Descriptive mentions are also left alone — React Native is still "built using JavaScript and React", TypeScript is still "preferred to JavaScript". Those are facts about the technologies, not radar positions.
No
ring,quadrant,featuredflag ortitleis changed anywhere — verified: the diff contains no added frontmatter lines. Moving Keycloak to adopt, GraphQL to hold, and so on is the rewrite work, not this PR.Three broken links fixed on the way
A link audit that resolves every internal link against the actually-generated routes (rather than pattern-matching slugs) found three that a slug scan misses. Two were already broken on
main:bdd→/tools/playwright.html— no such route,.htmlsuffix. Pre-existing.postgresql→/methods-and-patterns/database-as-s-service— typo (as-s), and the blip is now removed anyway. Pre-existing typo.typescript→ a link labelled JavaScript pointing at TypeScript's own page.Verified against a real build
npm run buildsucceeds and Deploy-Preview is green.featured: true)/overviewsitemap.xmlhrefto any removed slug in the built HTMLGone from the radar chart, the quadrant pages and the Technologies Overview route. All four quadrants still have blips, so nothing renders empty.
Two side effects, both intentional and harmless
2024-01-01,2024-08-01and2025-01-22held only removed blips (CMS blips and React testing library). The radar goes from 12 to 9 versions. No surviving blip had a version in any of them, so no blip's history or new/changed flag is affected.2023-08-01 / 2024-12-01 / 2026-04-23, soazure,bdd,doraandreact-nativecount as recent. 25 detail pages still carry the notice.Removed blips
67 blips
AI as a Service, Algolia, Amazon Cognito, Amazon S3, AWS CI CD Tools, AWS IAM, Axiom, Azure DevOps, Backstage, Bitbucket Cloud & Pipelines, Chai, Chakra UI, Clerk, Cloud-native platforms, CockroachDB, Content as a Service, Contentful CMS, Cypress, Data Science and Machine Learning, Data Streaming, Database as a Service (DBaaS), Dependency drift fitness function, DigitalOcean, Docker, Docker Developer Environments, Event Sourcing, Evolutionary Architecture, Express, GitHub Code Spaces, GitHub Packages, Google Analytics, Jamstack, Java, JavaScript, Jest, k6, Low-code / no-code development, Magnolia, Micro Frontends, Microservices, Mocha, Monorepo, NestJS, Next.js, Platform as a Service (PaaS), Prisma, Progressive Web Applications, Pulumi, React, React testing library, Rebase and merge as Git merge strategy, Render, Run cost as architecture fitness function, Sanity CMS, Serverless, Serverless Framework, Snowflake, Storyblok CMS, Strapi CMS, Superblocks, Support for Internet Explorer 11, Tailwind CSS, Terraform, tRPC, Turborepo, Vercel, Vitest
The ubiquitous ones in that list (React, Next.js, Java, JavaScript, Docker, Terraform, Tailwind CSS, Microservices) are deliberate: they go without saying now, and
about.mdalready states the radar "is not a complete list of our preferred technologies … we only include technologies that we think are currently relevant to our teams."C4 Model is deliberately kept. Its conclusion reads "rewrite/review; we should either embrace it fully, or delete it" — a conditional, not a decision, so it stays until the working group decides.
Still open from the review (separate PRs)