The development team at Runroom has been using a Tech Radar for a couple of years. This tool helps visualize the technologies and methodologies used in product development, including emerging market trends.
There are various forms of Tech Radars, each reflecting the unique characteristics and methodology of the team that develops it. At Runroom, they've chosen an approach that allows for an easily updated and organized list of items. The idea is to annually update it to determine which technologies to keep, discard, or try.
The presented technology map is a combination of the Tech Radars from both the Frontend and Backend teams at Runroom. After each team completed their creation process, they combined their findings to create a unified development team Tech Radar.
One of the most significant discussions at Runroom occurred at the beginning when defining and customizing the typical categories of Tech Radars: Adopt, Trial, Assess, and Hold. Each company adapts these categories to its context, and at Runroom, the goal was to establish them in a way that would remain relevant year after year. This approach reflects the company's commitment to tailoring the Tech Radar framework to suit its evolving needs and perspectives. The Runroom team reached a consensus on the meanings of the categories in their Tech Radar:
It was crucial for Runroom to define each category clearly to ensure new elements are incorporated without confusion or ambiguity. Consequently, each category has unique items, and ideally, there should be no repetition of the same item across different categories. This approach ensures clarity and specificity in their Tech Radar.
<aside> <img src="/icons/arrow-southeast_green.svg" alt="/icons/arrow-southeast_green.svg" width="40px" /> Items used in most projects, suitable for production, and intended for continued use. There's also an interest in migrating projects not using these items towards them.
Node LTS
NPM
React
Typescript
Symfony 6
Sonata 4
Deployer
PostgreSQL (alternativa a MySQL)
PHP
PHPUnit
API Rest
Testing (Unitario, Integración)
Jenkins
Docker + Docker Compose
Github </aside>
<aside> <img src="/icons/arrow-southeast_yellow.svg" alt="/icons/arrow-southeast_yellow.svg" width="40px" /> Items to be tested during an iteration, potentially replacing existing ones. These could also be items of business interest or with promising market prospects.
TailwindCSS
Vitest
Party Town Js
Domain Driven Design
Meilisearch (alternativa a Algolia, Elastic Search y Apache Solr)
Kotlin
KTOR
Langchain
Spring Boot (alternativa de Symfony)
</aside>
<aside> <img src="/icons/arrow-southeast_blue.svg" alt="/icons/arrow-southeast_blue.svg" width="40px" /> Items used in some projects, with a focus on further exploration. These items might be in pre-production or production, used to validate full adoption or consider migration in future iterations.
Hexagonal Architecture
Cypress
PostCSS
CSS Modules
NextJs
Redis
Testing (E2E)
Trunk Based Development
Datadog
Storybook </aside>
<aside> <img src="/icons/arrow-southeast_red.svg" alt="/icons/arrow-southeast_red.svg" width="40px" /> Items that are planned to be phased out and maintained. New projects should not include anything from this list.