Category: TechStack
From WordPress to a static site: how we moved this blog to Astro
This blog used to run on WordPress on a hand-built EC2 instance and an outdated MySQL database. It is now a static site built with Astro. Here is why we moved, what we found in the old blog, and how we made sure no content got lost.
Evolving Our Tech Landscape – ottonova Tech Radar Q3 2025 Update
At ottonova, we continuously evaluate our technology stack to ensure we’re using the best tools to deliver exceptional digital health experiences. Our quarterly Tech Radar update reflects our commitment to technological excellence and innovation. Here’s a summary of the key changes coming via our Q3 2025 Tech Radar update. Infrastructure Evolution Backstage has gained prominence…
Migrating from Self-Managed RabbitMQ to Cloud-Native AWS Amazon MQ: A Technical Odyssey
In the ever-evolving world of cloud-native solutions, it can be a daunting task to maintain message brokers. For a while, our team was responsible for a self-managed RabbitMQ instance. While this worked well initially, we encountered challenges in terms of maintenance, version updates, and data recovery. This led us to explore Amazon MQ, a fully…
Introducing the ottonova Tech Radar
We always promoted openness when it came to our tech stack. The ottonova Tech Radar is the next step in that direction. What is the Tech Radar? The ottonova Tech Radar is a list of technologies. It’s defined by an assessment outcome, called ring assignment and has four rings with the following definitions: ADOPT – Technologies we…
Why we switched from Moment.js to Day.js
Moment.js is an awesome library when it comes to performing complex date-time manipulations. It provides a rich and clean API that covers many use cases. That aside, Moment.js shouldn’t always be the go-to library when it comes to date-time problematics. Alternatives should be considered as well. What are the alternatives? Actually, there are plenty of alternatives…
About ottonova’s tech stack transparency
Hi everybody! At ottonova, we believe in being transparent about the technology stack we use. We see no reason to keep it a secret. Possible concerns we sometimes hear are about the following two domains: Our approach is to use mature technology stacks, follow best practices, and incorporate new technology components as needed. This approach…
