Have something to share about engineering practices, architecture or DevOps?
Become a speaker now

Archive for November, 2018



Learning the Three Types of Microservices

Microservices is a popular, but vague term. And — it turns out — definitions of microservices can vary, depending on what you want them to accomplish and how you want them to communicate with each other. So, just what are the three types of Microservices, what makes them unique, and when do you deploy each of them?

In this wide-ranging talk, you’ll learn the difference between Stateless, Data-Centric, and Aggregator microservice models, how to identify which one you need to build, and the challenges to keeping each of the up and running in a complex distributed system. You’ll also learn how to apply Nygard’s Stability Patterns (from his book, “Release It!”) to ensure your Microservice components are stable and resilient throughout the software lifecycle.

Whether you are new to Microservices or a veteran, a software developer or enterprise architect, this talk will help you get a handle on how to design and build successful Microservice components for you organization.

Master of Code Team

Continuous API Management

A lot of work is required to release an API, but the effort doesn’t always pay off. Overplanning before an API matures is a wasted investment, while underplanning can lead to disaster. This practical guide provides maturity models for individual APIs and multi-API landscapes to help you invest the right human and company resources for the right maturity level at the right time. How do you balance the desire for agility and speed with the need for robust and scalable operations?

Based on the newly-released O’Reilly book “Continuous API Management”, this talk covers :

* Learn which API decisions you need to govern and how and where to do so
* Design, deploy, and manage APIs using an API-as-a-product (AaaP) approach
* Examine ten pillars that form the foundation of API product work
* Learn how the continuous improvement model governs changes throughout an API’s lifetime
* Explore the five stages of a complete API product life cycle
* Delve into team roles needed to design, build, and maintain your APIs
* Learn how to manage your API landscape—the set of APIs published by your organization

Mike Amundsen

An internationally known author and speaker, Mike Amundsen travels the world consulting and talking about network architecture, Web development, and intersection of technology and society. He works with companies large and small to help them capitalize on the opportunities APIs and Microservices present for both consumers and the enterprise.

Amundsen has authored numerous books and papers. He contributed to the O’Reilly Media book, “Continuous API Management” (2018). His “RESTful Web Clients”, was published by O’Reilly in February 2017 and he co-authored “Microservice Architecture” (June 2016). Amundsen’s 2013 collaboration with Leonard Richardson “RESTful Web APIs” and his 2011 book, “Building Hypermedia APIs with HTML5 and Node”, are common references for building adaptable Web applications. His latest book “Design and Build Great APIs” for Pragmatic Publishing is scheduled for release in early 2019.


CI/CD Infrastucture as a Code

This talk is about how we integrate Jenkins with LDAP, Nexus, Nginx, Docker Swarm, Terraform to bring re-usable self-service CI/CD development platform delivered strictly from sources and why we use this set as a single point of integrations. Some insights on our open source project “DJEG”: https://github.com/shalb/djeg.

CyberBionic Systematics



DevOps Types and Anti-patterns

This Topic is based on true story and originates from a number of circumstances that served the birth of what we call devops today.

In June 2009, at the O’Reilly Velocity conference, John Allspaw and Paul Hammond presented the speech “10 Deploys a Day: Dev and Ops Cooperation at Flickr.”

The presentation had a amazing effect. Allspaw and Hammond in roles play a controversial interaction between design and operation. The usual deployment scene of application deployment with all the stuff like, “This is not my code, these are your servers!”.

Only rational way forward is when application development and operation are seamless, transparent and fully integrated. Over time, this presentation has reached legendary status and is historically regarded as an important moment that brought to the IT industry the methods that we now know as DevOps.

In 2013, Matthew Skelton presented us the work of web.devopstopologies.com. This is a kind of collection of anti-patterns and best practices for building communication in teams.

I offered to grant the right to use the materials and make a report adapted to Ukrainian realities and my personal experience. Matt kindly agreed.

Speech format was made more interesting than just a set of slides and a retelling of the source: graphics and characters from Ukrainian artists, javascript animation, high-performance http server in pure assembler, Kubernetes cluster on Raspberry Pi. I hope you will enjoy it.

Denys Vasyliev

Focused on Cloud Native Solutions Architecture, Development and Operations 10+ years in Telecom industry: network engineer, technical manager, operation team and unit lead, CTO. IP transit operators, Internet Providers and Mobile Network Operators: Beeline, Kyivstar, MTS , Velcom, Mobicom, Azerfon, Azercell, Astelit 2 Startups: manager positions and system architect/software engineer role. 5 years as Co-Founder cloud b2b/b2c web application project: VoIP Roaming Solution. Today: lead software engineer in Cloud Native Media Project.

Sustainable system testing with Chaos

Chaos Engineering is methodology that experiments on a distributed system in order to build confidence that the system will work well in production. Essentially, we experiment by trying to break our system to uncover system weakness.

In this talk, Paul will cover the basics of Chaos Engineer, give some case studies of companies that currently do this in production and give an introduction to some of the open source tooling that currently exists so that you can maybe try this at your company. Paul will also show that, by following good infrastructure management practices, that you can recover and scale the system when necessary, easily!

DIY Kubernetes identity provider. The Hard Way with Dex and LDAP.

The idea is to help Kubernetes users to understand basics of authN and authZ, OIDC flow, mechanics under the hood, and to show how to build production-ready identity management and audit log of Kubernetes clusters, combining tools from both worlds – the old one (LDAP) and the brave new one (Dex, dex-k8s-authenticator).

Igor Borodin

Passionate geek with various hands-on experience in cloudy stuff. 12-factor app apprentice and fan of Martin Fowler in general, likes to quote SRE and Continuous Delivery books. Nowadays hooked on Kubernetes and its ecosystem.

On the road to 6.9k. How to succeed in technical interview.

The talk about the technical knowledge that is required for modern DevOps and SRE engineers. It’s based on more than 100 technical interviews performed last year. The questions and answers that could be useful to identify experience on each technology field. What is the “required minimum” in each stack? What books blogs and articles should be studied to become DevOps professional?

Good Service: Detect and avoid errors in the world of microservices

Nothing is worse for your service’s reputation than being unwittingly down.

The developers at FINN.no are building and operating four hundred microservices to power Norway’s largest online classified ads site. There is no dedicated operations team, yet almost every major incident is limited to a few minutes of reduced service.

After a long road filled with adjustments and various initiatives to introduce monitoring across teams and domains, we have found a solution that works for us.

Learn how FINN.no builds nuanced real-time monitoring into a fleet of several hundred services; what to measure, and how to detect and isolate errors within seconds; and how to respond when something goes wrong.

Martin Lehmann

Martin spends most of his time writing JavaScript for browsers and servers, and got involved in FINN.no’s monitoring efforts due to his passion for delivering good quality in all layers of the service — from uptime and response latency to a good and accessible user experience in the browser.

He has worked quite a bit on establishing good metrics to monitor the services by, and then monitoring them using various free, open source tools. He has also been part of FINN.no’s on-call group, so he has experienced the chosen monitoring solutions from several perspectives.