Patrick's Technology Radar

• Languages & Frameworks
• Tools
• Platforms
• Techniques

Technologies can be programming languages & frameworks, tools, platforms, or specific techniques.

The following technology radar is based on the structure of the ThoughtWorks technology radar. This technology radar is constantly updated.

Hint 1: I have compiled a list of various public technology radars. 👇

Inspirational Technology Radar Examples

In this article you will find inspiring examples of different companies documenting their technology management with a technology radar and making the results public.

workingsoftware.devPatrick Roos

Hint 2: Why should you actively manage technology? 👇

Technical Debt Scenario #4: Hype Driven Development

The development team is always on the hunt for the latest technology hype. Currently, there are more than two front-end frameworks used for the product and the time to launch new features is getting longer and longer. What would you do?

workingsoftware.devPatrick Roos

Languages & Frameworks

Adopt

• The 3w core technologies (HTML, Javascript, CSS) Frontend
• TypeScript Frontend, Backend
• Java Backend
• Angular Frontend
• Spring Web MVC Backend
• Angular Material Frontend
• Ionic Frontend
• Bootstrap Frontend
• Cypress Frontend
• Jasmine Frontend
• JUnit Backend
• Jest Frontend
• NgRx Frontend

What is NgRx and why is it used in Angular apps?

This post will show you what NgRx is and why it is used in modern Angular frontend architectures.

workingsoftware.devPatrick Roos

• React Frontend
• AsciiDoc Documentation
• Shallow Render Frontend

Trial

• Svelte Frontend
• Atlaskit Frontend
• Jest Frontend
• Cucumber Frontend, Backend
• Apache Avro Backend
• Redux Frontend
• Neo4j Backend
• jsx Frontend
• Chakra-UI Frontend
• Lit Frontend
• Stencil Frontend
• Tailwind CSS Frontend
• Accelerated Mobile Pages (AMP) Frontend
• New! Fastify Backend
• New! Rust Backend
• New! Wolkenkit Backend

Assess

• Reactor Backend
• AssertJ Backend
• Solidjs Frontend
• Playwright Frontend
• WebAssembly Frontend
• Testcontainers Backend
• Clarity Design System Frontend
• Transloco Frontend
• Fresh Backend
• Radix-UI Frontend
• New! Spring Modulith Backend & Documentation
• New! Elm Frontend
• New! Elixier Backend
• New! D2 Scripting Language Documentation
• New! tRPC Frontend / Backend
• New! qwik Frontend

Hold

• AngularJS Frontend

Tools

Adopt

• Git Infrastructure

Which Git merge strategy is appropriate for our team?

How do you make your feature development traceable and easy to read in your Git history? How do you keep your Git history clean? What is the best Git merge strategy for our team?

workingsoftware.devPatrick Roos

• Maven Backend
• npm Frontend, Backend
• Helm Infrastructure
• GitHub Infrastructure
• GitLab Infrastructure
• Bitbucket Cloud Infrastructure
• Artifactory Cloud Infrastructure
• Jira Infrastructure
• Confluence Infrastructure
• Bitbucket Pipelines Infrastructure
• Webpack Frontend
• Gulp Frontend
• Karma Frontend
• Visual Studio Code Infrastructure
• IntelliJ Infrastructure
• Sonatype Nexus Infrastructure
• Sonarqube Infrastructure
• Sonarcloud Infrastructure
• AsciiDoc Documentation, Infrastructure
• nvm (Node Version Manager) Infrastructure
• Autoprefixer Frontend
• Transifex Frontend / Backend
• Storybook Frontend
• SDKMAN! Backend
• Transifex Frontend / Backend
• ohmyzsh Infrastructure
• Excalidraw Infrastructure
• GitHub Actions Infrastructure
• Chromatic Frontend
• Terraform Infrastructure
• ESLint Frontend

Trial

• Gradle Backend
• Yarn Frontend
• ArgoCD Infrastructure
• Pulumi Infrastructure
• Azure Key Vault Infrastructure
• PlantUML Documentation, Infrastructure
• SwaggerHub Infrastructure
• Confluent Schema Registry Infrastructure
• Lighthouse Frontend
• k6 Infrastructure
• Sentry Infrastructure
• Figma Frontend
• Sonarlint Infrastructure
• Xray Testing Integration in Jira Infrastructure
• Bitnami Sealed Secrets Infrastructure
• Lucidchart Documentation, Infrastructure
• ArchUnit Backend
• Structurizr Documentation
• GitHub Copilot Infrastructure
• Asciidoctor Documentation
• docToolChain Documentation
• Nx Infrastructure
• Husky Infrastructure
• Plausible Analytics Infrastructure
• k9cli Infrastructure
• Jetbrains Space Infrastructure
• Kong Infrastructure
• Snyk Infrastructure
• HashiCorp Vault Infrastructure
• Prettier Frontend
• Context Mapper Documentation
• Gitpod Infrastructure
• Diagrams Documentation
• New! Barman Infrastructure
• New! Currents Frontend, Testing
• New! KrakenD Infrastructure
• New! Zally Backend

Assess

