Book Image

The Cloud Adoption Playbook

By : Moe Abdula, Ingo Averdunk, Roland Barcia, Kyle Brown, Ndu Emuchay
Book Image

The Cloud Adoption Playbook

By: Moe Abdula, Ingo Averdunk, Roland Barcia, Kyle Brown, Ndu Emuchay

Overview of this book

As cloud technologies continue to challenge the fundamental understanding of how businesses work, smart companies are moving quickly to adapt to a changing set of rules. Adopting the cloud requires a clear roadmap backed by use cases, grounded in practical real-world experience, to show the routes to successful adoption. The Cloud Adoption Playbook helps business and technology leaders in enterprise organizations sort through the options and make the best choices for accelerating cloud adoption and digital transformation. Written by a team of IBM technical executives with a wealth of real-world client experience, this book cuts through the hype, answers your questions, and helps you tailor your cloud adoption and digital transformation journey to the needs of your organization.
Table of Contents (17 chapters)
Free Chapter
1
Cover
2
Title Page
3
Foreword
16
Index
17
End User License Agreement

Reference Implementations

As stated earlier in this chapter, the architect is responsible for creating blueprints for building a solution; therefore, a reference architecture without reference implementations is not useful for developer adoption. Providing the detail for building a reference application is key. Developers are among the most difficult audiences to please, but they are in an empowered position, especially in modern development. Developers must be convinced that a reference architecture is worth following; code is the way to convince them. Some of the reasons why developers are hard to convince are:

  • Developers are religious about their technology and frameworks. They tend to want to use what they are familiar with unless they can be shown a better way of doing things.
  • Developers feel that nothing is better than their own ways of coding. They must be convinced that new patterns and techniques are more efficient or productive.
  • Developers need to be met where they are. Developers...