FEXCO API Technology Landscape: TechRadar 2018-Q2

The FEXCO Central API Tech Radar is a fast overview about the used technologies in the platforms (Delivery and Computing) that make the API possible. This time we show the information for the second quarter 2018.

The development of common development/computing and delivery platforms has modified substantially the approach to the technologies to be used in order to prepare FTS for the new challenges.

Anything new?

The FEXCO central API technology stack is radically different from older projects. as an Innovation and Research initiative we have included definitely AI tech stack (Spark ML and Tensorflow) and we’ll continue on this way with an independent quadrant pretty soon.

Besides, we are on our way about improving our practices in the JVM stack (our skills with Akka and Scala have improved dramatically in the last months) as well as out of the JVM with system languages (Go and C) searching for the lowest footprint and build time for our components. Spring and Spring Cloud have  been completely abandoned because the extremely high latencies, high footprint and obsolescence compared to modern container orchestration systems.

Same for SQL Databases. The relational paradigm is definitely obsolete and the relational hell is not but a bad memory from the past.

The Delivery Platform is really mature with Continuous Delivery pipelines and we are looking to new products adopting Jenkins X as our usage of Kubernetes is solid (withing our loyal Azure AKS).

The integration with JIRA is going according to our plans in order to automate Agile actions and reduce the cost of non technical staff in teams and squads.


What is the FEXCO API Tech Radar?

It is a list of software related technologies, complemented by an assessment result, called ring assignment as categories. We use for now four rings:

  • ADOPT — Technologies we have worked in the past, have high confidence in to serve our purposes, even in large scale. Technologies with a usage culture in FTS production environments. We are not thinking of discard these technologies yet.
  • TRIAL — Technologies that we have seen work with success in project work to solve a real problem; first serious usage experience that confirm benefits and can uncover limitations. Technologies we have tested in Proofs of Concept with a TRIAL technologies are slightly more risky; some engineers in FTS walked this path and will share knowledge and experiences.
  • ASSESS — Technologies that are promising and have clear potential value-add for us that we test in PoCs; technologies worth to invest some research and prototyping efforts in to see if it has impact. ASSESS technologies have higher risks; they are often brand new and highly unproven in the organization. You will find some engineers that have knowledge in the technology and promote it, you may even find teams that have started a prototyping effort. ASSES technologies can be never adopted depending on the results from Proofs of Concept.
  • HOLD — What we used in the past and we should not use anymore for any reason. Technologies not recommended to be used for new projects. HOLD technologies should not be used for new projects, but usually can be continued for existing projects with a specific deadline for replacement.


The FEXCO API Tech Radar is one of the pieces with useful information for the integration, SRE and development teams and squads. Engineering teams can use it to be aware about our needs regarding training, skill sets, evolution, etc; it provides a platform to share knowledge and experience in technologies, to reflect on technology decisions and continuously evolve our Technology Landscape reflected on common platforms. Based on the pioneering work of ThoughtWorks, the FTS Software TechRadar sets out the changes in technologies that are interesting in software development — changes that we think our engineering teams should pay attention to and consider using in their projects.

The Technological Landscape will count on 4 main pieces:

  1. TechRadar
  2. RoadMap for technologies (made from the information in the TechRadar as a plan for improvement and evolution)
  3. Proofs of Concept Plan (according to proposed technologies)
  4. Training plan


The architectural team in FTS will update the FEXCO API TechRadar with information from the different projects and activities.


Author: Jesus de Diego

Software Architect and Team Lead

One Reply to “FEXCO API Technology Landscape: TechRadar 2018-Q2”

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.