Join the Summit

Do not miss out on the most updated DevOps Summit!


DevOps now is in its 10th year of practice but the old architecture is no longer able to support the speed of delivery and so needs the additional help of Microservices for incremental change. Microservices architecture helps to deliver easy testing, fast deployments and overall agility. It is also fairly complex—so to successfully implement Microservices, you need to understand the core concepts behind this approach. Adopting a new capability requires a plan that includes people, process and technology.

DevOps too is an enterprise capability and as the name suggests development and operation-based way of working that includes stakeholders, business owners, architecture, design, development, quality assurance, operations, security, partners and suppliers.

DevOps has been seen as something for the tech-people, no matter if they are developers or from IT support. In reality DevOps is about the culture of working together and automating everything that is repeated. This means that everyone in the organization should be involved and brought together; business, developers, quality assurance, contractors and IT operations. And most importantly, the management. We will have technical demos and workshops which require a certain level of technical expertise, but there will always be simultaneous events scheduled at the same time for more business oriented professionals.

Benefits of Attending
This two day programme is designed to connect these extensive aspects as well as the challenges. Expert practitioners and thought leaders will provide information on the implementation and help you to deepen your understanding and develop your business case and build towards getting significant return on investment.




Our Speakers

  • Venugopal Bangalore Krishnappa


  • Jyothish Cherian

    GE Digital


    Amadeus Labs

  • Amit Kumar Singh

    MediaKind Solutions

  • Ashish Srivastava

    ITC Infotech

  • Shripad Hebbar

    MediaKind Solutions

  • Vivek Ganesan

    Author & DevOps Enthusiast

  • Kiran Kashyap

    Société Generale

  • Raghothama Vijendran


  • Manoj Philip Mathen


  • Ramesh Krishnamurthy


  • Stalin Mahapatra


  • Rajat Goyal


  • Dinakar Guniguntala


  • Venkatesh P

    Mavenir Systems

  • Jeeva Chelladhurai

    Comorin Consulting Services

  • Ishant Kumar


  • Manojkumar Nagaraj


  • Deepa Talwaria



Dr. Shankar Ramamoorthy, Professor- Information Science Engineering, Head - Industry- Interface, CMRIT

Topic Abstract

Container technologies are the next stage of evolution after virtual machines. VMs need a lot of system resources, because each VM runs a full copy of an operating system and virtual copy of all the hardware that the operating system needs to run. Translation: lots of RAM and lots of CPU cycles.

Alternatively, one can run all your containers on a single operating system instance. As a result, a physical server can have several multiples of times more containers compared to virtual machines. This makes containers much cheaper than virtual machines, while also giving additional advantages regarding the portability and standardization of runtime environments. This also makes containers the go-to solution for cloud platforms.

Microservices Architecture
Microservices use a lot of SOA concepts, but especially emphasize the self-sufficiency and independence aspects of services. Each microservice is developed, tested, and deployed independently, and each one runs as a separate process. The microservices architecture pattern attempts to fix the mistakes of SOA implementations—large monolithic ESB applications. Some of the key design considerations for microservices are:

  • They implement true loose coupling. Each microservice must be independently deployable, and as a consequence, they should also be physically separated from each other.
  • They perform one piece of functionality and are not reusable across multiple services.
  • One should able to use whatever technology you want to build each one, since they are all independent of each other.
  • Once we publish the service interface contracts in advance, one should be able to develop, test, and deploy the microservices in parallel tracks. This considerably cuts down on time-to-market.

A microservices architecture makes it much easier to deal with technical debt. New functionality can be developed and deployed with the existing application if these new modules are independently deployable. Also, one can changes to the existing application much more easily if the application was designed to have independently deployable functionality modules.

Continuous Delivery
One can extend any continuous integration pipeline into a continuous delivery one. The major difference between the two is the level of confidence people have in the automation processes of the continuous integration pipeline. CI needs a number of manual interventions (config changes and tests) from the operations team, all of which can be automated to a very high degree, if not completely. One major factor is mutable versus immutable deployments.

Putting them all together–MAGIC!
Continuous delivery, micro services architecture, and containers are most effective when used together within an agile development environment. The provide the needful Magic for successfully delivery and supply chain success.

Arun NARAYANASWAMY, Director Engineering, Amadeus Labs

Topic Abstract

Federated DevOps is the need of the hour in the Agile rapid pace of changing devOps landscape. This talk will dwell on the benefits and structuring of DevOps tooling and how we can reap its benefits. There's a difference between being on the bleeding edge and being a successful follower. There is also a limitation on organizational governance and policies. How to bridge this gap? How to be innovative? And how can you be the leader in adopting the best of the tools

Jyothish Cherian, Head - Data Lake, GE Digital

Topic Abstract

