The six obstacles of moving to microservices and how to deal with them - Moisés Macero García - Codemotion Rome 2018

•Download as PPTX, PDF•

0 likes•79 views

The document summarizes the six main obstacles to moving to microservices: 1) The Book Reading Cult of only following expert advice without practical application, 2) The Never-Decoupled-Enough Story of constantly trying to decouple more without limits, 3) The Common Patterns Phobia of avoiding common patterns without clear reasons, 4) The Buzzwords Syndrome of using buzzwords without understanding, 5) The Agile Trap of overlooking important architectural tasks, and 6) The Conway's Law Hackers of rigidly mapping architecture to organization without flexibility. The document provides advice on dealing with each obstacle, such as being a critical reader, focusing on communication, and starting simply.

Technology

The Six Obstacles of Moving to
Microservices
Moisés Macero
ROME - APRIL 13/14 2018

Intro
Who am I?
•Software Developer / Architect
•From Málaga, Based in Amsterdam
•Book & Blog Author (ThePracticalDeveloper.com)
•Love traveling and hiking
…and made a lot of mistakes with Microservices

The six obstacles
•The Book Reading Cult
•The Never-Decoupled-Enough Story
•The Common Patterns Phobia
•The Buzzwords Syndrome
•The Agile Trap
•The Conway's Law Hackers

The Book Reading Cult (I)
MICROSERVICES
ADVANTAGES OF
LOOSE COUPLING
WE MUST DECOUPLE
STUFFTHE EXPERT’S BOOK

The Book Reading Cult
•How to deal with it
• READ BOOKS. Put the concepts into practice
…using your business case.
• Be a Critical Reader.
• Do Continuous Improvements. Don’t feel attached to
code.
• Keep your “against-the-book” items visible
• to solve them as soon as possible if you need them.

Invoices
Service
Emailing
Service
Users Service
The Never-Decoupled-Enough Story (II)
Contracts
Service

The Never-Decoupled-Enough Story
•How to deal with it
• Don’t make a drama of having (a few) sync calls
• Create a Microservices Map, keep it updated and
visible.
• OK-ish?
• No-Go? Why Microservices?

Freedom of choice
A typical monolith
Java
Spring MySQL
REST
Microservice 2
Scala
PostgreSQL
GraphQL
Microservice 1
Spring
Boot
MariaDB
REST
Microservice 3
Node.js
Neo4j
AMQP
Microservice 4
?

The Common Patterns Phobia
•How to deal with it
• How far do you want to go? Make it clear.
• Communicate. Why Common Guidelines?
• Anarchy vs Dictatorship? Better do Democracy.
• Write down the decisions
• And their reasons and their constraints.
• Revisiting the guidelines should be possible
• In a constructive way, with a plan

The Buzzwords Syndrome (IV)
•Microservices
•Event-Driven Architecture
•Reactive Programming
•Serverless (lambda architecture)
•Blockchain
•Internet of Things
•DevOps
•Big Data

The Buzzwords Syndrome
•How to deal with it
• Don’t use buzzwords if you’re not sufficiently informed
• Use Critical Thinking
• There should always be a reason

The Agile Trap (V)
•Service Discovery
•Load Balancing
•Gateway pattern
•Centralized Logging
•End-to-End tests
•Containerization
•Continuous Integration
•…

The Agile Trap
•How to deal with it
• Keep it simple, but serious: don’t overlook important
tasks
• Prepare a list with all the ‘architectural stories’, make it
visible.
• Use “Business Language”

The Conway’s Law Hackers (VI)
“[...] the interface structure of a software system necessarily will show a congruence
with the social structure of the organization that produced it.”
Software
Thing 1
Software
Thing 2

The Conway’s Law Hackers
Microservice
1
Microservice
2
Microservice
3
YOU’RE A GENIUS

The Conway’s Law Hackers
•How to deal with it
• If you apply “Reverse Conway”, be flexible.
• You’ll need changes in your Architecture
• Fight against budgeting pieces
• Focus on Communication.
• Human, but also Interfaces, Integration, Deployment
• Start with a single, small team. Yes, SMALL is better.

