The Adventures of COYO: The new journey of the Tech Radar

Daniel Doe
Haiilo
Published in
3 min readOct 11, 2021

Hmmm… the radar looks different from last time! See the full radar here

Wait, what is a Tech Radar and why do you need one?

Moin, if you’re asking that question maybe you missed the article we wrote a few months ago about the beginning of our adventure, but no worries, you can still read it here:

As a small resume for you either way, we needed “a way to provide an overview of the tech stack we use”!

Ooooh nice, what is new?

Photo by Mukuko Studio on Unsplash

Glad you ask! So what might strike you as the biggest change is how it looks. We decided to move from Thoughtworks “Build your own Radar” to the self hosted solution that you can find at the beginning of the article. That might be the most noticeable change but not the most important one: The real important changes happened inside the radar with the migration of blobs from one ring to another and in the most important case, the removal of outdated tech from the Hold ring. And that is where we will start from, with a thank you:

  • Bitbucket — we finally switched to Gitlab as that proved to be the better fit for our needs. We also started to migrate more and more CI jobs to the Gitlab CI, to leave Bamboo behind soon.
  • GridFS — with the migration to S3, this tool became obsolete for us and it was naturally removed from our stack.
  • Maven

Thank you for your service in the past few years.

On the other hand we welcome the following technologies in the round:

  • Storybook
  • Chromatic
  • Terratest
  • Microfrontends
  • Template Testing
  • AWS and friends

To find more about why we decided to welcome them to the COYO tech stack, have a look at the radar and click on their respective blob for more information.

To finalize, you might notice that the blobs are quite clustered in the middle. That is a result of the migration of some technologies to a more central position towards adoption, like:

  • Phrase
  • Pact
  • Jest
  • NGXS
  • GraphQL

Those Tools or Frameworks proved to be worth our time investment and they align with our vision for the future. We can just encourage others to keep using this technologies or introduce them in their own projects.

This mean exciting times for us, because we finally introduce the way to work with some of this Tools and Techniques and we are curious to see if they can hold their ground and prove to be helpful for us.

Exciting news, what can we expect next?

Interesting question, the main goal for the next months is to focus work on our technical debt and that of course includes getting rid of even more of the technologies we put on hold. We are working on a few initiatives to get rid of AngularJS once and for all, TSLint reached end of live and although we already introduced ESLint as a replacement there is still a bit of cleanup missing, Modularization of the backend and splitting into micro services is also kicking out strong, among many other things we have in our backpacks.

Photo by Tim Swaan on Unsplash

The Tech Radar needs regular updates and to keep on track with the fluctuation of our stack. So stay tuned for further updates next year! Thank you for reading and feel free to share your thoughts in the comments.

--

--