---

Note

Architects ask themselves "If my system is going to run for a long time, do i risk using and/or training my developers on a technology that just came out and might be obsolete in the future ?", like if service A is using a standard protocol. what happens when it is not supported in the future, is my system resistant to this change.

Some may take this risk by keeping in mind potential requirements to replace them.

An example of this are databases: if you use a relational database you will survive your vendor going bankrupt by migrating to a new vendor, that is if you do not use any feature available only to a specific vendor.