The session will cover the Micro-service Design Patterns and when to use the micro-service architecture? I will also be covering the Advantages Of Micro-service Architecture and how some prominent companies are using it to their advantage. I can talk about examples from Netflix and Amazon and then showcase their micro-service architecture. I will talk about the Technological Flexibility of Micro-service and how to achieve High Cohesion Combined With Loose Coupling. I will also have some AWS related micro-service examples. Then I will move on to API Integration that is used to integrate the entire architecture. I will talk about How to decompose the application into services and How to maintain data consistency? Then some ground will be covered in Automating The Process and finally will touch upon the Limitations Of Micro-service Architecture.

Venugopal Bangalore Krishnappa, Head Of Professional Services, Equifax

Topic Abstract

The hot skills fo 2020 and future is Devops, Data Science, Cloud and RPA. If each of these work in silos then an organisation will not be able to achieve the synergies associated with integrated approach of using Devops with Data Science and Cloud platforms.

During this session : The following candidates can will get exposed to "
1. Practical Cases of how Devops been used during critical stages
2. Current Scenarios how Data Scientists work in an organisation - Key Pain Areas
3. Reference Architecture Architecture of Devops, Data Sciencits, and Cloud
4. Suggested integrated Approach for Devops and Data scientist - Technical Canvas
5. AS IS Case to TO BE Situation
6. Key Challenges in implementation

Though this presentation is primarily mainly focussed for CXO levels, participants from Managerial level, Statisticians, Developers and Datascientist can be benfittted seeing wholistic picture of Integrated approach.

Raghothama Vijendran, Senior Director, Software Development, Oracle

Manoj Philip Mathen , Software Architect , Oracle

Topic Abstract

Software Test Cycles involves several manual, repeated activities that has to be performed every time there is a feature / product release. This not only involves testing the new feature but also testing to ensure no existing feature is broken (Regression). In this session, we will present the blueprint of our platform agnostic automated test framework – SPyDER.

SPyDER is a self-learning / self-healing intelligent automation suite that knows what and when to test based on analytic inputs from system / application logs. We will discuss how similar platforms can be build leveraging AI/ Machine Learning algorithms. The end result could be an intelligent Machine Learning based Test BOT that can replace human testers (when it comes to repetitive, manual testing). This will accelerate test cycles and facilitate a speedy movement of the code through the CI/CD pipeline for instance.

Shripad Hebbar, Global Test Director, MediaKind Solutions

Amit Kumar Singh, Senior Technical Lead, MediaKind Solutions

Topic Abstract

Shift Left Testing – Objective of Shift Left Testing is detect failures early by Test early and often. The longer it takes to discover software flaws and defects, the more expensive it is to address them. A bug discovered during testing costs 15 times as much as it found during design.

Shifting left requires two key DevOps practices: Continuous Testing and Continuous Deployment. Inverting the Traditional Testing Pyramid for Shift Left Testing is a DevOps mantra for Continuous Software Testing

Continuous Testing – Continuous Testing is a strategy of evaluating quality at every step of the Continuous Delivery Process. This involves a process of testing early, testing often, test everywhere, and AUTOMATE in order to obtain feedback on the business risks associated with a software release candidate as rapidly as possible.

Automation is a key component to shifting left because it reduces the effort and time required to perform testing, configuration and deployment activities. Continuous testing involves automating tests and running those tests as early and often as possible, along with service virtualization to mimic unavailable systems. Test automation tools and platforms allow creating test automation flows for unit, integration, regression and acceptance tests.

Configuration management tools like Puppet, Ansible and Salt-stack allow automating the configuration and deployment of software and infrastructure to make the build, test, and deployment process more repeatable. Container technology offers a unique way to shift development and test activities to the left. Containers allow multiple applications and their dependencies to be bundled in a container that can be easily created or destroyed on the fly without any additional automation, making it easy to create and store predefined application environments for development and testing. Business Case of a Media Platform – Cross Browser Testing, integrated with Continuous Integration pipeline

For a Media Platform, an Application Under Test (AUT) need to be tested across hundreds of browser OS and real device combinations. This ensures the media application on websites and mobile apps work flawlessly with every release for a comprehensive coverage to rapidly deliver flawless digital experiences.


  • Test Automation for Continuous Testing
  • ~ 100 vm’s hosted on private openstack data center
  • Built an in-house selenium grid infrastructure using few opensource projects for our automation testing requirements
  • Once a code checkin is done to master branch, for every checkin, auto-run over 500 tests against multiple browsers & platforms (chrome/firefox/ie11/edge/OTT STB) across windows/linux/mac and android 1ft emulator
  • manage > 100 vm’s using Ansible to automate the software deployment on windows /linux and mac vm’s
  • Benefits –
  • Dashboards similar to any cloud provider, to keep track of cases executed on different browsers with video/log file and test result data
  • Effective Test Coverage, testing across multiple browsers
  • Easy maintenance and effective management of over 100 VMs

