2022

Cortex Ops Team objectives

Personal objectives

  1. Objective: Understand what it takes for Cloud Native Java applications to succeed

  • Key results

    • Characterise the behaviour of Java apps running on Cortex under a range of commonly challenging circumstances
    • Understanding of key activities when moving from Java 8 or 11 to 17
      • roof: ‘most’ necessary activities flagged and quantified to customers at start of adoption cycle
      • moon: no unanticipated activities encountered during cortex adoption
    • Understanding of what is required to prepare for adoption of Spring Boot 3 (inc. Spring Native) in 2023

  • Activities

    • Join product team’s dicussions (TPRs, architecture/design meetings)
    • Investigate specific apps / configurations on corte
      • Camunda BPM
      • classpath scanning on startup (such as that triggered by autoconfiguration or data load)
      • spot instance removal
    • Maintain a generalised list of Java application requirements and implications if implemented on Cortex (‘maturity model’)
  1. Objective: Prospective users should be able to quickly make sense of our products

  • Key results

    • Onboarding time reduced from X to Y
    • customers suffer no outages inherent to platform in the first month post-migration
      • roof: 50%
      • moon: 80%

  • Activities

    • enhance detail assessment: qualitative and interactive approach
  1. Objective: Drive awareness / engagement of product teams with Cortex

  • Key results

    • Create baseline and monitor trend of engagement at C3 (e.g. absolute attendence, groups represented, questions asked, follow ups scheduled, net promoter score)
      • roof: maintain trend??
      • moon: double??

  • Activities

    • suggest visibility measures
    • publish case study (challenges and successes)
    • present at C3 (case study? Java findings from #1?)
    • C3 poll
    • mine Zoom report for attendence numbers