• Paketo Buildpacks Infrastructure
• jMolecules Backend
• Mozilla SOPS Infrastructure
• Telepresence Infrastructure
• Vite Frontend
• Dapr Infrastructure
• StackGres Infrastructure
• Dependency-Track Infrastructure
• Turborepo Infrastructure
• GoTrue API Infrastructure
• PostgREST Infrastructure
• Penpot Documentation
• Renovate Infrastructure
• Spinnaker Infrastructure
• GitHub Codespaces Infrastructure
• Debezium Infrastructure
• Fleet Infrastructure
• Kroki Documentation
• Docusaurus Documentation
• Codescene Infrastructure
• New! Terrastruct Documentation
• New! Crossplane Infrastructure
• New! Replay Frontend
• New! Meilisearch Infrastructure
• New! 11ty Infrastructure
• New! Grafana Loki Infrastructure

Hold

• Grunt Frontend
• Bower Frontend
• TSLint Frontend

Platforms

Adopt

• Microsoft Azure Infrastructure
• Google Cloud Infrastructure
• Docker Infrastructure
• Kubernetes Infrastructure
• PostgreSQL Infrastructure
• MongoDB Infrastructure
• Keycloak Infrastructure
• Auth0 Infrastructure
• Netlify Frontend, Infrastructure
• Firebase Infrastructure
• Node.js  Frontend, Backend
• Vercel Infrastructure
• Kafka Backend, Infrastructure
• Openshift Infrastructure
• Azure Functions Backend, Infrastructure
• Azure Kubernetes Services, Infrastructure
• Azure DevOps Infrastructure

Trial

• Supabase Infrastructure

Architecture and Technology Stack of Supabase ⚡

Supabase under the hood. This post shows you the high-level architecture and the technology stack of Supabase.

workingsoftware.devPatrick Roos

• GraalVM Backend, Infrastructure
• Fly.io Infrastructure
• Deno Backend

Assess

• Podman Infrastructure
• IPFS Infrastructure
• Azure Container Apps Infrastructure
• Bun Backend
• New! Tauri Frontend
• New! Icepanel Documentation

Hold

• Heroku Infrastructure

Techniques

Adopt

• Story Mapping Requirements Engineering
• Microservices Backend
• Material Design Frontend
• arc42, Documentation
• Open API Specification, Backend
• Test Driven Development Frontend, Backend
• DORA Metrics (Four Key Metrics) Infrastructure
• Component Driven development Frontend
• RESTFul API Backend
• Flexbox Frontend
• CSS Grid Frontend
• CUPID Frontend, Backend
• Infrastructure as Code Infrastructure
• Domain-Driven Design  Software Architecture
• New! Architecture Improvement Method Frontend, Backend

What is Infrastructure as Code? And why do you need it?

This article describes what Infrastructure as Code is and what problems Infrastructure as Code can solve. We also discuss the benefits and challenges of Infrastructure as Code and which tools are suitable for Infrastructure as Code.

workingsoftware.devPatrick Roos

• Serverless Architecture Software Architecture
• Monorepo Infrastructure
• Architecture Characteristics Worksheet Software Architecture

What is a monorepo and when should it be used?

In contrast to polyrepo, there’s the monorepo technique: a monorepo is a single repository for an entire organisation that contains several different projects with clearly defined relationships.

workingsoftware.devPatrick Roos

Trial

• Behavior Driven Development Frontend, Backend
• Acceptance Test Driven Development or Specification by Example Frontend, Backend
• Event Storming Requirements Engineering, Software Architecture
• Impact Mapping Strategic Planning, Requirements Engineering

Impact Mapping: Our Impact as an agile organisation

We often talk a lot about various initiatives and the resulting technical solutions in detail. But we often do so without keeping in mind the specific business objective and the desired impact we want to achieve. This is where Impact Mapping comes in.

workingsoftware.devPatrick Roos

Step-by-step guide: Create an Impact Map using a real-world example

In this practical guide, you’ll learn how to create an Impact Map for a specific business goal and get a template for your next impact mapping session.

workingsoftware.devPatrick Roos

• Offline First Development Frontend, Software Architecture
• Usage of Service Workers Frontend
• Trunk based development Backend Frontend
• GraphQL Backend
• Flux Frontend
• Documentation as Code Documentation

What is Documentation as Code? And why do you need it?

“Documentation as Code” means that your documentation process benefits from the same techniques used in software development.

workingsoftware.devPatrick Roos

• Diagrams as Code Documentation
• Conventional Commits Documentation
• C4 Model for visualising software architecture Documentation
• Domain Storytelling Requirements Engineering / Software Architecture

Assess

• Micro-Frontends Frontend, Software Architecture
• Event Sourcing Backend, Software Architecture
• Saga-Pattern Backend
• Testing RxJS Code with Marble Diagrams Frontend
• Async API Specification Backend
• Non-Fungible Token Infrastructure
• JSON:API Backend
• Agile Architecture Documentation Workshop, Frontend, Backend, Infrastructure
• Context Mapping Software Architecture
• Set-Based Design Software Architecture

Hold

• Estimate user stories by days / hours
• Single Page Applications per default

Which web frontend architecture fits best?

This post will help you find the right web frontend architecture that best fits your specific quality goals.

workingsoftware.devPatrick Roos