Ashish Srivastava, General Manager & Consulting Partner, ITC Infotech

Topic Abstract

Based on the growing business and future scalability forecast, Airline needed a proactive IT with an efficient Enterprise Architecture, which understands business goals and proactively works on business solutions. This case study about a leading Airline in India, and its transformation journey through the DevOps adoption

Case Study Topics:

  • Case Study for Implementing NextGen DevOps for one of India's largest Airlines
  • Business Challenges
  • Pre-DevOps Era
  • DevOps Adoption by Airline
  • Resistance to Adopt DevOps
  • Infusing new DevOps Culture
  • Clever Tricks to adopt DevOps
  • Benefits and ROI for the Airline

Ramesh Krishnamurthy, Chief Technology Officer, Indium

Topic Abstract

More & more applications are developed & deployed on the ‘Cloud’. Governance & compliance are getting tougher to meet as data privacy is one of the biggest concern to customers world-wide. Vulnerabilities in applications have much bigger ramifications than ever before. Shift-left approach for Security is ideal scenario to unearth any vulnerabilities early in the development cycle. Are you developing a secure application is more important question today than ever before!

The 60 min presentation will detail the aspects on how to build a secure product right from the beginning. DevOps have make many tasks automated and with Security into the gambit, DevSecOps is a good model for everyone to adopt. The presentation will cover a live example of a DevSecOps model.

  • Global compliance & standards
  • Shift left approach
  • DevSecOps: Why one should adopt?
  • Working model
  • Q&A

Venkatesh P, Vice President - Engineering and Global Head, Mavenir Systems

Topic Abstract

The need to ensure quicker high-quality deliverables consistently is the need of the dynamically changing competitive Telecom sector. Right from having new features to world class user experience is given.

Dev-Ops is just not a process transformation with new tools, it is a means to achieve better integration between Developers, Testers, IT Operations and Deployment. Dev-ops is a culture guided by principles of high coding standards with infrastructure as code, Automation, continuous integration, continuous delivery, seamless deployment backed by set of Dev-ops tools based on different criteria’s.

The DevOps approach accompanied by agile development methods like “Sprints” and “Scrums” is to implement a CI/CD pipeline for the end customers. The agile methodology is driven by the vision to minimize the time-to-market of innovations in telecommunication services. In the Process Framework architecture, DevOps is the preferred working-model.

In the session, I will be taking the use case of one of the biggest global telecom player and how they make use of different Dev-ops tools to achieve the objective of delivering new features with the right quality and enhanced customer experience.

For the use cases illustrating the requirements above I will share on the tools for

  • Requirement Management
  • Bug/Issue Management
  • Config, code, repositories
  • Audit, Build and Test
  • Deploy and support

Manojkumar Nagaraj, Senior Director , Capgemini

Deepa Talwaria, Program Manager, Capgemini

Topic Abstract

Security testing is gaining importance day by day whether the applications are hosted on cloud, on-premises or even hosted internally for internal consumption. The cost of security breaches and impact on organization brand, customer experience and financial liability is turning many organizations to look at industrializing this as part of their overall testing strategy and approach within SDLC.

The security breaches can happen both Application level and Infrastructure level. However, the industry data says most security breaches today are from application vulnerabilities. Application security is very complex as every application development involves one or more aspects like inclusion of legacy software, usage of open source, procured or commercial software along with development of new code. Today’s security testing is handled outside of the SDLC in some of the organizations independent of Agile or Waterfall shops. However, this has resulted in higher defect leakage into production causing much pain financially and quality wise. The paper talks about handling the best practices of security testing delivered through DevOps approach for the Organizations adopting Agile and DevOps methodologies for rapid development. The proposed solution recommends integration of security testing whether at Binary or source code level into SDLC. The concept of integrating security testing through DevOps approach is called as DevSecOps which provides the rigor in embedding the security testing using shift left and right approaches offering the coverage and quality. Whether the code is tested in progressive or regressive cycle, the proposed DevSecOps process provides solution to Automate the security testing in an industrialized way.

The key business benefits are better code quality, cost reduction and speed of delivery, achieved by early detection and fixing of security issues during the development phase.

Ishant Kumar, Sr. DevOps Engineer, Adobe

Topic Abstract

Vivek Ganesan, Author & DevOps Enthusiast

Kiran Kashyap, Scrum Master, Société Generale

Topic Abstract

Does your unit test suite take an obscenely long time to run? Do you want to optimize the cost of testing, without resorting to traditional cost-cutting stuff?

Do you still use debuggers for fixing production defects? Do you crave for an easier way to manage test cases written by developers?

