Excerpts From “What Can DevOps Learn from Formula 1” Presentation

-

Full presentation available here.

A list of salient points follows:

  1. How to define success?
    • Developers want Agility & Change
    • Operations want Availability & Stability
  2. F1 car lifecycle
    • Design –> Develop –> Test –> Deploy –> Support
    • Support (Operations) need to always provide feedback to Design (Development)
    • Engineers need to work hand-in-hand with Operations
  3. Success must be measured
    • F1: Telemetry and monitoring are required to deliver drivers’ results
    • IT Systems: Performance data collection and analysis as well as performance monitoring are required to deliver success
    • Monitoring is critical in managing change
  4. Need to constantly monitor and manage impact of change. Need to provide feedback for where the car:
    • Is fast – where things are done right
    • Is slow – where to optimise and improve
    • Failed – where to fix
  5. Three key aspects that impact application performance
    • Concurrency
    • Data volume
    • Resources
  6. Where does one find the real bottlenecks?
    1. Not often in Development – no issues in concurrency, data volume, resource
    2. Less often in QA/ Test – concurrency issues may likely surface, resource issues may occasionally surface
    3. Often in Production – concurrency, data volume and resource issues become evident

Comments

Post a Comment

Popular posts from this blog

Understanding ITIL Service Management the UML way…

-
Image
I originally had a great deal of difficult reconciling the differences amongst ITIL Change Management, Incident Management, and Problem Management. Having researched on the subjects and understanding them better now, I’ve tried to put the concepts together using a UML class diagram to capture my understanding and to keep it imprinted. Similarly, I wanted to differentiate the various categories of changes (Standard, Emergency, Normal) using an easy to understand & self-explanatory manner – a UML Activity Diagram!
Read more

How to depict (Professional-Looking) Logical Network Diagrams in Astah

-
Image
I have always had to create (professional-looking) UML diagrams using Visio-like icons. You’ve got to admit that showing a bunch of boring UML boxes hardly interests anyone less technical (like anyone whose designation has the words “manager” or “director”). This is actually possible in Astah! I’ve created a template for future projects that allows me to produce logical network diagrams that look like the following: To create this diagram, you need to do the following: Assign various icons to stereotypes. I created the following for my use: Create a new UML Deployment Diagram Every element in the diagram is created as a Node The nodes are subsequently assigned the appropriate <<stereotype>>. E.g. Internet is <<internet>>, WebZone FW is <<firewall>>, Web LB is <<loadBalancer>> Ensure the “Icon Notation” is set to “Customized Icon” for each node Instead of the boring boxes, the corresponding icons automatically gets displayed!
Read more