Tech Radar

Tech Radar

soldevelo-logo.png

 

This document serves as a guide to the technologies, tools, frameworks, and patterns relevant to our Frontend development practices. This radar is a living document. It reflects our current understanding and opinions, and it should be reviewed and updated periodically.

Want to propose a change, disagree with a placement, or add an interesting new technology? Please reach out to @Damian Szafranek. This Tech Radar is a living document - we keep it useful by updating it together as our projects, tools, and experiences evolve.

Categories

Frameworks & Meta-Frameworks

UI Libraries & Design Systems

State Management

Data Fetching & API Clients

Styling

Build Tools & Bundlers

Tooling & Developer Experience (DX)

Testing

Accessibility Testing

Languages & Runtimes

Infrastructure & DevOps

Databases & Data Stores

AI & LLM Tooling

 How to Read This Radar

The radar is organized into several Categories (represented as subpages), covering different areas of Frontend development. Within each category, individual technologies are assigned one of four Statuses, indicating our recommended approach to them.

Statuses

Each technology on the radar falls into one of the following statuses:

  • ADOPT

  • Recommendation: Strongly Recommended / Default Choice.

  • Meaning: Technologies we have high confidence in to serve our purpose, typically low-risk and proven in our environment. We expect teams to use these for new work where appropriate. We invest in learning and maintaining expertise in these technologies.


  • TRIAL

  • Recommendation: Worth Pursuing / Explore with Intent.

  • Meaning: Technologies that appear promising and have shown potential value. We believe they are worth exploring on projects that can handle the associated risks (e.g., non-critical features, internal tools, proof-of-concepts). The goal is to gain experience and evaluate their suitability for broader adoption.


  • ASSESS

  • Recommendation: Worth Investigating / Monitor.

  • Meaning: Technologies that are interesting and potentially valuable, but require more investigation before recommending a trial. This might involve building small prototypes, research spikes, or closely monitoring their maturity, community adoption, and features.


  • HOLD

  • Recommendation: Proceed with Caution / Avoid for New Work.

  • Meaning: Technologies that are not recommended for new projects. This could be due to various reasons: being outdated, replaced by better alternatives, known issues (performance, security), misalignment with our strategic direction, or declining community support.

How to Add New Categories

Once creating a new Category, clone the [TEMPLATE] Category Template at first.