Wrapping up
•Microservices are not the solution to all your
problems.
•The perfect Software doesn’t exist.
•Keep it simple (≠ fast).
•Try. Try again. Keep trying. Learn from it.
•Learn from books, but also from doers.
•Start small.
•Don’t be afraid of starting with a Monolith.

Questions?
?
tpd.io/book
@moises_mac
ero
github.com/mech
ero

Similar to The six obstacles of moving to microservices and how to deal with them - Moisés Macero García - Codemotion Rome 2018

Cloud Native Future

Julie Coonce

This presentation is conducted on 14th Sept in Limerick DotNet User Group. (https://www.meetup.com/preview/Limerick-DotNet/events/xskpdnywmbsb) SlideShare Url: https://www.slideshare.net/lalitkale/introduction-to-microservices-80583928 In this presentation, new architectural style - Microservices and it's emergence is discussed. We will also briefly touch base on what are not microservices, Conway's law and organization design, Principles of microservices and service discovery mechanism and why it is necessary for microservices implementation. About Speaker: Lalit is a senior developer, software architect and consultant with more than 12 yrsof .NET experience. He loves to work with C# .NET and Azure platform services like App Services, Virtual Machines, Cortana, and Container Services. He is also the author of 'Building Microservices with .NET Core' (https://www.packtpub.com/web-development/building-microservices-net-core) book. To know more and connect with Lalit, you can visit his LinkedIn profile below. https://www.linkedin.com/in/lalitkale/ This presentation will be useful for software architects/Managers, senior developers. Do share your feedback in comments.

Introduction To Microservices

Lalit Kale

Service as-a-software

Jean-Jacques Dubray

A microservice is written quickly: Reasonable scope, a small REST interface, nice and easy and way lot cooler than those fat web applications we did before. But, is it really that easy? Well - no, not really! A single service is quite easy to manage, but therefrom the overall complexity does not go away. Instead of a few big web applications we now have lots of microservices - and to make sure that integration, operations and maintenance will not become a lottery game with increased heart-attack risk, it is crucial to consider a few things, that were not (so) important for traditional web applications. Should I use REST or would event driven be the better choice? How can I make sure the service collaboration works as desired? With GUI or better without GUI? How can I guarantee availability and scalability in production? How to deploy best? How I can I make sure that services are easily replaceable? How can I avoid service spaghetti? Those and many more questions will be answered in this session - to make sure the encounter with microservices will not become a health risk.

Microservices - stress-free and without increased heart-attack risk - Uwe Fri...

distributed matters

Serverless Architectures enable scalable and cost-effective apps to be built faster, so they can dramatically increase the odds of Your Startup's Success! In "Startups + Serverless = Match made in Heaven" meetup, www.ServerlessToronto.org members discussed how to help Entrepreneurs push their businesses up to "other side of the teeterboard" (without failing) using the Serverless technologies: https://www.youtube.com/watch?v=1SqfJo47kMA

Serverless Toronto helps Startups

Daniel Zivkovic

Moving from a monolithic based architecture to a more microservices architecture can be fraught with challenges. We'll talk about some of these challenges and some common myths associated with trying to strangle the Monolith. We'll also talk about config management and automation's critical role in helping you move to a microservices architecture, and how our monolithic approach to automation changes in the new world.

Monoliths, Myths, and Microservices - CfgMgmtCamp

Michael Ducy

This presentation explores the Microservices architecture style. Although there is no precise definition of this architectural style (some argue Microservices is not an architectural style, just another term for SOA architectures), there is increasing agreement this approach is useful in implementing highly scalable, robust and configurable software systems. We’ll attempt to clarify the topic from a purely architectural point of view dispelling some myths in the process.

Are Microservices our future?

Angelo Simone Scotto

MLOps for living: Infrastructure-as-Code on AWS

AntonChernov9

This is a slide deck belonging to a talk in which I talk about the challenges with µservices in general and provide a few ideas how to avoid the worst pitfalls. The talk starts with a short explanation why µservice are always hard (yes, the title of the presentation is sort of an oxymoron) and when and when not to choose µservices. After that introduction I provide a few ideas which from my experience help to get around the worst problems and pitfalls with µservices. As the ideas are from very different topic areas I organized them according to the software production chain starting with design hints and ending with resilience hints (a pure production related topic). As always the voice track is missing but I hope that also the slides in themselves will give you a few helpful hints.

Microservices - stress-free and without increased heart attack risk

Uwe Friedrichsen

Introduction to Microservices

Amazon Web Services

Microservices: Yes or not?

Eduard Tomàs

Mehr als eine Dekade wurden Anwendungen in drei Schichten gebaut. Doch zunehmende Digitalisierung und Vernetzung führen zu einer Komplexität, derer man mit dieser Architektur nicht mehr Herr wird. Daher gibt es viele neue Paradigmen und Trends wie z.B. Microservices, Cloud, Serverless, Event Driven Architecture oder Domain Driven Design. Was ist da dran und wie wirkt sich das alles auf BPM aus? Dieser spannenden Frage wird Camunda-Mitgründer Bernd Rücker nachgehen. Dabei wird er den Bogen von methodischen Aspekten rund um Prozessmodellierung und Ownership bis hin zu technischen Architekturen und Herausforderungen spannen.

Neue zeiten verlangen nach neuen Paradigmen - Bernd Rücker

camunda services GmbH

Grokking microservices in 5 minutes

Andrew Siemer

Accelerate Delivery: Business case for Agile DevOps, CI/CD and Microservices

Rick Hightower

Things You Need to Know Before Starting An App-Openair2015 keynote

Sana Nasar

Let's talk about... Microservices

Alessandro Giorgetti

Advanced Microservices - Greach 2015

Steve Pember

Microservices vs monolithics betabeers

Jesús Mª Villar Vazquez

The way we build systems is changing. From our history of monolithic systems, then distributed systems, to Internet connected systems, we are now entering the era of cloud-hosted, microservice based, pay-for-usage system development. What does the history of software architecture tell us about the challenges of this new environment? And how does our approach to software architecture need to evolve in order to meet them? Software architecture has been a mainstream discipline since the 1990s and in that time has become a recognised, widely researched and often valued part of the software engineering process. However architecture approaches must reflect the technologies and priorities of the systems we are building and in this regard its future has never looked more uncertain or more exciting. From our history of monolithic compile time architecture, to many tiered distributed systems, to Internet connected services, we are now entering the era of cloud-hosted, microservice-based, pay-for-usage systems development. In this new world the boundaries of “my” system are no longer so clear and our systems are dissolving into complex webs of independently owned and evolved services, with nothing more in common than a shared credit card for billing and an agreement on the format of network requests. What can the history of software architecture tell us about the likely challenges in this environment? And how must it develop in order to meet them? This version of the talk was presented at GOTO London in October 2016.

Software Architecture as Systems Dissolve

Eoin Woods

Liferay as a Microservice Platform

Daniel Reuther

Similar to The six obstacles of moving to microservices and how to deal with them - Moisés Macero García - Codemotion Rome 2018 (20)

Cloud Native Future

Introduction To Microservices

Service as-a-software

Microservices - stress-free and without increased heart-attack risk - Uwe Fri...

Serverless Toronto helps Startups

Monoliths, Myths, and Microservices - CfgMgmtCamp

Are Microservices our future?

MLOps for living: Infrastructure-as-Code on AWS

Microservices - stress-free and without increased heart attack risk

Introduction to Microservices

Microservices: Yes or not?

Neue zeiten verlangen nach neuen Paradigmen - Bernd Rücker

Grokking microservices in 5 minutes

Accelerate Delivery: Business case for Agile DevOps, CI/CD and Microservices

Things You Need to Know Before Starting An App-Openair2015 keynote

Let's talk about... Microservices

Advanced Microservices - Greach 2015

Microservices vs monolithics betabeers

Software Architecture as Systems Dissolve

Liferay as a Microservice Platform

More from Codemotion

Fuzz-testing: A hacker's approach to making your code more secure | Pascal Ze...

Codemotion

Pompili - From hero to_zero: The FatalNoise neverending story

Codemotion

Pastore - Commodore 65 - La storia

Codemotion

Rivivere l'ebbrezza di progettare un vecchio computer o una consolle da bar è oggi possibile sfruttando le FPGA, ovvero logiche programmabili che consentono a chiunque di progettare il proprio hardware o di ricrearne uno del passato. In questa sessione si racconta come dal reverse engineering dell'hardware di vecchie glorie come il Commodore 64 e lo ZX Spectrum sia stato possibile farle rivivere attraverso tecnologie oggi alla portata di tutti.

Pennisi - Essere Richard Altwasser

Codemotion

There's a lot of talk about blockchain, but how does the technology behind it actually work? For developers, getting some hands-on experience is the fastest way to get familiair with new technologies. So let's build a blockchain, then! In this session, we're going to build one in plain old Java, and have it working in 40 minutes. We'll cover key concepts of a blockchain: transactions, blocks, mining, proof-of-work, and reaching consensus in the blockchain network. After this session, you'll have a better understanding of core aspects of blockchain technology.

Michel Schudel - Let's build a blockchain... in 40 minutes! - Codemotion Amst...

Codemotion

When was the last time you were truly lost? Thanks to the maps and location technology in our phones, a whole generation has now grown up in a world where getting lost is truly a thing of the past. Location technology goes far beyond maps in the palm of our hand, however. In this talk, we will explore how a ridesharing app works. How do we discover our destination?How do we find the closest driver? How do we display this information on a map? How do we find the best route?To answer these questions,we will be learning about a variety of location APIs, including Maps, Positioning, Geocoding etc.

Richard Süselbeck - Building your own ride share app - Codemotion Amsterdam 2019

Codemotion

Eward Driehuis, SecureLink's research chief, will guide you through the bumpy ride we call the cyber threat landscape. As the industry has over a decade of experience of dealing with increasingly sophisticated attacks, you might be surprised to hear more attacks slip through the cracks than ever. From analyzing 20.000 of them in 2018, backed by a quarter of a million security events and over ten trillion data points, Eward will outline why this happens, how attacks are changing, and why it doesn't matter how neatly or securely you code.

Eward Driehuis - What we learned from 20.000 attacks - Codemotion Amsterdam 2019

Codemotion

IoT revolution is ended. Thanks to hardware improvement, building an intelligent ecosystem is easier than never before for both startups and large-scale enterprises. The real challenge is now to connect, process, store and analyze data: in the cloud, but also, at the edge. We’ll give a quick look on frameworks that aggregate dispersed devices data into a single global optimized system allowing to improve operational efficiency, to predict maintenance, to track asset in real-time, to secure cloud-connected devices and much more.

Francesco Baldassarri - Deliver Data at Scale - Codemotion Amsterdam 2019 -

Codemotion

What if Virtual Reality glasses could transform your environment into a three-dimensional work of art in realtime in the style of a painting from Van Gogh? One of the many interesting developments in the field of Deep Learning is the so called "Style Transfer". It describes a possibility to create a patchwork (or pastiche) from two images. While one of these images defines the the artistic style of the result picture, the other one is used for extracting the image content. A team from TNG Technology Consulting managed to build an AI showcase using OpenCV and Tensorflow to realize such goggles.

Martin Förtsch, Thomas Endres - Stereoscopic Style Transfer AI - Codemotion A...

Codemotion

Blockchain (and Cryptocurrency) is an evolution of 20-year old research from scientists like Chaum, Lamport, and Castro & Liskov. Due to the current hype, it's hard to distinguish beneficial aspects of the technology from a desire for a "silver bullet" for device security, verifiable logistics, or "saving democracy". The problem: blockchain introduces new security challenges - and blind adoption without understanding reduces overall security. In this talk, Melanie Rieback and Klaus Kursawe explain the pitfalls and limits of blockchain, so you can avoid making your applications LESS secure.

Melanie Rieback, Klaus Kursawe - Blockchain Security: Melting the "Silver Bul...

Codemotion

Networking is a core part of computing in the digital world we inhabit. But, how well do you know how it works? Do you understand all the moving parts of the OSI stack inside your computer, and how the network is actually put together? How can this ever work? This guided safari of layers, standards, protocols, and happenstance will bring us close to the copper wire, and up through the layers of CDMA/CD, ARP, routing and HTTP. We will make a few excursions through patchworks that still work forty years later, and cleverly designed mechanisms that show that simplicity is the only way to last.

Angelo van der Sijpt - How well do you know your network stack? - Codemotion ...

Codemotion

Performance tests are not only an important instrument for understanding a system and its runtime environment. It is also essential in order to check stability and scalability – non-functional requirements that might be decisive for success. But won't my cloud hosting service scale for me as long as I can afford it? Yes, but… It only operates and scales resources. It won't automatically make your system fast, stable and scalable. This talk shows how such and comparable questions can be clarified with performance tests and how DevOps teams benefit from regular test practise.

Lars Wolff - Performance Testing for DevOps in the Cloud - Codemotion Amsterd...

Codemotion

Sascha will demonstrate the opportunities and challenges of Conversational AI learned from the practice. Both Technology and User Experience will be covered introducing a process finding micro-moments, writing happy paths, gathering intents, designing the conversational flow, and finally publishing on almost all channels including Voice Services and Chatbots. Valuable for enterprises, developers, and designers. All live on stage in just minutes and with almost no code.

Sascha Wolter - Conversational AI Demystified - Codemotion Amsterdam 2019

Codemotion

A key challenge we face at Pacmed is quickly calibrating and deploying our tools for clinical decision support in different hospitals, where data formats may vary greatly. Using Intensive Care Units as a case study, I’ll delve into our scalable Python pipeline, which leverages Pandas’ split-apply-combine approach to perform complex feature engineering and automatic quality checks on large time-varying data, e.g. vital signs. I’ll show how we use the resulting flexible and interpretable dataframes to quickly (re)train our models to predict mortality, discharge, and medical complications.

Michele Tonutti - Scaling is caring - Codemotion Amsterdam 2019

Codemotion

Coolblue is a proud Dutch company, with a large internal development department; one that truly takes CI/CD to heart. Empowerment through automation is at the heart of these development teams, and with more than 1000 deployments a day, we think it's working out quite well. In this session, Pat Hermens (a Development Managers) will step you through what enables us to move so quickly, which tools we use, and most importantly, the mindset that is required to enable development teams to deliver at such a rapid pace.

Pat Hermens - From 100 to 1,000+ deployments a day - Codemotion Amsterdam 2019

Codemotion

Quantum computers can use all of the possible pathways generated by quantum decisions to solve problems that will forever remain intractable to classical compute power. As the mega players vie for quantum supremacy and Rigetti announces its $1M "quantum advantage" prize, we live in exciting times. IBM-Q and Microsoft Q# are two ways you can learn to program quantum computers so that you're ready when the quantum revolution comes. I'll demonstrate some quantum solutions to problems that will forever be out of reach of classical, including organic chemistry and large number factorisation.

James Birnie - Using Many Worlds of Compute Power with Quantum - Codemotion A...

Codemotion

Chinese food exploded across America in the early 20th century, rapidly adapting to local tastes while also spreading like wildfire. How was it able to spread so fast? The GY6 is a family of scooter engines that has achieved near total ubiquity in Europe. It is reliable and cheap to manufacture, and it's made in factories across China. How are these factories able to remain afloat? Chinese-American food and the GY6 are both riveting studies in product-market fit, and both are the product of a distributed open source-like development model. What lessons can we learn for open source software?

Don Goodman-Wilson - Chinese food, motor scooters, and open source developmen...

Codemotion

Pieter Omvlee - The story behind Sketch - Codemotion Amsterdam 2019

Codemotion

Would you fly in a plane designed by a craftsman or would you prefer your aircraft to be designed by engineers? We are learning that science and empiricism works in software development, maybe now is the time to redefine what “Software Engineering” really means. Software isn't bridge-building, it is not car or aircraft development either, but then neither is Chemical Engineering. Engineering is different in different disciplines. Maybe it is time for us to begin thinking about retrieving the term "Software Engineering" maybe it is time to define what our "Engineering" discipline should be.

Dave Farley - Taking Back “Software Engineering” - Codemotion Amsterdam 2019

Codemotion

What is the job of a CTO and how does it change as a startup grows in size and scale? As a CTO, where should you spend your focus? As an engineer aspiring to be a CTO, what skills should you pursue? In this inspiring and personal talk, I describe my journey from early Red Hat engineer to CTO at Bloomon. I will share my view on what it means to be a CTO, and ultimately answer the question: Should the CTO be coding?

Joshua Hoffman - Should the CTO be Coding? - Codemotion Amsterdam 2019

Codemotion

More from Codemotion (20)