Do you want a Ferrari? Why is it important what your system is running on?

Do you want a Ferrari? Why is it important what your system is running on? A beautiful example of an expensive car that one can be proud of. It is expensive, there are few of them, it rides great, but probably not every owner takes it to the field to plow potatoes. Or is it the other way around?

Unfortunately, in the IT world it is the opposite. Have a “tailor-made” system developed, which in the series is close to even rarer cars than the Ferrari. And then it starts.

Custom-made cars, as well as custom-made systems, are often repaired only by the original manufacturer. Or an enormously expensive repairman who uses his own parts and car, as well as the system, will never be what he used to be.

Plus, you don’t have to brag about IT IT, as is usually the case with bright Ferrari cats.

You want it to work. Make it passable. Easy to manage. Whether you can go to the mechanic, or ajťák next door, and he can add his own functions according to the specifications that are available.
You also want when the manufacturers of those overpriced toys go bankrupt, or, as part of their sustainability, give a price that you can no longer afford to be able to move elsewhere. And that’s usually the case with custom systems.

More and more companies are beginning to find that the trends of 2005 are no longer valid. It is no longer the case that someone has “rushed” your IT system and you are forever satisfied with it.
Do you want to pay all the time? Pay for updates that don’t apply to you as a system owner at all? New version of the programming language and you have to pay? Any modification is enormously expensive?

The system must be chosen with regard to sustainability, practicality, transferability. These are the main principles. People are changing on all sides. Both in your company and in the company of suppliers. Even the supplier can change. If you have not been locked and you have everything in your hands – this means the application codes as well as the rights to handle these codes.

You want the system to serve you for decades. This is a current trend. Let the community develop as much as possible, independent of your supplier. You don’t want to worry, you want to use the system. And knowing that it’s still evolving, the documentation writes, it’s global, so you can give your partners abroad access or even the whole system, because in other countries they also know how to work with it.

These are open source systems that are deployed around the planet. Such a system is a trend today. Sustainable, supported by a large community, with many, many tutorials for both users and developers.

The small workshops of software engineers next door do not have much to offer against such solutions. Perhaps only if you want to brag that you constantly pay for what they have elsewhere for free and better.