Anubex is a company filled with highly technical, skilled and passionate people. It might not surprise you then that most of us have strong opinions about what technologies (e.g. programming languages, database, frameworks) are ‘good’ and which are ‘bad’, regularly leading to lengthy, well-articulated, intelligent, heated… yet never conclusive debates.
Notwithstanding these individual preferences, we all subscribe to a general vision that sees technology as a means, not as an end: Anubex does not favor nor disapprove of any specific set of technologies. A certain technology can be a great tool in one specific context, while being a serious liability in another (E.g. because of skills shortage, because of industry-specific integration needs).
At the same time, we believe strongly that the right choice of technology and (arguably even more important) architecture is fundamental to the continued success of both our own and our customers’ operations. Or put more negatively: a wrong choice can have big consequences.
So we’re back at the question: ‘what is the right choice?’
I hope I’ve already established firmly that we don’t believe there is one right choice. Yet we have to make choices and for this we make an evaluation based on two key criteria:
The term we use for describing technologies that fit these criteria is “native technologies” since they just fit it and once established, are seen as obvious choices. They are also the very same technologies you would choose when starting a development from scratch, as opposed to migrating an existing application.
But let’s turn the above two criteria, which probably seem pretty subjective and high-level to you, into questions that are more specific and more objectively answerable:
Whether you’re contemplating a migration project or an entirely new development, if a technology gets a clear ‘YES’ on all the above, you can be assured that it’s a safe choice to make!