From Sam Newman & Associates
After spending time at multiple startups and 12 years at ThoughtWorks, Sam Newman is now an independent consultant. Specialising in microservices, cloud, and continuous delivery, Sam helps clients around the world deliver software faster and more reliably through training and consulting.
Sam is an experienced speaker who has spoken at conferences across the world, and is the author of Building Microservices from O'Reilly Media.
Microservices are all the rage, and so are security breaches! Learn what you can do to create one without the other.
Microservices give us many options. We can pick different technologies, mix synchronous and asynchronous integration techniques or embrace different deployment patterns. But they also give us different options for how we think about securing our systems. Done right, and microservices can increase the security of your vital data and processes. Done wrong, and you can increase the surface area of attack. This talk will discuss the importance of defence in depth, discussing the many different ways in which you can secure your fine-grained, distributed architectures.
Audience: Developers, architects, technical leaders, operations engineers and anybody interested in the design and architecture of services and components.
What You Will Learn: The audience should come away with a working framework for thinking about AppSec, and also understand how microservices can help (or hinder) building a secure system.
During the evolution of the ideas behind Continuous Delivery, many of us came to the conclusion that having branches for features was not a good idea, and resulted in some fairly problematic issues. This was contentious at the time, with lots of discussion around whether or not feature toggles or feature branching was the right way forward.
Roll on several years, and through Git and GitHub, branches are everywhere. Is this a problem?
This talk re-examines the role of feature branches and feature toggles, and looks at them in the context of new research and technology to try and distill down some sensible lessons in a post-GitHub, but hopefully not post-factual, world.