Meet our Speakers
Armagan Amcalar
Armağan Amcalar is a software architect from Berlin. He is creating the future of mobility as the Head of Software Engineering at unu. As a university lecturer and a mentor, Armagan teaches JavaScript and software architecture in various contexts. He has created several open-source frameworks and projects on GitHub. As a public speaker, he loves to speak about software in international conferences all over the world.
Topic
Mindset, infrastructural and organizational changes to adapt to microservices
Microservices are taking the world by storm and it’s more than just an architecture — in order to fully function, microservices approach needs a transformation in your development teams and total commitment to several best practices:
- Change. Change is inevitable. Code, dependencies, deployment and release processes will change.
- DevOps. Developers will own the release and every intermediate step has to be automated and kept in code.
- Eliminating hierarchy within the team and increasing autonomy.
This talk will go into detail on what you need to change in order to properly adopt microservices in terms of mindset, infrastructural and organizational changes as well as the benefits that will be obtained as a result of such changes. The lessons are learnt the hard way and this talk is based on a true story — the transformation of development teams at unu GmbH.
Workshop
Time: 10:00–16:00
Venue: Deworkacy, Red October
Language: English
Accessible Microservices
The concept of microservices is hot and it draws many developers from a diverse background. Unfortunately, we see a lot of ideas from the past rebranded as microservices; whereas the thinking behind microservices imply and promise a bigger change. This talk will go over the details of what actually makes a microservices architecture and how other distributed systems — that rely on queues and other mechanisms to function — fail to fulfill the promise.
A modern microservices implementation should be:
- Zero-configuration: any microservices system will likely have hundreds of services. A manual configuration of IP addresses, ports and API capabilities is infeasible.
- Highly-redundant: service failures are common in this scenario. So it should be very cheap to have copies of such services at disposal with proper fail-over mechanisms.
- Fault-tolerant: the system should tolerate and gracefully handle miscommunication, errors in message processing, timeouts and more.
- Self-healing: it’s normal for outages and failures to occur. The implementation should automatically recover any lost service and functionality.
- Auto-discovery: the services should automatically identify new services that are introduced to the system to start communication without manual intervention or downtime.
This training will implement such an implementation with Node.js and Docker Cloud. It’s a hands-on training and participants will enjoy building and managing a real-life microservices app in a cloud of their own choice.