The Subject They Don’t Teach : What’s Post-Deployment

When we talk about Agile methodologies then focus on just delivery is not enough. There is life beyond delivery, and very often a product makes or breaks its destiny during that phase.
The Devops process itself is more than Continous Integration/Deployment, and it is important to know the other Cs of Continuous Monitoring and Continuous Operations as well.
We will share a case study for a team that had to sustain fast-paced releases with a large customer base. Agile, Continuous Integration and Continuous Delivery were not just fads for them but needs for survival.
This system turned out to be a big success story and thus we went ahead and replicated the model in the rest of the organisation.
 
3 favorite thumb_down thumb_up 1 comment visibility_off  Remove from Watchlist visibility  Add to Watchlist
 

Outline/structure of the Session

- How is Devops misunderstood
- How are Devops and Agile related
- What are 5 Cs of Devops
- We pick one C of Devops and share our story
- We share some best practices in terms of managing the Devops process efficiently

Learning Outcome

- Build an appreciation that the Agile process doesn't stop at production delivery
- Build an appreciation of the human element in the devops process
- Look at a new system to better manage support issues
- Understand how best to manage the Devops process with an eye at continuous improvement, further beyond the standard CI/CD tools.

Target Audience

Software engineers, Managers, Product managers, Operations managers

Prerequisite

The participants should have a basic understanding of what Agile delivery processes are all about, what do Continuous Integration/Deployment stand for, and how the entire delivery life cycle plays out, to best appreciate the content of this talk.

schedule Submitted 1 week ago

Comments Subscribe to Comments

comment Comment on this Proposal
  • Naresh Jain
    By Naresh Jain  ~  2 days ago
    reply Reply

    Thanks for the proposal, Kiran. This is an important topic and a case study to explain the same is great. However, I see a disconnect between the session outline and learning outcomes. Can you please explain how the outline will lead to the proposed learning outcome?

    Also, can you please share a video from your past presentations? This will help the program committee understand your presentation style.


  • Liked Nick Balestra
    keyboard_arrow_down

    Nick Balestra - Painless micro frontends delivery

    Nick Balestra
    Nick Balestra
    Senior Engineer
    OpenTable
    schedule 2 weeks ago
    Sold Out!
    45 mins
    Case Study
    Intermediate

    While microservice architectures allowed teams to scale delivery of independently deployable services, most frontend layers are still run as monolithic applications. Similar to server-side applications, frontend layers often grow into large monoliths that are difficult to maintain and evolve. Building, deploying and consuming frontend components across a diversity of teams and web applications can be a daunting task, especially at scale. To address this issue, at OpenTable we enable fast-moving teams to easily build and deploy front-end components using OpenComponents, an open-source, battle tested, front-end microservice architecture for painless component delivery.

    The idea behind micro frontends is to enable multiple teams to work seamlessy together by fostering end-to-end ownership of independently developed, tested and deployed features.

    Think about UI as the composition of features which are maintained by independent teams. These teams could be cross-functional allowing them to develop such features end-to-end, from a database to user interface and independently deploy them.

    During this session I'll explain how OpenComponents works, how do we use it at OpenTable and how we allows teams to build ship and consume frontend components at runtime across teams and web applications at scale.

  • Liked Rajith Raveendranath
    keyboard_arrow_down

    Rajith Raveendranath - Developer at a Crossroads - Choosing a suitable programming language for Microservices

    Rajith Raveendranath
    Rajith Raveendranath
    Director Quality
    SunTec
    schedule 2 weeks ago
    Sold Out!
    20 mins
    Talk
    Intermediate

    How to choose a suitable programming language for developing Microservices?

    We start our discussion with the most important characteristics of Microservices.

    The following aspects of programming languages are discussed, keeping Microservices in mind:

    • Functional Composition
    • Managing Concurrency
    • Frameworks & Tools
    • Popularity

    We conclude by comparing some popular programming languages using these and drawing some inferences