It is very easy to spin up a microservice, and it is getting more common for organisations - even traditional enterprises - to create a large number of microservices. While "what is the right number of microservices to have?" is a separate debate, whatever that number is, it is now much harder to secure a system than before.

What used to be a single process call in a monolith, spans to multiple calls all over the network, thereby increasing the surface area of attack.

In this talk, you will learn about the context of security in a microservices world and different patterns to secure your services.

The world is always changing. Organizations, traditional enterprises & startups alike want to build systems for the changing world, and they jumped into Microservices hoping they can stay ahead of competitors and be a true disruptor in their domain.

As Sam Newman said, "If we have to reap the true benefits of Microservices architecture, we need to worry much less about what happens inside a service than what happens between the services”. Without a clear understanding of those inter-service interactions, we might end with a distributed microservices where the services are still coupled to some degree. To me, it is just a nice distributed monolith.

Inter-service interactions can be better understood by an event-driven mindset. In the real world, the events drive actions and reactions. The event-driven approach is not anything new, but putting events as a first class citizen will fundamentally shift how systems are designed and make it seamless to think in terms of actual domain models.

Let us talk about the patterns, challenges, and benefits of looking at events as first-class citizens and see how if it is done correctly, it not only solves the problem for today but also enables us to be ready for the future.

No one has escaped the "Microservices" wave recently. As every architecture brings with it a lot of good practises, microservices brings success by helping us achieve a faster to market releases. Though the concept of "two-pizza" teams has been prevalent from early 2000’s, we now have many successful poster children to learn from. The success in this journey depends on infrastructure, automation, architecture and process elements. These includes good CI practises, different testing approaches, dynamic service registration & discovery, orchestration, logging and tracing. Though they are familiar, we all know that it is not as easy as it sounds, let us see what we need to consider from start to finish to make Microservices journey a real success in a 'show and tell' format.

Sneak Peek of what to expect: A bit of many concepts with corresponding tools including CI, Microservices, Docker, Consumer Driven Contracts, Service discovery, Consul, Registator, Multihost deployments, Kibana, Elastic search, Prometheus