Sign In

Richard Watson

VP, Analyst at Gartner covering cloud, application platforms and cloud-native

Richard Watson is a Vice President and Analyst at Gartner, specializing in Application Architecture and Platforms.3 He is an experienced IT industry professional with expertise in cloud computing, application platforms, and cloud-native technologies.4

Areas of Expertise

Richard Watson advises application and platform teams on:

  • Cloud-native platforms and architecture1
  • Kubernetes
  • Cloud adoption strategies3

Professional Background

Watson has been with Gartner for several years, where he has:

  • Served as a VP and Analyst in Gartner for Technical Professionals (GTP)3
  • Published research focusing on cloud-native architecture, Kubernetes, and cloud adoption12
  • Advised clients on their cloud computing adoption strategies for approximately ten years

Education and Location

Richard Watson holds a degree from The Open University and is based in Ireland.4

Online Presence

His LinkedIn profile can be found under the username richard-watson-852136, where he shares insights on topics such as platform engineering and cloud architecture.5 Watson's expertise and analysis in cloud-native technologies make him a valuable resource for organizations looking to modernize their applications and improve their cloud adoption strategies.2

Highlights

Apr 10 · linkedin

I am delighted to say my new note, "How to Use LIFESPAR Architecture Principles to Deliver Cloud-Native Applications" (paywall), has just been published. https://lnkd.in/ezZGPxT2

I've covered cloud architecture for Gartner for almost 15 years, and I stand behind this research I originated in the early days of cloud adoption. Gartner clients continue to look for guidance expressing the HOW and WHY of adopting cloud, and this framework is a cycle based on a set of principles I've given the mnemonic LIFESPAR. They are:

  • Latency-tolerant: Applications remain operational despite variable and extended latency for services accessed across public networks and between cloud provider data centers.
  • Instrumented: Sufficient telemetry data is available from applications to observe health and other operational and performance characteristics.
  • Failure-tolerant: Applications are resilient to occasional or extended failures of underlying platform and infrastructure components or dependent services.
  • Event-driven: Code written in event-driven style is structured as a set of handlers, waiting for events and responding in a choreographed way rather than with sequential, determined and synchronous orchestrations.
  • Secure in-depth: The application protects the organization’s data and system availability, guarding against data loss or SLA violations caused by malicious or accidental events.
  • Parallelizable: Data and application tier processing can be scaled out to multiple simultaneous and redundant instances of system components as required by an SLA.
  • Automated: Applications are packaged, deployed and executed without manual steps or complex internal dependencies.
  • Resource-aware: Applications can be adapted to different provisioning and system architecture styles, and potentially permit changes to algorithms and data structures, in response to cloud resource cost changes and the nature of those resources.

The diagram here summarizes the cloud-native architecture paradigm — relationships between goals, characteristics, LIFESPAR principles and design patterns. Our framework presents one cloud-native architecture paradigm (another example is  The Twelve-Factor App). It describes essential cloud characteristics in terms of their implications on solution architecture and the contributions that infrastructure, platform, and application tiers must make (through their capabilities) to help architects implement patterns that maximize the characteristics.

... Because the HOW (... do I architect an application?) must be driven by the WHY (... what are my cloud adoption goals?).

Feb 7 · linkedin

You've heard that Platform Engineering is a solution to achieving efficiencies and economies of scale in a DevOps environment. It's a route to improving developer outcomes and reducing undifferentiating toil. But how do you implement it in your organization? You already know the answer because it's the same combination of people, processes, technology, and culture that you need to wrangle for every major initiative. This newly updated how-to framework guides you on continuously improving teams, processes, and culture around the platform through collaboration with platform users. #platformengineering https://lnkd.in/eSGPkQve (Paywall)

Related Questions

What are Richard Watson's key research areas at Gartner?
How has Richard Watson's work impacted cloud adoption strategies?
What are some notable publications by Richard Watson?
How long has Richard Watson been with Gartner?
What is Richard Watson's educational background?
Richard Watson
Richard Watson, photo 1
Richard Watson, photo 2
Add to my network

Location

Ireland