Software Engineering
The technologies we choose. And why.
Our job is building digital platforms. To do it well, every year we line up the technologies we use in our projects and decide what to adopt, what to try out, what to keep an eye on and what to let go. This page sums up those choices.
Source: Interlogica Tech Radar, 2025 edition, by the Solution Team.
The radar
How to read it
We adopt
Established technologies, in production for a long time. We keep a deep knowledge of them, through use and training.
We trial
Already used in at least one real project, and convincing: we are putting them to the test before making them a standard.
We assess
Promising, not yet in our projects. We study them through proofs of concept, often proposed by the Interlogici.
We have let go
Superseded, or no longer in line with how we work. Where they are still in production we maintain them, but we do not choose them for new projects.
Our stack
Four areas, one choice for each
Languages and frameworks
A few main languages, chosen to last: TypeScript from frontend to backend, two compiled languages for the enterprise world.
We adopt
- TypeScript / JavaScript
- PHP
- Python
- Java
- C#
- SQL
- React
- Angular
- Node.js
- Symfony
- Spring Boot
- Povery
We trial
- Go
- Quarkus
- Laravel
We assess
- React Native
Platforms
AWS is our reference cloud platform; Azure supports projects in Microsoft environments.
We adopt
- AWS
- Azure
- Cloudflare
- GitLab
Tools
Containers, infrastructure as code, quality and observability: the same tools in every project.
We adopt
- Docker
- Terraform
- Ansible
- PostgreSQL
- MySQL
- RabbitMQ
- Keycloak
- Harbor
- SonarQube
- Sentry
- Grafana
- Zabbix
- Git
We trial
- Kubernetes
- Prometheus
- N8N
- Langfuse
- MLflow
- AI-assisted IDEs
We assess
- Trivy
- Horusec
- SafeLine
Methods
How we work matters as much as the technologies: automation, testing and continuous improvement.
We adopt
- CI / CD
- Automated testing
- Infrastructure as Code
- Retrospectives
We trial
- Event Sourcing
Made by us, open to everyone
Povery: serverless in the shape of a familiar framework.
Povery is a TypeScript framework for building applications on AWS Lambda. It comes from one of our internal projects: it hides many details of the serverless world and offers an interface similar to the MVC frameworks developers already know.
We released it as open source. It has been in production for years in several projects, and it is our first choice when a project wants the advantages of serverless.
Our method
Every project starts with the same guarantees
Continuous integration and delivery
Automated validation, tests and builds at every change; frequent releases, so we adapt to change smoothly.
Measured quality
Automated tests across the whole pyramid, continuous code analysis with SonarQube in the pipelines, production errors seen with Sentry before anyone reports them.
Infrastructure as code
Environments described with Terraform and Ansible: repeatable, versioned, in the hands of the people who build the project.
Retrospectives
Not a ceremony: the moment when the people working on the project look back and decide what to improve.
Choosing also means letting go
What we have let go, and why
We like to experiment. That is exactly why we say clearly which paths we no longer take: anyone who entrusts us with a project should know what we build it on.
C / C++
Extraordinary languages, but they call for a kind of project management that is not ours: we no longer take on new C/C++ development.
MongoDB
Attractive at first, but for the projects we work on a relational database holds up better over time.
LangChain
It looked like the foundation for LLMs in the enterprise; it proved too unstable for software that has to last.
Rust
The price in development and change effort is too high for the kind of projects we do.
Pulumi
It took infrastructure away from a declarative approach: for Infrastructure as Code we use Terraform.
Jenkins
Our integration and delivery pipelines live on GitLab.
Living skills
The radar gets updated. So do the people.
At least once a year we ask the Interlogici which skills they have and which technologies they work on: every new edition of the radar starts from there.
We are building training paths on the cloud and on infrastructure as code, open to every Interlogico who wants to grow in these areas.
Got a project?