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.

Outline/Structure of the Talk

- We explain why Continous monitoring part of Devops was important for our case
- We explain complexities and people challenges involved for us
- We share our story of how we turned pain point into a Roster system to achieved desired results
- We share best practices we used for managing the 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

Prerequisites for Attendees

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 2 years ago

Public Feedback

    • Liked Nick Balestra

      Nick Balestra - Painless Micro Frontends Delivery

      Nick Balestra
      Nick Balestra
      Sr. Engineer
      schedule 2 years ago
      Sold Out!
      45 Mins
      Case Study

      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 Atulya Mahajan

      Atulya Mahajan / Kiran Chhabra - Parenting Lessons for Agile Transformations

      45 Mins

      Agile transformations are no child's play. There is inertia, restlessness, impatience and the constant desire to run away. Traits that anyone who has been a parent to little kids has encountered, and learnt in their own way how to handle.

      This session looks at parallels between parenting and trying to influence teams through an agile transformation. We look at some of the things that successful parents do that can be done by leaders trying to take their teams through a transformation.

      Because if teams sometimes behave like children, the leader needs to be a parent too!

    • Liked Rajith Raveendranath

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

      Rajith Raveendranath
      Rajith Raveendranath
      schedule 2 years ago
      Sold Out!
      20 Mins

      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, we will look at some features that are missing in the most popular languages - C, C++ & Java for composing functionally, and some alternatives
      • Managing Concurrency, we will look at how some programming languages are simply concurrent, thus avoiding the need of managing mutability, as we often do in C, C++ & Java
      • Frameworks & Tools
      • Popularity, there are the popular ones and the esoteric, but what is interesting are the ones in betweeen

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

      We will compare the three most popular languages - C, C++, Java with some multi-paradigm languages like javascript & python and with some functional languages like Scala & Erlang.