Do you understand TDD but don't know where to start writing the first unit test case?

If you say yes to any of the above questions, this session is for you.

This demo-driven talk will help you understand

How to start with TDD in a brownfield monolithic application? How to organize test cases with cost efficiency and time efficiency as goals?

How you can demonstrate the above concepts to your team, in your office, by using an open-source code repo?

Jeeva Chelladhurai, Author & Founder, Comorin Consulting Services

Topic Abstract

1. Introduction to Infrastructure as a Code (IaaC)
2. Overview of Terraform, Packer and Ansible
3. Hands-on Cloud Deployment automation using Terraform, Packer and Ansible

Stalin Mahapatra, Architect, Amadeus

Rajat Goyal, DevOps Expert, Amadeus

Topic Abstract

This workshop aims at providing a hands-on experience on Kubernetes by executing an application in a cluster and ensuring it scales; leveraging several aspects of Kubernetes. Agenda details

  • Understanding Kubernetes Architecture
  • Creating 3 node Kubernetes cluster (1 Master and 2 Worker Node)
  • Building a stateless application in Java and run it in docker container.
  • Deploy the Application into the Kubernetes cluster
  • Different ways to expose the application
  • Scaling application
  • Secret Management
  • Logging & Monitoring of the Kubernetes Cluster

Dinakar Guniguntala, Runtimes Cloud Optimization Architect, IBM India Private Ltd

Topic Abstract

In this session learn about Kabanero, a new, free and open source framework that helps you to develop apps for container platforms and provides a harmony between developers, architects, and operations. Modern microservices development is very challenging to developers and operations alike. Developers need to understand new technologies such as Docker, Kubernetes, Istio etc and Operations admins need to keep up with a fast paced development lifecycle where hundreds of commits can happen in a single day. Ideally we need a framework that can hide all of the deployment complexity from Developers and automate the build / test / packaging / deployment to help the Ops admins.

In this session we will demonstrate an end to end work flow and delve into each of the different aspects of the build to deploy lifecycle that can help Developers and Ops admins alike.

Sizing a docker container can be very tricky as can be attested by Ops admins !. If the container is sized smaller than needed, it can get killed, larger than necessary, leads to idle resources, worse still, you are paying for that ! Current methods requires us to monitor workloads through tools such as Prometheus and then guess the container limits and hope for the best. This talk explores the use of a Free Open Source tool that can help you with right sizing your container. We will walk through a demo where the tool runs in a kubernetes cluster and monitors the resource usage including the heap, native memory, cpu and I/O usage. It then produces a yaml file used for kubernetes deployment that has the right set of limits filled in. Not only that, the tool also can help you tune Java workloads by suggesting the right set of GC / JIT parameters based on observed values and user requirements (Eg, throughput or resource usage, startup time) This can vary by the Runtime and the vendor Eg, Java/Hotspot, Java/OpenJ9, or even other language runtimes such as node.js.


Royal Orchid Central Bangalore


Manipal Centre, 47/1, Dickenson Rd, Yellappa Garden, Yellappa Chetty Layout, Sivanchetti Gardens, Bengaluru, Karnataka 560042

Phone: 080 2558 4242

Register For Any One Day

Register For Both Days


Standard Price : Rs 60,000 +GST

You can choose to strategically brand your organisation as per the below offer

Package includes:

1.Speaking Slot - 30-45 minutes

2.One additional pass apart from Speaker

3.Space to keep standees/roll-ups

4.Website Branding and cross-linking to your website

5.Logo on Agenda

6.Name Tag Branding

7.Brochure Inserts - You can bring along offerings of your services/products. We will add them as part of the conference kit

8.Social Media Promotions about your company sponsoring the event




Confirm your CANCELLATION in writing up to 15 working days before the event and receive a refund less a 10% service charge. Regrettably, no refunds can be made for cancellations received less than 15 working days prior to the event.

However, SUBSTITUTIONS are welcome at any time and is done at no extra cost. The organisers reserve the right to amend the programme if necessary.

Important Disclaimer:The organizers reserve the right to make substitutions or alterations and/or cancel a speaker(s) if deemed necessary by circumstances beyond its control.

INDEMNITY: Should for any reason outside the control of UNICOM Training & Seminars (P) ltd (hereafter called UNICOM), the venue or the speakers change, or the event be cancelled due to industrial action, adverse weather conditions, or an act of terrorism, UNICOM will endeavour to reschedule, but the client hereby indemnifies and holds UNICOM harmless from and against any and all costs, damages and expenses, including attorneys fees, which are incurred by the client. The construction validity and performance of this Agreement shall be governed by all aspects by the laws of India to the exclusive jurisdiction of whose court the Parties hereby agree to submit.