Have you ever tried guiding your developers that they can\u2019t use a framework of their choice or they need to use a particular operating system of all their development activities? You must have, I guess and the result is disgruntlement. And if the developers are working independently, they would start using their own tools and create a shadow IT. It often happens that you select and OS, an application framework or a platform or infrastructure because it is on the company recommended checklist but then you discover that it doesn\u2019t have compatibility with different solutions or platforms. <\/p>\n\n\n\n
Intuitive tooling equals to developer productivity. Developers always wants tools that can get their job done more than the tools, platforms or frameworks that has been recommended by either your vendor or is on the company checklist. If you force your developers to work on a set different from that, their productivity would go down. The IT operations team and the security teams would be up in revolt when half of their time they would be bogged down in managing systems and software sprawl. <\/p>\n\n\n\n
The different results of application platform lock-in are <\/p>\n\n\n\n
Your vendor may push you to accept and use their platform because they may consider it to be more integrated but it may result in certain flexibilities of you being narrowed down.\u00a0So\u00a0you need to access whether the platform chosen will be compatible with public and private clouds or whether you would be restricted to work on a specific operating system if you choose the vendor\u2019s recommended platform\u00a0<\/p>\n\n\n\t\t