Software 4.0 is the ethereal power behind the Digital Revolution.

What is Software 4.0?

It is distributed, multi modal, reactive, API first and Elastic. And much more.

The talk is a back to basics view of Software 4.0 and the ABCs that define it.

A simplified view as this would help the engineering teams, overwhelmed by the plethora of keywords and expectations, to get started with their digital transformation.

An experience share about how we achieved high performance transaction pricing with elastic scaling, for a big T in the US, using Micro-services and Flow Based Programming.

We start with the challenges faced by the telecom operator in their All IP access network which necessitates high volume, low latency transaction processing.

We discuss the Micro-services advantage which let us build responsive, resilient and elastic services.

We further discuss the FBP edge, which help us manage the big data effectively and also work as an event driven framework for Micro-services

We will have a short discussion on the software stack used.

We conclude by sharing the results and the lessons learnt

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.

[Update based on the panel review]

Inspired by Martin Fowler's introduction to micro services (https://www.youtube.com/watch?v=wgdBVIX9ifA);

The demo will introduce the "ABC"s of the transition to micro services. We will refer to the Hadoop Distributed File System open source and demonstrate to (re)design the NameNode module as a micro service. This will introduce the three primary challenges and their possible solutions as in;

1. Componentize using Services instead of the conventional componentization using the design

2. Data segregation using an event driven framework to separate the centralized data across services

3. Accessing a micro service as a web service instead of an orchestrated access; the delegate & facade patterns will be demoed to loosely couple the interfaces

The demo will conclude with a listing of the next steps in transition, which need to be considered after the primary challenges are addressed.

The setting up phase of DevOps is like the Opening Game in Chess. A good opening can give us advantage for the remaining games. As in chess, there are "book moves" in the Opening Game of DevOps that may be played to our advantage.

Based on my experience in setting up DevOps in an overseas eCommerce platform project with world wide deployment, I will be sharing these book moves as aphorisms in each of the three stages of the build pipeline.

Some of these good practices will be demonstrated in GitHub using some open source projects and the CI tools used in Git Hub.

In the concluding part, we will look at some conventional traps which may hindering the devops in your project context to deliver on its promise and consider some alternatives which we have discussed in the earlier part of the session.

In Agile Teams, Testing acts as a safety net and helps doing any kind of development and change seamlessly. The confidence when the Continuous delivery system give a Pass signal comes from the quality of the test . Test code lives as long as the code lives.

But strangely, though enough buzz  and importance is there on the continuous delivery, deployment and devops practices but some teams don't give equal priority to the deeper testing practices.

In this presentation Anish along with Rajith will explore the anti patterns of Agile Testing and provide overview about the Onion Layered Test Practice Map (Task, Story, Sprint, Release Level). Without good test practice and quality test, continuous delivery may only give false confidence.