2/3/2024 0 Comments Implementation ibm zcloudThe risk of not reducing complexity or even increase complexity is very high and ending up with spending a lot of resources for just replacing some old tools by some new ones is a very likely scenario in that case. As soon as deviations has to be built in for some cases and/or for some people you end up with a lot of custom build complexity in the tools, making these tools not maintainable and not flexible. Keep in mind that once you have a standard you want to implement that standard with easy configurable tools. Of course there must be room for improvement but implement a heavy governance to guard the standard. Stick to the standards! Don’t allow deviations even if they seem to be not that harmful.They can’t! They can help you but you have to do the hard work yourself. Don’t sit back and assume that vendors are going to solve your challenges with magic tools.By keeping the standard simple you are able to easily configure the tooling. Once you start automating, tools are needed. That will help us in the ability to move through the next levels a lot faster. Keep the standard as simple as possible.That foundation has to be solid as a rock. Standardizing is hard work, but necessary to put down a solid foundation for moving to a Cloud Way of Working.Without standardization an organization can forget about moving to a Cloud Way of Working because you will run into huge system management problems.Let’s try to give a brief summary of what I think are the most important things. Typically they all use their own divers standards for a long time already and are very familiar with these.Ĭoming up with a standard that is accepted by people that are used to their own standards for 10, 20 years or more is a challenge. IBM Z is a platform that is shared by multiple people working for multiple parts in the organization. From an IBM Z perspective, standardization will not be easy. If I had to invest my money I would invest it into standardization. It’s the foundation that has to be solid as a rock. ![]() Standardization for me is the most important part of achieving our ambition. Without standardization you can forget about moving to a Cloud Way of Working because you will run into huge system management problems. Doing that enables you to move to a Public Cloud in a smooth, cost-effective way. So I believe that moving existing on-site workload to a Public Cloud should always start with standardizing your own environments. This is true for every on-site workload that you want to move to a Public Cloud and is independent of the platform that the workload is running on. Every deviation from these standards comes with higher costs and a higher risk on a Cloud provider lock in. If you want to move to the Cloud you must follow the standards that the Cloud provider requires.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |