There is no doubt that an element of uniqueness is essential in many different areas and there are many reasons why being unique can be beneficial. The question I have today is that from the IT operations and IT architecture stand point, is it good to be unique? In my humble opinion, it’s a big no-no. In fact, I even think it is bad juju to be unique.
In fact, time and time again, I come across customers of various sizes, from various industries and various regions proudly showing me their infrastructure and their design, and boasting about how their infrastructure and architecture needs to be different because of their special business requirements. Many have even boasted about their ingenious ideas on how they have tweaked a product to do things that the product was not designed to do.
Some have definitely taken products like Microsoft Active Directory and Microsoft Exchange and fully embraced the Star Trek tagline of going beyond the final frontier. They’re proud that their architecture is unique and you know what, I am glad for them, but probably not so much for the company. Don’t get me wrong, I am not saying that they are doing anything bad, they are just doing what they need to do.
However, here’s why I think being unique is not a good thing in IT:
Of course, there are many other reasons why I think you should consider not being unique when you are designing your new systems. Your best bet is to find out if other organizations are deploying the products that you’re about to deploy, and chances are they will be more than willing to share their experiences with you.