Microservices promise faster development, deployments, scaling and all the goodies you always wanted but never had.
Sessions in the Microservices track at GOTO Copenhagen 2016 include real life cases on how to and how not to implement microservices, focusing on both the people-side and technology-side of the migration process from a monolithic system to a microservice based architecture. These talks seek to answer questions like: “What challenges do you meet when both systems and teams are distributed?”, “How do you withhold or even increase you current level of security when moving to a fine-grained distributed architecture?” and “Can a microservices architecture help you to get more empowered and autonomous teams?”
Watch the videos from the Microservices track at GOTO Copenhagen 2016 below.
AppSec and Microservices
with Sam Newman, Author of Building Microservices
Microservices are all the range, and so are security breaches! Learn what you can do to try and have 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 in 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.
Microservices: A utopian mystery
with Praveena Fernandes, Software Engineer at Neo4j
Microservices promises faster development, deployments, scaling and all the goodies you always wanted but never had. Highly scalable services like Netflix and Soundcloud have successfully integrated micro services not just as a way of application development, but as a structure of how the organisation runs. Over the past year, I have worked on a transformation project which was inspired from success stories of these organisations and adopted micro services to help move away from a monolithic system to deliver value to end users quickly and reliably. We were often faced with cultural, technical, and geographical challenges around harnessing the goodness of micro services which is very different from adopting them in a startup environment.
In this talk, I share my top lessons – these include both successes and failures – which were often difficult to digest. Most importantly, I share the successes that at the time, looked like failures.
Microservices in Go
with Matt Heath, Engineer at Mondo
Moving to a microservice architecture and embracing a cloud native approach is a complex challenge, which often requires re-evaluating our approach to technology. Having previously helped transition Hailo to a a new microservice platform, built almost entirely in Go, Matt leverages modern technologies and a microservice based approach to build reliable platforms which can scale to millions of users. This talk will cover how to develop and migrate to a microservice based architecture using Go, common pitfalls to avoid, and lessons learnt when developing high volume, low latency, distributed applications.
Reclaim the stack: Why cross-functional teams build better microservices
with Peter-Gillard Moss, Head of Technology for Thoughtworks Technical Operations
Thoughtworks operates across 34 offices in 12 countries. And its operations department is no less complicated. We have teams of developers all over the world working on integrations, bespoke apps, vendor management. On tight budgets and a demanding army of software professionals to answer to and cater for it’s a tough act, especially distributed. Yet we’re not unusual.
Traditional agile approaches weren’t working. Monoliths were entrenching pain. Tech debt was racking up.
Microservices and cross-functional teams allowed us to ’embrace the craziness’ that is ThoughtWorks. Teams became empowered and autonomous. But it is not without its hurdles and challenges. In this talk I’ll present the lessons we’ve learnt on our journey.
Distributed – of Systems and Teams
with Bridget Kromhout, Principal Technologist for Cloud Foundry at Pivotal
We endeavor to build consistency, availability, and fault tolerance into our distributed systems, but how do we build them into our teams? The human factors in devops require as much attention as do our technical implementations.
Collaboration, understanding, trust: we know how important these interactions are in a devops practice, but how do we enable them between disparate team members, especially in a distributed team? My company’s in California, and I’m over three thousand kilometers away in flyover country, USA. Being one of those little squares at the bottom of every video call gives me an outsider’s perspective on the inside of our organizational optimization.
Drawing in comparisons from theoretical computer science and practical systems implementation, I explore how building understanding requires a practical application of great tools in a deliberate pursuit of a constructive culture.