MicroManchester 2016 "A Brief Guide to Microservices"

•

0 j'aime•406 vues

Setting the scene at #micromanchester by providing a brief guide and core principles of microservices http://www.microservicesmanchester.com/

Technologie

Welcome to...
04/07/2016 @danielbryantuk

Welcome! Brief Logistics Interlude
• Fire escapes
• Code of Conduct (http://confcodeofconduct.com/)
• The conference itself
– Two tracks of awesomeness
– Tea & coffee and Lunch provided
– Drinks in the evening
• Get involved on social media!
– Official Hashtag #micromanchester
04/07/2016 @danielbryantuk

• Pragmatic high-end software consultancy
• Founded in 2009, Owned by Jonas Partner and Trifork
• 40 permanent staff - all Hands-on experts
• A client base of enterprise size customers, that include:
– HMRC, British Airways, The Post Office, British Gas, notonthehighstreet.com, TNT, Atos...
• Technology-based solutions that are production ready,
– often aimed at enhancing legacy systems
– Proof-of-concept
• Digital and Devops transformations
• Win a Sonos Play:1 with the most creative tweet involving an OpenCredo Owl (#ocowl)
04/07/2016 @danielbryantuk

Billy Jenkins and Rory Brandon
www.oliverbernard.co.uk
• Staffing and Recruitment Agency - HQ in London with Manchester office in Fountain Street
• Specialising in Software Development and Testing, Agile Project Delivery and
DevOps/Infrastructure
• Work with the BBC, Barclays, HMRC, Equal Experts in Manchester
• Involved in hosting, organising and sometimes speaking at Tech Events throughout the UK
• Here to give some market intelligence and advice around current trends and conditions,
salary/rate info as well as tips and ideas on hiring and staff retention
• Free iPad giveaway

Welcome to the world of Microservices
Daniel Bryant
Chief Scientist @Opencredo
@danielbryantuk

So, What are microservices?
“Loosely coupled service oriented architecture
with bounded contexts”
Adrian Cockcroft
“Applications that fit in your head”
James Lewis
04/07/2016 @danielbryantuk

So, What are microservices?
• Architectural style - build services around biz capability
• Enable evolutionary architecture and scaling (teams and Tech)
• single App composed of (interchangable) multiple services
• Services Running as individual processes, individually deployable
• lightweight external communication (e.g. rest over http)
• Potentially polyglot Language and Data stores
• Minimum centralised management
04/07/2016 @danielbryantuk

Monolith vs microservices
04/07/2016 @danielbryantuk
martinfowler.com/articles/microservices.html

So, this appears familiar (Corba, SOA, etc)
Oh, Yes...
but this time it's Different...
Hopefully...
04/07/2016 @danielbryantuk

The Perfect Storm?
• Collaborative processes
– increasing requirements for speed from the business
– Agile, lean and Devops
• Programmable infrastructure
– Driven out from Deployment at scale (google, netflix, amazon)
– Config management, Cloud and containers
• Open source
– Sharing of technology and knowledge
– Download, consume and contribute
04/07/2016 @danielbryantuk

So, Implementing Microservices sound easy...
04/07/2016 @danielbryantuk

Implementing Microservices is easy
Implementing Microservice systems is complex
(so too are the associated organisational/people systems)
04/07/2016 @danielbryantuk

Some thinking points for today
04/07/2016 @danielbryantuk
Ronnie Mitra @ #api360 www.infoq.com/news/2016/06/api360-microservices-summit

Enjoy today!
Talk to everyone - share Your knowledge!
04/07/2016 @danielbryantuk

Contenu connexe

Tendances

(Updated for Sept 2016, and Java-themed as this talk was presented as part of the 'Virtual JUG' vJUG24 event on 27th Sept) There is trouble brewing in the land of microservices – today’s shiny technology is tomorrow’s legacy, and there is concern that we will all be dealing with spaghetti services in 2018… It is often a sign of an architectural approach’s maturity that, in addition to the emergence of well-established principles and practices, anti-patterns also begin to be identified and classified. In this talk we introduce the 2016 edition of the seven deadly sins that if left unchecked could easily ruin your next microservices project… This talk will feature as a session in vJUG24, the first 24 hour virtual Java Conference in the World. More information is available at http://virtualjug.com/vJUG24/

vJUG24 2016 "Seven (More) Deadly Sins of Microservice"

Daniel Bryant

Everyone is talking about building “cloud native” Java applications—and taking advantage of microservice architecture, containers, and orchestration/PaaS platforms—but there is surprisingly little discussion of migrating existing legacy (moneymaking) applications. This session aims to address this, and, using lessons learned from several real-world examples, it covers topics such when to rewrite applications (if at all), modeling/extracting business domains, applying the “application strangler” pattern, common misconceptions with “12-factor” application design, and the benefits/drawbacks of container technology.

JavaOne 2016 "Java, Microservices, Cloud and Containers"

Daniel Bryant

The 'microservices' architectural style has taken the software development industry by storm over the past two years. Several people are arguing that this is simply classical SOA being rebranded, while others are suggesting that creating loosely-coupled composable services is simply architectural best-practice. Join Daniel for a brief introduction to the topic of microservices, and also a tour of the nastiest sins (anti-patterns) he has seen in his journey as a consultant. Topics covered include: * Pride - selfishly ignoring the new requirements for testing * Envy - introducing inappropriate intimacy within services by creating a shared domain model * Wrath - failing to deal with the inevitable bad things that occur within a distributed system * Sloth - composing services in a lazy fashion, which ultimately leads to the creation of a Distributed Monolith * Lust - embracing the latest and greatest technology without evaluating the operational impact incurred by these choices Presented at the BCS Software Practice Advancement SPA-298 event on 6/4/2016

BCS 2016 "Intro to Microservices (and the Seven Deadly Sins)"

Daniel Bryant

When I ask fellow developers what they think about empathy, the answer is often “not much”. However, I believe that the skill of empathy, being able to place yourself in another’s position, is crucial to designing, building and operating software at any scale. Join me for a whistle stop tour of the benefits of empathy, which I have learned from working on a wide variety of software projects over the previous ten years. I will share stories of success and failure, and suggest practical techniques that you can harness in order to help your team develop empathy. When gathering requirements and performing business analysis, it is obvious that the ability to experience from within another user/customer/being's frame of reference is a valuable skill, but the same can be said when writing code. If we follow Martin Fowler’s train of thought where “any fool can write code that a computer can understand. Good programmers write code that humans can understand” we can see that empathy is at the heart of this skill. We could also argue that the rise of “DevOps” is simply both sides of the traditional divide trying to understand each other better. Developing the skill of empathy isn’t necessarily easy, but in this talk I will share my learnings, techniques and tricks for developing more effective software.

The London Web "Empathy - The Hidden Ingredient of Good Software Development"

Daniel Bryant

ZTLive 2016 "Introduction to Microservices"

Daniel Bryant

The technology changes required when implementing a microservice-based application are only one part of the equation. The business and organisation will also most likely have to fundamentally change. In an ideal world, this shouldn’t be a problem - what with the rise of agile, lean and DevOps - but this is not always the situation Daniel encounters in his consulting travels. He would like to share with you some stories of successful (and not so successful) strategies and tactics he has used over the past four years when introducing service-oriented architecture into organisations. Join Daniel for a whistle-stop tour of the business and people challenges that he has experienced first hand when implementing a greenfield microservice project, and also breaking down a monolith. You will discover ‘divided companies’ vs ‘connected companies’, determine the actual impact of conway's law, briefly touch on the lean startup/enterprise mindset, dive into change management without the management double-speak, and look at the lightweight processes needed to ensure the technical success of a microservices implementation.

muCon 2015 "The Business Behind Microservices: Organisational, Architectural,...

Daniel Bryant

TTN 2015 "Defining DevOps: Concepts, Technology and Automation. Oh yeah, and ...

Daniel Bryant

In the international bestseller Thinking, Fast and Slow, Daniel Kahneman explains how we, as human beings, think and reason and, perhaps surprisingly, how our thought processes are often fundamentally flawed and biased. This session explores the ideas presented in the book in the context of professional software development. Along this journey, the presentation also shares techniques, processes, and models that can help overcome some of the identified limitations of our decision-making abilities. Topics discussed include the “availability heuristic,” which can lead developers to choose the “latest and greatest” technology without proper evaluation; “optimistic bias,” which can blind architects so they can’t see the “unknown unknowns” within a project; and more.

J1 2015 "Thinking Fast and Slow with Software Development"

Daniel Bryant

The technology changes required when implementing a microservice-based application are only one part of the equation. The business and organisation will also most likely have to fundamentally change. In an ideal world, this shouldn’t be a problem - what with the rise of agile, lean and DevOps - but this is not always the situation I encounter in my consulting travels. I would like to share some stories of successful (and not so successful) strategies and tactics I have used over the past four years when introducing service-oriented architecture into organisations. Join me for a whistle-stop tour of the business and people challenges that I have experienced first hand when implementing a greenfield microservice project, and also breaking down a monolith. We’ll look at ‘divided companies’ vs ‘connected companies’, determine the actual impact of conway's law, briefly touch on the lean startup/enterprise mindset, dive into change management without the management double-speak, and look at the lightweight processes needed to ensure the technical success of a microservices implementation.

LMSUG 2015 "The Business Behind Microservices: Organisational, Architectural ...

Daniel Bryant

The technology changes required when implementing a microservice-based application are only one part of the equation. The business and organisation will also most likely have to fundamentally change. In an ideal world, this shouldn’t be a problem – what with the rise of agile, lean and DevOps – but this is not always the situation Daniel encounters in his consulting travels. He would like to share with you some stories of successful (and not so successful) strategies and tactics he has used over the past four years when introducing service-oriented architecture into organisations. Join Daniel for a whistle-stop tour of the business and technical people challenges that he has experienced first hand when implementing a greenfield microservice project, and also breaking down a monolith. You will discover ‘divided companies’ vs ‘connected companies’, determine the actual impact of Conway’s Law on architecture and operations, briefly touch on the lean startup/enterprise mindset, dive into change management without the management double-speak, and look at the lightweight processes needed to ensure the technical success of a microservices implementation.

MicroManchester 2016 "Microservices from 30000ft: Organisation, Architecture ...

Daniel Bryant

Presented at OOP2016 with Erich Eichinger The technology changes required when implementing a microservice-based application are only one part of the equation – the business and organisation will often have to fundamentally change. In an ideal world, this shouldn’t be a problem, what with the rise of agile, lean and DevOps, but in reality this is not always the situation. In this talk we will share some stories of successful (and not so successful) strategies and tactics that we have used when introducing microservices into a variety of organisations over the past four years. Join us for a whistle-stop tour of the business and people challenges that we have experienced first hand when implementing greenfield microservice projects and also breaking down monoliths. We’ll look at ‘divided companies’ vs ‘connected companies’, determine the actual impact of conway's law, briefly touch on the lean startup/enterprise mindset, dive into change management without the management double-speak, and look at the lightweight processes needed to ensure the technical success of a microservices implementation (e.g. DevOps, CD). The main lessons we're keen to share are from observations on a couple of microservice transformation projects we have been involved in - some where teams have been cross-functional and aligned around strategic objectives, and some where they haven't. The latter proved much more challenging, as we saw single domain models being created and shared around the codebase, unclear service/context boundaries, and ultimately people tripping over each other.

OOP2016 "The Business Behind Microservices: Organisational, Architectural and...

Daniel Bryant

The technology changes required when implementing a microservice-based application are only one part of the equation. The business and organisation will also most likely have to fundamentally change. In an ideal world, this shouldn’t be a problem – what with the rise of agile, lean and DevOps – but this is not always the situation I encounter in my consulting travels. I would like to share some stories of successful (and not so successful) strategies and tactics I have used over the past four years when introducing service-oriented architecture into organisations. Join me for a whistle-stop tour of the business and people challenges that I have experienced first hand when implementing a greenfield microservice project, and also breaking down a monolith. We’ll look at ‘divided companies’ vs ‘connected companies’, determine the actual impact of conway’s law, briefly touch on the lean startup/enterprise mindset, dive into change management without the management double-speak, and look at the lightweight processes needed to ensure the technical success of a microservices implementation.

OC 2015: The Business Behind Microservices

Daniel Bryant

All is not completely rosy in microservice-land. It is often a sign of an architectural approach’s maturity that in addition to the emergence of well-established principles and practices, that anti-patterns also begin to be identified and classified. In this talk we introduce seven deadly sins that if left unchecked could easily ruin your next microservices project... This talk will take a tour of some of the nastiest anti-patterns in microservices, giving you the tools to not only avoid but also slay these demons before they tie up your project in their own special brand of hell. Topics covered include: Pride - selfishly ignoring the new requirements for testing; Envy - introducing inappropriate intimacy within services by creating a shared domain model; Wrath - failing to deal with the inevitable bad things that occur within a distributed system; Sloth - composing services in a lazy fashion, which ultimately leads to the creation of a “Distributed Monolith”; and Lust - embracing the latest and greatest technology without evaluating the operational impact incurred by these choices.

DLJCJUG 2015: The Seven Deadly Sins of Microservices

Daniel Bryant

Is continuous delivery mainstream? We would all like to think so, but as William Gibson reminds us, “The future is already here—it’s just not evenly distributed.” The large (unicorn) companies have been talking about deploying containerized applications for some time, but the processes, techniques, and technologies involved are not always clear when looking in from the outside. This can make it difficult to emulate their success. Based on his experience building several Docker-based applications that were deployed to a range of orchestration and scheduling platforms, Daniel Bryant demonstrates how to create a scalable build pipeline that takes a series of Java applications, containerizes them, and deploys them to Docker Swarm. Example code will be available to download via GitHub, and the examples can be executed locally via Vagrant.

OReilly SACON 2016 "A Practical Guide for Continuous Delivery with Containers"

Daniel Bryant

In this presentation Nic and Daniel will take you through notonthehighstreet.com's journey, the pain, the joy, and the road to the ultimate success of running a hundred million pound ecommerce business on Docker, Mesos and the AWS cloud. Their mission was to break down a monolith, to chip away at it, and constantly deliver business value, all the while without needing a migration big bang that was bigger than the one that created the universe. Whilst extending and rebuilding the company's core platforms using a microservice pattern would deliver their need for change, it also introduced complexity around deployment and development - hence their need for Docker. They truly believe that without containers they would have failed in their mission, and in fact, adopting Docker has given them so much more than the ability to change. It has given them the ability to scale, to geolocate, to develop in a way they never thought possible, and above all it has given them the ability to transform our business. They went “All In”, every single line of code for our front and back end systems is running in a container and Nic would love to share the story of how they did it. Presented with Nic Jackson at ContainerSched 2015

ContainerSched 2015 "Our journey to world (gifting) domination - how notonthe...

Daniel Bryant

It is often a sign of an architectural approach’s maturity that in addition to the emergence of well established principles and practices, that anti-patterns also begin to be identified and classified. In this talk Daniel will introduce the 2016 edition of the seven deadly sins that if left unchecked could easily ruin your next microservices project... This talk will take a tour of some of the nastiest anti-patterns in microservices, giving you the tools to not only avoid but also slay these demons before they tie up your project in their own special brand of hell. Topics covered include: Envy - introducing inappropriate intimacy within services by creating a shared domain model, and how many teams deploy and use data stores incorrectly; Wrath - failing to deal with the inevitable bad things that occur within a distributed system; Sloth - ignoring the importance of NFRs; and Lust - embracing the latest and greatest technology without evaluating the impact incurred by these choices.

OOP/MM 2017: "Seven (More) Deadly Sins of Microservices"

Daniel Bryant

We all hear the term "DevOps" being thrown around on a daily basis, but what does it actually mean? With a little help from everyone's favourite 80's action hero, we'll undergo a whistle-stop tour of the philosophy, culture and tooling behind this buzzword, specifically aimed at Java Developers. We'll also look at a real-world case study from Instant Access Technologies Ltd, and explore the key role that DevOps has played during a successful upgrade of the epoints customer loyalty platform to support increasing traffic. The core discussion will focus on the challenges encountered as we moved from a monolithic app deployed into a data centre on a 'big bang' schedule, to a platform of loosely-coupled components, all being continuously deployed into the Cloud.

LJCConf 2013 "Chuck Norris Doesn't Need DevOps"

Daniel Bryant

We all hear the term "DevOps" being thrown around on a daily basis, but what does it actually mean? With a little help from everyone's favourite 80's action hero, we'll undergo a whistle-stop tour of the philosophy, culture and tooling behind this buzzword, specifically aimed at Java developers. We'll also look at a real-world case study from Instant Access Technologies Ltd, and explore the key role that DevOps has played during a successful upgrade of the epoints customer loyalty platform to support increasing traffic. The core discussion will focus on the challenges encountered as we moved from a JVM-based monolithic app deployed into a data centre on a 'big bang' schedule, to a platform of loosely-coupled components, all being continuously deployed into the Cloud. We will conclude the talk by recommending a learning path for Java developers who are interested to learn more about DevOps.

LJC: "Chuck Norris Doesn't Do DevOps...but Java developers might benefit"

Daniel Bryant

In the international bestseller ‘Thinking, Fast and Slow’, Daniel Kahneman explains how we as human beings think and reason, and perhaps surprisingly how our thought processes are often fundamentally flawed and biased. This talk explores the ideas presented in the book in the context of professional software development. As software developers we all like to think that we are highly logical, and make only rational choices, but after reading the book I’m not so sure. Here I’ll share my thinking on thinking, and provide guidance, processes and models to help overcome some of the identified limitations of our decision-making abilities. Topics that will be discussed include; the ‘Availability Heuristic’, which can lead developers to choose the ‘latest and greatest’ technology without proper evaluation; ‘Optimistic Bias’, which can blind architects from the ‘unknown unknowns’ within a project; and more!

JAXLondon 2015 "Thinking Fast and Slow with Software Development"

Daniel Bryant

Tendances (19)

vJUG24 2016 "Seven (More) Deadly Sins of Microservice"

JavaOne 2016 "Java, Microservices, Cloud and Containers"

BCS 2016 "Intro to Microservices (and the Seven Deadly Sins)"

The London Web "Empathy - The Hidden Ingredient of Good Software Development"

ZTLive 2016 "Introduction to Microservices"

muCon 2015 "The Business Behind Microservices: Organisational, Architectural,...

TTN 2015 "Defining DevOps: Concepts, Technology and Automation. Oh yeah, and ...

J1 2015 "Thinking Fast and Slow with Software Development"

LMSUG 2015 "The Business Behind Microservices: Organisational, Architectural ...

MicroManchester 2016 "Microservices from 30000ft: Organisation, Architecture ...

OOP2016 "The Business Behind Microservices: Organisational, Architectural and...

OC 2015: The Business Behind Microservices

DLJCJUG 2015: The Seven Deadly Sins of Microservices

OReilly SACON 2016 "A Practical Guide for Continuous Delivery with Containers"

ContainerSched 2015 "Our journey to world (gifting) domination - how notonthe...

OOP/MM 2017: "Seven (More) Deadly Sins of Microservices"

LJCConf 2013 "Chuck Norris Doesn't Need DevOps"

LJC: "Chuck Norris Doesn't Do DevOps...but Java developers might benefit"

JAXLondon 2015 "Thinking Fast and Slow with Software Development"

En vedette

CraftConf [Preview] "Empathy - The Hidden Ingredient of Good Software Develop...

Daniel Bryant

All is not completely rosy in microservice-land. It’s often a sign of an architectural approach’s maturity that anti-patterns begin to be identified and classified alongside well-established principles and practices. Daniel Bryant introduces seven deadly sins from real projects, which left unchecked could easily ruin your next microservices project. Daniel offers an updated tour for 2016 of some of the nastiest anti-patterns in microservices from several real-world projects he’s encountered as a consultant, providing a series of anti-pattern “smells” you can sniff out and exploring the tools and techniques you need to avoid or mitigate the potential damage. Topics include: Pride: Selfishly building the wrong thing, such as the "Inter-Domain-Enterprise-Application-Service-Bus” or a fully bespoke infrastructure platform Envy: Introducing inappropriate intimacy within services by creating a shared “canonical” domain model Wrath: Failing to deal with the inevitable bad things that occur within a distributed system Sloth: Composing services in a lazy fashion, which ultimately leads to the creation of a "distributed monolith” Lust: Embracing the latest and greatest technology without evaluating the operational impact incurred by these choices

OSCON EU 2016 "Seven (More) Deadly Sins of Microservices"

Daniel Bryant

All is not completely rosy in microservice-land. It is often a sign of an architectural approach’s maturity that in addition to the emergence of well established principles and practices, that anti-patterns also begin to be identified and classified. In this talk Daniel will introduce the 2016 edition of the seven deadly sins that if left unchecked could easily ruin your next microservices project... This talk will take a tour of some of the nastiest anti-patterns in microservices, giving you the tools to not only avoid but also slay these demons before they tie up your project in their own special brand of hell. Topics covered include: Envy - introducing inappropriate intimacy within services by creating a shared domain model, and how many teams deploy and use data stores incorrectly; Wrath - failing to deal with the inevitable bad things that occur within a distributed system; Sloth - ignoring the importance of NFRs; and Lust - embracing the latest and greatest technology without evaluating the impact incurred by these choices. This is an all-new 2016 version of Daniel's popular 'deadly sins talk' that was recently presented at QCon NY. The talk received 94% highest rating, and was the fifth most attended talk at the conference. Daniel plans to continually improve the presentation based on his learnings and attendee feedback.

muCon 2016: "Seven (More) Deadly Sins of Microservices"

Daniel Bryant

Microservice platforms are finally becoming a reality: Mesos, Kubernetes, and a whole bunch of PaaS-style offerings are available, but the reality is that these platforms still don’t provide everything you need in order to build a fully functional microservice ecosystem. Come to this session to learn about the essential deployment, orchestration, and glue components that often have to be self-assembled. The presentation begins by looking at deployment techniques and tools and examines where to test (QA, staging, or production), how to test (integration and contracts), and how to separate deployment and release. It then discusses orchestration, configuration, and service discovery. Finally it looks at essential glue such as logging, monitoring, and alerting.

Haufe #msaday: "Building a Microservice Ecosystem"

Daniel Bryant

In the international bestseller 'Thinking, Fast and Slow', Daniel Kahneman explains how we as human beings think and reason, and perhaps surprisingly how our thought processes are often fundamentally flawed and biased. This talk explores the ideas presented in the book in the context of professional software development. As software developers we all like to think that we are highly logical, and make only rational choices, but after reading the book I'm not so sure. Here I'll share my thinking on thinking. Topics that will be discussed include; the 'Availability Heuristic', which can lead developers to choose the 'latest and greatest' technology without proper evaluation; 'Optimistic Bias' which can blind architects from the 'unknown unknowns' within a project; and more!

Devternity 2016 "Thinking Fast and Slow with Software Development"

Daniel Bryant

All is not completely rosy in microservice-land. It is often a sign of an architectural approach’s maturity that in addition to the emergence of well established principles and practices, that anti-patterns also begin to be identified and classified. In this talk Daniel will introduce the 2016 edition of the seven deadly sins that if left unchecked could easily ruin your next microservices project... This talk will take a tour of some of the nastiest anti-patterns in microservices, giving you the tools to not only avoid but also slay these demons before they tie up your project in their own special brand of hell. Topics covered include: • Envy - introducing inappropriate intimacy within services by creating a shared domain model, and how many teams deploy and use data stores incorrectly; • Wrath - failing to deal with the inevitable bad things that occur within a distributed system; • Sloth - ignoring the importance of NFRs; and • Lust - embracing the latest and greatest technology without evaluating the impact incurred by these choices.

DevOpsNorth 2017 "Seven (More) Deadly Sins of Microservices"

Daniel Bryant

Microservices are where it's at. Everything is easier to manage when it's micro, right? Micro code bases (less than 10 LOC), micro containers (less than 10Mb), and micro teams (less than one person???). 'Micro' things may appear to be easier to manage, but there is always a macro context, and working with people and teams is no exception. This talk presents some of the challenges the OpenCredo team have seen when implementing microservices within a range of organisations, and we'll suggest tricks and techniques to help you manage your 'micro' teams and the 'macro' level. Topics covered include: empathy - because understanding others is at the heart of everything you do; leadership - advice on creating shared understanding, conveying strategy, and developing your team; organisational structure - from Zappos' holocracy to MegaOrg's strict hierarchy, from Spotify's squads, chapters and guilds, to BigCorp's command and control. There is a management style for everybody; and more

microXchg 2017: "Microservices: The People and Organisational Impact"

Daniel Bryant

[Many thanks to Nginx for sponsoring this O'Reilly webinar!] Implementing a continuous delivery (CD) pipeline is not trivial, and the introduction of container technology to the development stack can introduce additional challenges and requirements. In this webcast we will look at the steps that are essential for creating an effective pipeline for creating and deploying containerized applications. Topic covered include: - The impact of containers on CD - Creating a container pipeline (including functional and nonfunctional testing) - Lessons learned the hard way A supporting O'Reilly report "Containerizing Continuous Delivery in Java" is also available, and this contains instructions and code for how to create a Jenkins-based continuous delivery pipeline that takes a series of Java applications and containerizes them, ready for functional and nonfunctional testing, and ultimately, deployment.

O'Reilly/Nginx 2016: "Continuous Delivery with Containers: The Trials and Tri...

Daniel Bryant

Why You Should Care About ALS @slidecomet @itseugenec

HighSpark | Visual Storytelling Agency

How to Make Awesome SlideShares: Tips & Tricks

SlideShare

En vedette (10)

CraftConf [Preview] "Empathy - The Hidden Ingredient of Good Software Develop...

OSCON EU 2016 "Seven (More) Deadly Sins of Microservices"

muCon 2016: "Seven (More) Deadly Sins of Microservices"

Haufe #msaday: "Building a Microservice Ecosystem"

Devternity 2016 "Thinking Fast and Slow with Software Development"

DevOpsNorth 2017 "Seven (More) Deadly Sins of Microservices"

microXchg 2017: "Microservices: The People and Organisational Impact"

O'Reilly/Nginx 2016: "Continuous Delivery with Containers: The Trials and Tri...

Why You Should Care About ALS @slidecomet @itseugenec

How to Make Awesome SlideShares: Tips & Tricks

Similaire à MicroManchester 2016 "A Brief Guide to Microservices"

Daniel Bryant's slides from his talk at Haufe Microservices Architecture Day 2016. Microservice platforms are finally becoming a reality: Mesos, Kubernetes, and a whole bunch of PaaS-style offerings are available, but the reality is that these platforms still don’t provide everything you need in order to build a fully functional microservice ecosystem. Come to this session to learn about the essential deployment, orchestration, and glue components that often have to be self-assembled. The presentation begins by looking at deployment techniques and tools and examines where to test (QA, staging, or production), how to test (integration and contracts), and how to separate deployment and release. It then discusses orchestration, configuration, and service discovery. Finally it looks at essential glue such as logging, monitoring, and alerting.

Haufe #msaday - Building a Microservice Ecosystem by Daniel Bryant

OpenCredo

Building a microservice ecosystem

Haufe-Lexware GmbH & Co KG

Microservices: The Organizational and People Impact

Ambassador Labs

Last year at this conference we learned from Mark Richards that modern software has almost completed its evolution toward component-based architectures—seen in the mainstream embrace of self-contained systems (SCS), microservices, and serverless architecture. We all know the benefits of component-based architectures, but there are also many challenges to delivering such applications in a continuous, safe, and rapid fashion. Daniel Bryant shares a series of patterns to help you identify and implement solutions for continuous delivery of contemporary service-based architectures. Topics include: - The core stages in the component delivery lifecycle: Develop, test, deploy, operate, and observe - How contemporary architectures impact continuous delivery and how to ensure that this is factored into the design - Modifying the build pipeline to support testability and deployability of components (with a hat tip to Jez Humble’s and Dave Farley’s seminal work) - Commonality between delivery of SCS, microservices, and serverless components - Continuous delivery, service contracts, and end-to-end validation: The good, the bad, and the ugly - Validating NFRs within a service pipeline - Lessons learned in the trenches

O'Reilly SACON "Continuous Delivery Patterns for Contemporary Architecture"

Daniel Bryant

EPrints Update, Les Carr, University of Southampton

Repository Fringe

2016: Applying AI Innovation in Business

Leandro de Castro

All is not completely rosy in microservice-land. It’s often a sign of an architectural approach’s maturity that anti-patterns begin to be identified and classified alongside well-established principles and practices. Daniel Bryant introduces seven deadly sins from real projects, which left unchecked could easily ruin your next microservices project. Daniel offers an updated tour for 2016 of some of the nastiest anti-patterns in microservices from several real-world projects he’s encountered as a consultant, providing a series of anti-pattern “smells” you can sniff out and exploring the tools and techniques you need to avoid or mitigate the potential damage. Topics include: - Pride: Selfishly building the wrong thing, such as the “Inter-Domain-Enterprise-Application-Service-Bus” or a fully bespoke infrastructure platform - Envy: Introducing inappropriate intimacy within services by creating a shared “canonical” domain model - Wrath: Failing to deal with the inevitable bad things that occur within a distributed system - Sloth: Composing services in a lazy fashion, which ultimately leads to the creation of a “distributed monolith” - Lust: Embracing the latest and greatest technology without evaluating the operational impact incurred by these choices

JAXDevOps 2017 "The Seven (More) Deadly Sins of Microservices

Daniel Bryant

The seven deadly sins of microservices

Haufe-Lexware GmbH & Co KG

CraftConf 2017 "Microservices: The Organisational and People Impact"

Daniel Bryant

The seven more deadly sins of microservices final

Haufe-Lexware GmbH & Co KG

Haufe #msaday - Seven More Deadly Sins of Microservices by Daniel Bryant

OpenCredo

Geeks bearing gifts: Unwrapping New Technologies, Version April12

ayoungkin

Modern software development architecture has almost completed its evolution towards being properly component-based: this can be seen by the mainstream embracing Self Contained Systems (SCS), microservices, and serverless. We all know the benefits this can bring, but there can be many challenges delivering applications built using these styles in a continuous, safe, and rapid fashion. This talk presents a series of patterns based on real-world experience, which will help architects identify and implement solutions for continuous delivery of contemporary architectures. Key topics and takeaways include: - Core stages in the component delivery lifecycle: develop, test, deploy, operate and observe - How contemporary architectures impact continuous delivery - Modifying the build pipeline for testability and deployability of components (with a hat tip to Jez Humble and Dave Farley’s seminal work) - Commonality between delivery of SCS, microservices and serverless components - Continuous delivery, service contracts and end-to-end validation: The good, bad and ugly - Lessons learned in the trenches

JAX DevOps 2018 "Continuous Delivery Patterns for Modern Architectures"

Daniel Bryant

Modern Java applications are moving towards component-based architectures, as seen in the mainstream embrace of self-contained systems (SCS), microservices, and serverless architecture. We all know the benefits of component-based architectures, but there are also many challenges to delivering such applications in a continuous, safe, and rapid fashion. Daniel Bryant shares a series of patterns to help you identify and implement solutions for continuous delivery of contemporary service-based architectures. Topics include: – The core stages in the component delivery lifecycle: Develop, test, deploy, operate, and observe – How contemporary architectures impact continuous delivery and how to ensure that this is factored into the design – Modifying the build pipeline to support testability and deployability of components (with a hat tip to Jez Humble’s and Dave Farley’s seminal work) – Commonality between delivery of SCS, microservices, and serverless components – Continuous delivery, service contracts, and end-to-end validation: The good, the bad, and the ugly – Validating NFRs within a service pipeline – Lessons learned in the trenches

jSpring 2018 "Continuous Delivery Patterns for Modern Architectures and Java"

Daniel Bryant

All is not completely rosy in microservice-land. It’s often a sign of an architectural approach’s maturity that anti-patterns begin to be identified and classified alongside well-established principles and practices. Daniel Bryant introduces seven deadly sins from real projects, which left unchecked could easily ruin your next microservices project. Daniel offers an updated tour of some of the nastiest anti-patterns in microservices from several real-world projects he’s encountered as a consultant, providing a series of anti-pattern “smells” to watch out for and exploring the tools and techniques you need to avoid or mitigate the potential damage. Topics include: Pride: the admission of the challenges with testing in a distributed system Envy: introducing inappropriate intimacy within services by creating a shared “canonical” domain model Wrath: failing to deal with the inevitable bad things that occur when operating new technologies, both from the people and technical aspects Sloth: composing services in a lazy fashion, which ultimately leads to the creation of a "distributed monolith” Lust: embracing the latest and greatest technology without evaluating the operational impact incurred by these choices

GOTO Chicago/CraftConf 2017 "The Seven (More) Deadly Sins of Microservices"

Daniel Bryant

IDCC Presentation on the Future of Data Management Planning, Feb 2016

Stephanie Simms

Digital Catapult Centre Brighton - Bill Harpley

wired_sussex

Building Java applications for the IaaS cloud is easy, right? “Sure, no problem. Just lift and shift,” all the cloud vendors shout in unison. However, the reality of building and deploying cloud applications can often be different. This session introduces lessons learned from the trenches during several years of designing and implementing cloud-based Java applications, which we have codified into our Cloud Developer's “DHARMA” rules: Documented (just enough); Highly cohesive/loosely coupled (all the way down); Automated from code commit to cloud; Resource-aware; Monitored thoroughly; and Antifragile. This session was presented at JavaOne 2014

JavaOne 2014: Cloud Developer's DHARMA: Redefining 'done' for Cloud applications

Daniel Bryant

So, the citizen developers have all the cool tools, and those that actually code for a living are left with legacy stuff? Not so fast! The same tools that Microsoft is targeting for citizen developers make development easier, faster and cheaper for everyone! This session combines tools such as Flow, Azure Cognitive Services and Azure Functions with some actual simple development work to provide highly customized, Machine Learning powered analysis workflow for the newly baked Modern Team Sites in SharePoint Online. This demo-heavy session will look at real business scenarios, and how we can solve them using citizen developer tools and some code (Because we’re developers after all, right?) After this session, you'll know how to create rich and customized business automation processes that use the latest tools offered to us by Microsoft.

Citizen Developer Tools (session at SharePoint Saturday Houston 4/28/2018) by...

Antti Koskela

Unified Communications as a Service (or UCaaS), is a relatively new opportunity for service providers, making a complete business communications solution available from virtually anywhere and billed on a monthly basis, without the cost of on-premises equipment. The OPEX model makes UCaaS extremely popular with growing and distributed companies. One of the popular software providers enabling the UCaaS market is 3CX, an open-standards communications solution. Service providers are discovering that deploying 3CX as a service is an excellent opportunity to grow their business, bringing business-class UCaaS to a range of vertical markets and geographies. As we’ll show today, TelcoBridges’ ProSBC offers a valuable set of capabilities to make hosted 3CX implementations secure, avoids on-premises CPE, is easy to manage and the subscription-based business model makes scaling easy and affordable. In this recorded webinar, we are joined by Matt Ussery, CIO and founder of Austen Consultants, and take a closer look at how he built his successful hosted cloud service based on 3CX and ProSBC. You can view the recording at: https://youtu.be/YX8C0UBtEec

UCaaS with 3cx and ProSBC

Alan Percy

Similaire à MicroManchester 2016 "A Brief Guide to Microservices" (20)

Haufe #msaday - Building a Microservice Ecosystem by Daniel Bryant

Building a microservice ecosystem

Microservices: The Organizational and People Impact

O'Reilly SACON "Continuous Delivery Patterns for Contemporary Architecture"

EPrints Update, Les Carr, University of Southampton

2016: Applying AI Innovation in Business

JAXDevOps 2017 "The Seven (More) Deadly Sins of Microservices

The seven deadly sins of microservices

CraftConf 2017 "Microservices: The Organisational and People Impact"

The seven more deadly sins of microservices final

Haufe #msaday - Seven More Deadly Sins of Microservices by Daniel Bryant

Geeks bearing gifts: Unwrapping New Technologies, Version April12

JAX DevOps 2018 "Continuous Delivery Patterns for Modern Architectures"

jSpring 2018 "Continuous Delivery Patterns for Modern Architectures and Java"

GOTO Chicago/CraftConf 2017 "The Seven (More) Deadly Sins of Microservices"

IDCC Presentation on the Future of Data Management Planning, Feb 2016

Digital Catapult Centre Brighton - Bill Harpley

JavaOne 2014: Cloud Developer's DHARMA: Redefining 'done' for Cloud applications

Citizen Developer Tools (session at SharePoint Saturday Houston 4/28/2018) by...

UCaaS with 3cx and ProSBC

Plus de Daniel Bryant

API Gateways are certainly not a new technology, but the way in which they are being deployed, configured, and operated within modern platforms is forcing many of us to rethink our approach. Can we simply lift and shift our existing gateway into the cloud? Is our API gateway GitOps friendly (and does it need to be)? And what about service meshes, CNI, eBPF, and... Join this talk for a whistle stop tour of modern API gateways, which a focus on deploying and managing this technology within Kubernetes (on which many modern platforms are built): - Understand why platform engineers should care about API Gateways today - Learn about API gateways, options, and requirements for modern platforms - Identify key considerations for migrating to the cloud or building a new platform on Kubernetes - Understand how cloud native workflows impact the user/developer experience (UX/DX) of an API gateway - Explore the components of a complete "edge stack" that supports end-to-end development flows

ITKonekt 2023: The Busy Platform Engineers Guide to API Gateways

Daniel Bryant

When enterprise organizations adopt microservices, containers, and cloud native development, the technologies and architectures may change, but the fact remains that we all still add the occasional bug to our code. The main challenge you now face is how to perform integration or end-to-end testing without spinning up all of your microservices locally and driving your laptop fans into high speed! Join me for a tour of your microservices testing options using a series of Java-friendly tools. - Explore challenges with scaling container-based application development (you can only run so many microservices locally before minikube melts your laptop) - Learn about effective unit testing with mocks, using TestContainers for dependency testing, and using Telepresence to extend your local testing environment into the cloud - Understand when to use each type of test and tooling based on your use case and requirements for realism, speed, and practicality - See how Telepresence can "intercept" or reroute traffic from a specified service in a remote K8s cluster to your local dev machine

CraftConf 2023 "Microservice Testing Techniques: Mocks vs Service Virtualizat...

Daniel Bryant

PlatformCon 23: "The Busy Platform Engineers Guide to API Gateways"

Daniel Bryant

Java Meetup 23: 'Debugging Microservices "Remocally" in Kubernetes with Telep...

Daniel Bryant

Over the last year, the Ambassador Labs team has doubled down on their adoption of Product Led Growth (PLG), a growth model where product usage drives customer acquisition, retention, and expansion. It’s been an interesting journey for the DevRel team, who have found themselves working more closely with both the sales and growth engineering teams. In their quest to reduce the friction of product adoption, they’re thinking more and more about the end-to-end experiences, experimentation, instrumentation, data analysis, and handoffs — much like we saw in the software development world with the adoption of DevOps breaking down barriers between engineering and operations. The Ambassador Labs team have learned more about the value of creating hypotheses and analyzing quantitative data, but have also been reminded that there is no substitute for qualitative data and engaging human-to-human. Join Daniel for a whistle-stop tour of PLG through the DevRel lens: – Understand how moving to PLG can impact devrel teams and the work they do: for better and worse! – Explore how DevRel tooling and community platforms are increasingly overlapping with PLG marketer tooling – Learn how to structure your goals, common languages, and teams for successfully adopting PLG

DevRelCon 2022: "Is Product Led Growth (PLG) the “DevOps” of the DevRel World"

Daniel Bryant

Developers building applications on Kubernetes today are being asked to not just code applications -- they are also responsible for shipping and running their applications, too. We often talk about needing a Kubernetes platform, but are we really looking for a PaaS? Or instead, are we looking for some kind of developer control plane with a Goldilock-sized collection of tools that provides just the right amount of platform? This talk will look back on my experience of building platforms, both as an end-user and now as part of an organization helping our customers do the same. We’ll wrap this talk with a walk-through of the CNCF ecosystem through the developer control plane lens, and look at what’s next in the future of this important emerging category.

Fall 22: "From Kubernetes to PaaS to... err, what's next"

Daniel Bryant

Join me for a tour of coding, testing, and shipping microservices using remote-to-local “remocal” tools and techniques. You will: - Understand the challenges with scaling container-based application development – i.e. you can only run so many microservices locally before minikube melts your laptop. - Learn when to use various types of development practices and tooling based on your use case and requirements for production realism, speed, and practicality. - Explore how to utilize containerized dependencies and Docker for testing, including for both apps and services you own and those you don’t. - Learn how Telepresence can enable “remocal” development, expanding your local machine and Docker Desktop out into a remote Kubernetes cluster.

Building Microservice Systems Without Cooking Your Laptop: Going “Remocal” wi...

Daniel Bryant

Many organizations adopt cloud native development practices with the goal of shipping features faster. The technologies and architectures may change when we move to the cloud, but the fact remains that we all still add the occasional bug to our code. The challenge here is that many of your existing local debugging tools and practices can’t be used when everything is running in a container or deployed onto Kubernetes running in the cloud. This is where the open source Telepresence tool can help. Join Daniel to learn about: - Quick overview of remote-local ("remocal") options and tooling e.g. “kubectl port-forward”, Skaffold, ksync, Telepresence etc. - An exploration of how Telepresence can “intercept” or reroute traffic from a specified service in a remote K8s cluster to your local dev machine -- The benefits of getting a “hot reload” fast feedback loop between applications being developed locally and apps running in the remote environment

KubeCrash 22: Debugging Microservices "Remocally" in Kubernetes with Telepres...

Daniel Bryant

When enterprise organizations adopt microservices, containers, and cloud native development, the technologies and architectures may change, but the fact remains that we all still add the occasional bug to our code. The main challenge you now face is how to perform integration or end-to-end testing without spinning up all of your microservices locally and driving your laptop fans into high speed! Join me for a tour of testing microservices using a series of Java applications as a case study. You will learn everything about effective unit testing with mocks, using TestContainers for dependency testing, and using Telepresence to extend your local testing environment into the cloud. Learn when to use each type of test and tooling based on your use case and requirements for realism, speed, and practicality. We will discuss how to utilize containerized dependencies and Docker for testing, including both apps and services you own and those you don’t. We’ll also go over the challenges with scaling container-based application development (you can only run so many microservices locally before minikube melts your laptop). Finally, you’ll see how Telepresence can "intercept" or reroute traffic from a specified service in a remote K8s cluster to your local dev machine.

JAX London 22: Debugging Microservices "Remocally" in Kubernetes with Telepre...

Daniel Bryant

Many engineers are confused about how a cloud-native API gateway relates to Kubernetes Ingress or a Service load balancer. This talk will unravel this confusion. An API gateway is at the core of how APIs are managed, secured and presented within any web-based system. Although the technology has been in use for many years, it has not always kept pace with recent developments within the cloud-native space. Join Daniel Bryant in uncovering the evolution of API gateways over the past ten years and how the original problems they were solving have shifted in relation to cloud-native technologies and workflow.

CloudBuilders 2022: "The Past, Present, and Future of Cloud Native API Gateways"

Daniel Bryant

Developers building applications on Kubernetes today are being asked to not just code applications -- they are also responsible for shipping and running their applications, too. We often talk about needing a Kubernetes platform, but are we really looking for a PaaS? Or instead, are we looking for some kind of developer control plane with a Goldilock-sized collection of tools that provides just the right amount of platform? This talk will look back on my experience of building platforms, both as an end-user and now as part of an organization helping our customers do the same. The key takeaways are: - Treat platform as a product - Realize that you can’t have good developer experience (DevEx) without good UX - Focus on workflows and tooling interoperability We’ll wrap this talk with a walk-through of the CNCF ecosystem through the developer control plane lens, and look at what’s next in the future of this important emerging category.

KubeCon EU 2022: From Kubernetes to PaaS to Err What's Next

Daniel Bryant

Many Java-based organizations adopt cloud native development practices with the goal of shipping features faster. The technologies and architectures may change when we move to the cloud, but the fact remains that we all still add the occasional bug to our code. The challenge here is that many of your existing local debugging tools and practices can’t be used when everything is running in a container or deployed onto Kubernetes running in the cloud. This is where the open source Telepresence tool can help. Join me to learn about: – The challenges with scaling Kubernetes-based Java development i.e. you can only run so many microservices locally before minikube melts your laptop – Quick overview of remote-local ("removal") options and tooling e.g. “kubectl port-forward”, Skaffold, ksync, Telepresence etc – An exploration of how Telepresence can “intercept” or reroute traffic from a specified service in a remote K8s cluster to your local dev machine – The benefits of getting a “hot reload” fast feedback loop between applications being developed locally and apps running in the remote environment

Devoxx UK 22: Debugging Java Microservices "Remocally" in Kubernetes with Tel...

Daniel Bryant

Developers building applications on Kubernetes today are being asked to not just develop applications -- they are also responsible for releasing and running their applications, too. In this talk, we’ll discuss the secular shift towards what Netflix calls “Full Cycle Development” or what Google calls “Service Ownership”. With developers managing so much of the cloud-native development loop, a new class of infrastructure has emerged -- the developer control plane. We’ll explore the evolution from Kubernetes to PaaS, to the developer control planes in use today. We’ll draw on our personal experiences and podcast chats with the larger CNCF community, and discuss real-world examples of developer control planes used at New Relic, Spotify, InVision, and Twitter. We’ll wrap this talk with a walk through of the CNCF ecosystem through the developer control plane lens, and look at what’s next in the future of this important emerging category.

DevXDay KubeCon NA 2021: "From Kubernetes to PaaS to Developer Control Planes"

Daniel Bryant

At a previous JAX event I talked about effective cloud native Java developer workflow. Two years later and many new developer technologies have come and gone, but I still hear daily from cloud developers about the pain and friction associated with building, debugging, and deploying to the cloud. In this talk I’ll share my latest learning on how to bring the fun and productivity back into delivering Kubernetes-based software. Join this talk to: Learn why the core tenets of continuous delivery — speed and safety — must be considered in all parts of the cloud native SDLC Explore how cloud native coding benefits from thinking separately about the inner development loop, continuous integration, continuous deployment, observability, and analysis Understand how cloud native best practices and tooling fit together. Learn about artifact syncing (e.g. Skaffold), dev environment bridging (e.g. Telepresence), GitOps (e.g. Argo), and observability-focused monitoring (e.g. Prometheus, Jaeger) Explore the importance of cultivating an effective cloud platform and associated team of experts Walk away with an overview of tools that can help you develop and debug effectively when using Kubernetes

JAX London 2021: Jumpstart Your Cloud Native Development: An Overview of Prac...

Daniel Bryant

Many organizations adopt cloud native development practices with the goal of shipping features faster. The technologies and architectures may change when we move to the cloud, but the fact remains that we all still add the occasional bug to our code. The challenge here is that many of your existing local debugging tools and practices can't be used when everything is running in a container or deployed onto Kubernetes running in the cloud. This is where the open source Telepresence tool can help. Join me to learn about: - The challenges with scaling Kubernetes-based Java development i.e. you can only run so many microservices locally before minikube melts your laptop - An exploration of how Telepresence can "intercept" or reroute traffic from a specified service in a remote K8s cluster to your local dev machine - The benefits of getting a "hot reload" fast feedback loop between applications being developed locally and apps running in the remote environment - A tour of Telepresence, from the sidecar proxy deployed into the remote K8s cluster to the CLI - An overview of using "preview URLs" and header-based routing for the sharing, collaboration, and isolation of changes you are making on your local copy of an intercepted service

Container Days: Easy Debugging of Microservices Running on Kubernetes with Te...

Daniel Bryant

By Daniel Bryant, Ambassador Labs We all need to be able to get user traffic into our applications, and your requirements for services running on Kubernetes are no different. "But", I hear you say, "what about the K8s Ingress spec? And how do I observe what's happening under the hood? And who should be responsible for configuring the gateway: dev or ops?" These are all good questions! Join me for a whistle-stop tour of all things emissary-ingress, where we will explore how this new edition to the family of CNCF incubation projects can make your life easier when it comes to routing, observability, and integration into the bigger (people and technology) picture.

Canadian CNCF: "Emissary-ingress 101: An introduction to the CNCF incubation-...

Daniel Bryant

Many Java-based organizations adopt cloud native development practices with the goal of shipping features faster. The technologies and architectures may change when we move to the cloud, but the fact remains that we all still add the occasional bug to our code. The challenge here is that many of your existing local debugging tools and practices can't be used when everything is running in a container or deployed onto Kubernetes running in the cloud. This is where the open source Telepresence tool can help. Join me to learn about: - The challenges with scaling Kubernetes-based Java development i.e. you can only run so many microservices locally before minikube melts your laptop - An exploration of how Telepresence can "intercept" or reroute traffic from a specified service in a remote K8s cluster to your local dev machine - The benefits of getting a "hot reload" fast feedback loop between applications being developed locally and apps running in the remote environment - A tour of Telepresence, from the sidecar proxy deployed into the remote K8s cluster to the CLI - An overview of using "preview URLs" and header-based routing for the sharing, collaboration, and isolation of changes you are making on your local copy of an intercepted service

MJC 2021: "Debugging Java Microservices Running on Kubernetes with Telepresence"

Daniel Bryant

Many Java-based organizations adopt cloud native development practices with the goal of shipping features faster. The technologies and architectures may change when we move to the cloud, but the fact remains that we all still add the occasional bug to our code. The challenge here is that many of your existing local debugging tools and practices can't be used when everything is running in a container or deployed onto Kubernetes running in the cloud. This is where the open source Telepresence tool can help. Join me to learn about: - The challenges with scaling Kubernetes-based Java development i.e. you can only run so many microservices locally before minikube melts your laptop - An exploration of how Telepresence can "intercept" or reroute traffic from a specified service in a remote K8s cluster to your local dev machine - The benefits of getting a "hot reload" fast feedback loop between applications being developed locally and apps running in the remote environment - A tour of Telepresence, from the sidecar proxy deployed into the remote K8s cluster to the CLI - An overview of using "preview URLs" and header-based routing for the sharing, collaboration, and isolation of changes you are making on your local copy of an intercepted service

LJC 4/21"Easy Debugging of Java Microservices Running on Kubernetes with Tele...

Daniel Bryant

At GOTO Amsterdam in 2019 I presented how to create an effective cloud native developer workflow. Two years later and many new developer technologies have come and gone, but I still hear daily from cloud developers about the pain and friction associated with building, debugging, and deploying to the cloud. In this talk I'll share my latest learning on how to bring the fun and productivity back into delivering Kubernetes-based software. Join this talk to: Learn why the core tenets of continuous delivery -- speed and safety -- must be considered in all parts of the cloud native SDLC Explore how cloud native coding benefits from thinking separately about the inner development loop, continuous integration, continuous deployment, observability, and analysis Understand how cloud native best practices and tooling fit together. Learn about artifact syncing (e.g. Skaffold), dev environment bridging (e.g. Telepresence), GitOps (e.g. Argo), and observability-focused monitoring (e.g. Prometheus, Jaeger) Explore the importance of cultivating an effective cloud platform and associated team of experts Walk away with an overview of tools that can help you develop and debug effectively when using Kubernetes

GOTOpia 2/2021 "Cloud Native Development Without the Toil: An Overview of Pra...

Daniel Bryant

HashiCorp Consul integrates with Ambassador to securely route Ingress traffic to Consul Service Mesh when using Kubernetes. When onboarding applications onto a service mesh or when integrating with existing applications outside of the Mesh, a north south API gateway is typically required for communications with clients outside of the network. Ambassador is a Kubernetes API Gateway that allows you to route incoming traffic to your Consul Service Mesh proxies while also providing the ability to leverage advanced API Gateway functionalities such as rate limiting and authentication.

HashiCorp Webinar: "Getting started with Ambassador and Consul on Kubernetes ...

Daniel Bryant

Plus de Daniel Bryant (20)