There is lots of theory out there about microservice architecture, but how often do you get to put that knowledge into practice? It's not feasible to re-architect your real system often, and certainly not in a single day, or is it? This brand new training from the author of Building Microservices gives you a safe space to explore ideas behind microservice architectures with peers from other organisations. In this training, we'll share some framing for micro service architectures that explore the various forces that can drive the design and evolution of microservices, and then you'll participate in a series of interactive architectural kata exercises to put your new found knowledge to the test. Afterwards, you'll have a series of tools to take back to your own organisations to put into practice.

This training will cover:

• What makes a good microservice
• How to use concepts from domain driven design to define service boundaries
• Explore how to plan and manage a migration from a monolith to the microservice architecture
• Understand how technical choices can impact the architecture itself
• How to manage change and governance in a microservice environment

Audience

• People who are in the process of moving to micro services, or are already on the path should get a lot out of the event.
• It's primarily aimed at people in technical leadership positions like tech leads and architects, but should be of use to any developer or operations person interested in how to move to microservices.
• Prior knowledge of service oriented architectures generally or microservices specifically is useful, but by no means essential.

Microservices are great, and they offer us lots of options for how we can build, scale and evolve our applications. On the face of it, they should also help us create much more secure applications - the ability to protect in depth is a key part of protecting systems, and microservices make this much easier. On the other hand, information that used to flow within single processes, now flows over our networks, giving us a real headache. How do we make sure our shiny new microservices architectures aren’t less secure than their monolithic predecessors?

In this talk, Sam Newman outlines some of the key challenges associated with microservice architectures with respect to security, and then looks at approaches to address these issues. From secret stores, time-limited credentials and better backups, to confused deputy problems, JWT tokens and service meshes, this talk looks at the state of the art for building secure microservice architectures.