This is the translation for the Spanish post written on my personal website.
At Audiense we have been building out our backend application over the last six years using NodeJS allowing us to run JS on the server. The development teams never really considered the consequences or scalability of using such a open source server environment before starting new projects (or even migrating existing ones over).
Let’s just say the last six years have been a learning curve for us all. NodeJS has a lot of particularities around the asynchronous execution, allowing for several bugs and pitfalls if not scoped correctly. In addition, due to the fact that JS suffers from the lack of a well defined structure, forcing you to apply best practices by default, our codebase grew quickly reaching a large coupled monolith proving difficult to maintain. Sound familiar?
With alarm bells ringing and the addition of a few new experienced developers we gradually began implementing better code architecture practices throughout our application.
This guide will showcase some of the good practices that have helped make our code more flexible, testable and easier to understand.
