So you have a basic PAAS running by using Openshift, Stratos, Cloudfoundry, but you still do not achieve the perceived flexibility, or agility for that matter in being able to readily deploy to production. 

You still face similar bottlenecks or in some cases you now have new problems to take care of even after biting the bullet of time and money investments for that next-gen infrastructure management. There are still issues in the pipeline, and it is not so straight forward to put your application quickly to production. Unfortunately, organizations miss the point that it takes more than just using an Openshift or CLoudfoundry to really benefit from PAAS or PAAS like solutions. What we often forget in the world of DevOps is that it always requires changes on both sides, Dev & Ops to pull it off. 

At time you find yourself there because your Dev team hasn't looked into the factors to enable their applications to be scalable and easily deployable on a PAAS. The traditional Controller > Service > Persistence layers bundled into one will always be a huge impediment in elasticity. So we start breaking them down into simpler applications, a.k.a mircorservices, however each of these microservices themselves should be very carefully designed so as to be significantly detached from anything infrastructural or in words a platform concern than business concern. 

Let's a have a look at some of the factors to consider in your solution architecture for reaching there. Inspired by real life experiences from implementing the not so much talked about 12-factor app concept.


Outline/Structure of the Talk

  • Introduction to PaaS
  • When traditional app meets the PAAS
  • Introducing the 12-factor App
    • First steps to 12-factor
    • Where to start?
    • rethinking Continuous Integration
    • simplifying logging
    • the container as environments
  • A small live demo

Learning Outcome

  • Architectural & Design considerations in designing Apps for scalability
  • How to live in the (agreeably) complicated delivery pipeline of Microservices
  • What NOT to do when hosting Apps on PAAS
  • How to go about achieving true value with investments in DevOps automation.

Target Audience

Architects, Developers, DevOps Guys, any one from the Engineering and Operations side of the world of Software development

schedule Submitted 5 years ago

Public Feedback

    • Naresh Jain
      Naresh Jain
      schedule 5 years ago
      Sold Out!
      45 Mins

      On Agile teams, collaboration is the way of life. Our leaders want their team members to work closely with each other, have shared goals and even think as one entity. Why? Because we believe that collaboration leads to happier, more productive teams that can build innovative products/services.

      It's strange that companies use the word collaboration very tightly with innovation. Collaboration is based on consensus building, which rarely leads to visionary or revolutionary products/services. Innovative/disruptive concepts require people to independently test out divergent ideas without getting caught up in collaborative boardroom meetings.

      In this presentation, Naresh Jain explores the scary, unspoken side of collaboration and explains in what context, collaboration can be extremely important; and when it can get in the way or be a total waste of time.

    • Vinay Krishna

      Vinay Krishna - BDD - an effective way to collaborate among 3 amigos - Testing is just a by product

      90 Mins

      A common misinterpretation is that BDD is another way to automate the functional testing or just a synonym to Acceptance Test Driven Development (ATDD). However, it’s not correct understanding. BDD doesn’t talk about testing rather it focus on development which is driven by expected behaviour of application/system. It helps to share the understanding by examples among three amigos (BAs, Developers and Testers) and helps to explore unknown. It describes what business/end users want the system to do by talking through example behavior.

      In this workshop, the actual concept of BDD is explained using case study of various real-time projects. It also covers the myths, challenges, benefits and best practices along with tools used to adopt it.

    • Anadi Misra
      Anadi Misra
      Agility Roots
      schedule 5 years ago
      Sold Out!
      480 Mins

      This session provides an introduction to DevOps, the cultural phenomenon that is enabling organizations to develop, deploy and operate quality software faster to meet business needs. This course introduces attendees to the goals, objectives, benefits, achievements and practices in a DevOps environment. The course also looks at the relationship with underpinning practices such as Agile, Lean, ITIL/ITSM and Continuous Delivery. This is a four hours introductory session that tells about DevOps in a very business oriented language and is aimed at the following target audience.

      • Senior IT Management wanting to gain an understanding of DevOps’ IT and business benefits
      • Software developers, engineers, managers, consultants or anyone involved in application development
      • IT Operations teams, management, professionals and consultants
      • Managed service providers
      • Service Management process owners, process managers and consultants
      • IT professionals working within, or about to enter, an Agile environment
      • Business stakeholders interested in learning about DevOps
    • Anadi Misra

      Anadi Misra - The no-obviate DevOps

      Anadi Misra
      Anadi Misra
      Agility Roots
      schedule 5 years ago
      Sold Out!
      45 Mins

      A lot of enterprises have trouble in starting to practice DevOps, steps like making a "DevOps Team" are common amongst large enterprises. Needless to say such teams see a lot of resistance, not only on the tooling but processes and practices front also when they try to practice DevOps. Starting to do DevOps is not as much about removing things from the system and put in something dramatically new as it is about creating an ecosystem based on well know principals of managing operations and the relationships between those who develop to those who manage. This ecosystem has to evolve into a state of being and is not built up by adding random pieces of automation or throwing in a new profile of engineers.

      We need to simplify our thought process and look into the basics for the three ways, what is CAMS and how to go about bringing in all the four pillars into practice for benefiting from DevOps as a practice.

      The talk aims at explaining how DevOps practices in-fact benefit from tapping into existing Lean, and ITSM practices hence making the transition with lesser heart burns and frictions.