Back to Blog
Sip elixirs5/7/2023 ![]() Our goal was to provide a slick, real-time experience to our users. ![]() One of the themes that kept creeping up from our discoveries was user experience: the look and feel of the whole thing. We set off on a scoping and requirements gathering exercise and managed to draw a circle around the features we wanted to build and deliver in due time. In other words, we were in a fairly good position to experiment and explore. Now a rewrite does not require a change in technologies: we could have stuck to the more or less blessed stack of Node.js/Typescript for our back-end, but we realized an opportunity here to try something new in a part of the application that is not necessarily on the hot-path. We also felt that utilizing more modern, ubiquitous technologies like WebSockets would suit us better and provide our users with a more engaging experience – and well, let’s just say it had a host of other small problems that made it a prime candidate for a rewrite. In its then-current state, our notification system was baked into some older parts of our service ecosystem and heavily resisted far-reaching changes. It will not be a deep dive into the language and its surrounding ecosystem, but instead, I’ll offer a glimpse into how we approach language and technology evaluation and adoption. In this post, I’ll walk you through some of the considerations and learnings we encountered along the way. Late last year, we were faced with the challenge of modernizing our notifications system for end-users by making it fit for both the changing requirements of the industry and our internal development teams. At Smartly.io, a new technology stack can be introduced in several ways, one of which is to address a particular challenge.
0 Comments
Read More
Leave a Reply. |