“We don’t have time to refactor.”
“Our managers won’t let us implement automated tests!”
“This app is really old. No one knows how it works since Peter left the company 3 years ago, and people are scared to make changes to it.”
“This piece of software is buggy. We know it, but don’t have time to invest in it. So we just have a manual process to work around the bug when it happens.”
“Nope. I’m not working on that crappy piece of sh*t.”
It’s safe to say that every software engineer has heard one or more of these examples during his or her career. And most probably has already pronounced something approaching. …
Back in early 2016, we decided here at Younited to transition to a microservice architecture. We have learned a great deal since. And one thing we learned is how to substitute a microservice by a new one without downtime, and without requiring to update all callers at the same time.
You have a piece of software that provides a service to other parts of a larger system. For instance, a service that tells you if a customer on your website is a returning customer. This piece of software can be a feature of an existing monolith or a stand-alone component. …
Laissez moi vous narrer une histoire palpitante, captivante et tout un tas d’autres adjectifs en -ante. C’est l’histoire du développement de Youniversalis, notre outil d’auto-documentation de notre système d’information composé de microservices.
Younited Credit a beau avoir commencé son activité à peine en 2011, on a tout de même réussi à créer très très rapidement un monolithe. …