Software Development: Thinking, Fast and Slow

•Download as PPTX, PDF•

1 like•2,419 views

The document discusses how cognitive biases and heuristics affect software developers' thinking and decision making. It explores Daniel Kahneman's concepts of System 1 thinking (fast, emotional, instinctive) and System 2 thinking (slower, deliberate, reasoning). Specific biases that can influence developers are then examined, including the availability heuristic (recalling what is memorable), substitution heuristic (replacing complex judgments with easier ones), and anchoring bias (relying too heavily on initial information). The document encourages developers to employ techniques like constant learning, prototyping, and unbiased estimation practices to overcome these cognitive tendencies.

Technology

Professional Software Development:
Thinking, Fast and Slow
Daniel Bryant
CTO, Instant Access Technologies
d.bryant@iatltd.com
@taidevcouk

Thinking, Fast and Slow
An awesome book!
Exploring how we think…
“Bias and decision heuristics”
amzn.to/KidCCy
21/03/2014 @taidevcouk

Your Thinking: A Tale of Two Systems…
System 1:
fast, instinctive, emotional, subconscious
Systemic errors
System 2:
slower, deliberate, reasoning, conscious
Lazy, and causal (not statistical)
21/03/2014 @taidevcouk

Heuristics / biases affecting software developers
21/03/2014 @taidevcouk

Availability Heuristic
“If something can be recalled,
it must be important”
Ever notice that MongoDB are at every conference?
…and every application seems to use MongoDB?
21/03/2014 @taidevcouk

Substitution Heuristic
“…a computationally complex judgment
will be substituted
for a more easily calculated heuristic”
Observe what happens when you ask…
‘Is Scala a good choice for your current project?’
21/03/2014 @taidevcouk

Anchoring Bias
“Common tendency to rely too heavily
on the first piece of information offered
when making decisions. ”
How does your manager ask for estimates?
…is it an unbiased question?
21/03/2014 @taidevcouk

Thinking Professionally
• Availability
– Constant learning and evaluation
– Spike, prototype, experiment…
• Substitution
– Matt Raible comparison matrix (bit.ly/OxUzad)
• Anchoring
– ‘Clean Coder’ PERT Estimation (amzn.to/1dr0SSW)
21/03/2014 @taidevcouk

Thanks for Listening!
This is a beta lightning talk…
… was it interesting? Please let me know!
Contact me:
d.bryant@iatltd.com
@taidevcouk
21/03/2014 @taidevcouk

Viewers also liked

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 briefly 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. This is the second iteration of this talk.

LJC 2014 "Professional Software Development: Thinking Fast and Slow"

Daniel Bryant

Come along and learn how the Crafty Consultant makes his money by consulting craftily in DevOps. We'll see how silos can be broken down by introducing more independent and isolated team, how only idiots automate everything, and why monitoring only provides actionable insight that simply confuses your clients... ...and then we'll look at the real world implementation of DevOps :-) The primary aims of this talk are to introduce the concepts behind the DevOps movement, and we'll do this by debunking all of the Crafty Consultant's advice. We'll cover the drivers of breaking down silos (in business and in tech), the benefits of automation (especially with provisioning and configuring infrastructure), and the power that monitoring provides (particularly when deploying to the cloud, or implementing a microservice architecture).

LJC 2015 "The Crafty Consultants Guide to DevOps"

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!

Jfokus 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

EVRYTHNG: Concepts, technologies and applications for connecting physical obj...

EVRYTHNG

5 Years of Web of Things Workshops

Dominique Guinard

Viewers also liked (7)

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

LJC 2014 "Professional Software Development: Thinking Fast and Slow"

LJC 2015 "The Crafty Consultants Guide to DevOps"

Jfokus 2015 "Thinking Fast and Slow with Software Development"

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

EVRYTHNG: Concepts, technologies and applications for connecting physical obj...

5 Years of Web of Things Workshops

Similar to Software Development: Thinking, Fast and Slow

Guest lecture at "Advanced Design: Innovation and Trans-disciplinary in Architectural Design" Post-Graduate programme of studies, School of Architecture, Aristotle University of Thessaloniki. SUMMARY: An introduction to Free/Libre Open Source Software development philosophy and the essential tools / processes needed to evolve from individually creating F/LOSS code to social coding as part of a F/LOSS community.

Doing F/LOSS :: The Cathedral & the Bazaar

Apostolos Kritikos

JAX London 2016: "Empathy - The hidden ingredient of good software development?"

Daniel Bryant

Julia Flanders, who is the Director of the Digital Scholarship Group in the Northeastern University Library, and a Professor of Practice in Northeastern's English Department gave a talk on Jobs, Roles, Skills, Tools: Working in the Digital Academy as part of the Program on Information Science Brown Bag Series. In the talk, illustrated by the slides below, Julia discusses the evolving landscape of digital humanities (and digital scholarship more broadly) and considers the relationship between technology, tool development, and professional roles. For more see: http://informatics.mit.edu/event/brown-bag-jobs-roles-skills-tools-working-digital-academy-julia-flanders

MIT Program on Information Science Talk -- Julia Flanders on Jobs, Roles, Ski...

Micah Altman

How do you test ideas? Sounds like a hard question... What does it even mean? To test ideas, you need to break out of a traditional mindset of thinking that testing purely relates to the boundaries of making sure that software meets the expectations of how it is supposed to work. We need to think more about the unknowns... The unexpected things relating to software. Only then can we transpire those ideas of unknowns to our initial thinking about the software solution before we even attempt to write a line of code or an artefact to try and describe the expectations. All software starts with an idea - an idea for a solution to a problem, or an idea to make money, or an idea to delight people. Testing the idea of the software solution is a hugely important part of continuous testing. This testing, at the earliest point in time within the SDLC, actually helps prevent problems and bugs. It helps uncover unknowns. Unknowns related to risks and unknowns that cause assumptions and ambiguities within the design and development of the software. And this testing requires a whole host of psychology and sociology skills. In this talk, Dan will share his ideas, experiences, success stories and pain points, strategies, tips & tricks and more, regarding why and how to test your ideas.

Testing the ideas

Dan Ashby

Emerging practices 2019 week 1

R. Sosa

Understanding 20161128 v8

ISSIP

Emerging practices 2019 week 2

R. Sosa

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.

CraftConf16 "Empathy: The Hidden Ingredient of Good Software Development?"

Daniel Bryant

Emerging practices 2019 week 3

R. Sosa

This talk explores how thinking could be formulated as a blockchain process that could have benefits for both artificial intelligence and human enhancement. Some possibilities might include the ability to orchestrate digital mindfile uploads, advocate for digital intelligences in future timeframes, implement smart contract-based utility functions, instantiate thinking as a power law, and facilitate the enactment of Friendly AI.

Blockchain Thinking: The Brain as a DAC (Decentralized Autonomous Corporation)

Melanie Swan

SuanIct-Bigdata desktop-final

stelligence

As design leaders we must enable our teams with skills and knowledge to take on the new and exciting opportunities that building powerful AI systems bring. Dynamic systems require transparency regarding data provenance, bias, training methods, and more, to gain user’s trust. Carol will cover these topics and challenge us as design leaders, to represent our fellow humans by provoking conversations regarding critical ethical and safety needs. Presented at dmi:Design Leadership Conference in Boston in October 2018.

Designing AI for Humanity at dmi:Design Leadership Conference in Boston

Carol Smith

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

Daniel Bryant

Creating An Incremental Architecture For Your System

Giovanni Asproni

Oss swot

Bill Ott

In open collaboration systems, work gets done through talking. We support a particular kind of talk-based work -- deletion discussions in Wikipedia -- by categorizing and summarizing discussions. In a user test, 84% find benefit from this. This talk about my thesis was given 2013-09-18 in Malta at the Virtual Work training school: http://dynamicsofvirtualwork.com/malta-training-school/ part of the COST action on Virtual Work http://cost.eu/domains_actions/isch/Actions/IS1202

Talking is (virtual) work -supporting online argumentation--2013-09-18 Malta ...

jodischneider

EDHREC @ Data Science MD

Donald Miner

Data Science in 2016: Moving Up

Paco Nathan

The term 'Data Science' was first described in scientific literature about 15 years ago. It started to become a major trend in industry about 7 years ago. O'Reilly Media surveys the industry extensively each year. In addition we get a good birds-eye view of industry trends through our conference programs and publications, working closely with some of the best practitioners in Data Science. By now, the field has evolved far beyond its origins eclipsing an earlier generation of Business Intelligence and Data Warehousing approaches. Data Science is moving up, into the business verticals and government spheres of influence where it has true global impact. This talk considers Data Science trends from the past three years in particular. What is emerging? Which parts are evolving? Which seem cluttered and poised for consolidation or other change? Session presented at Big Data Spain 2015 Conference 15th Oct 2015 Kinépolis Madrid http://www.bigdataspain.org Event promoted by: http://www.paradigmatecnologico.com Abstract: http://www.bigdataspain.org/program/thu/slot-2.html

Data Science in 2016: Moving up by Paco Nathan at Big Data Spain 2015

Big Data Spain

Big Data: the weakest link

CS, NcState

Similar to Software Development: Thinking, Fast and Slow (20)

Doing F/LOSS :: The Cathedral & the Bazaar

JAX London 2016: "Empathy - The hidden ingredient of good software development?"

MIT Program on Information Science Talk -- Julia Flanders on Jobs, Roles, Ski...

Testing the ideas

Emerging practices 2019 week 1

Understanding 20161128 v8

Emerging practices 2019 week 2

CraftConf16 "Empathy: The Hidden Ingredient of Good Software Development?"

Emerging practices 2019 week 3

Blockchain Thinking: The Brain as a DAC (Decentralized Autonomous Corporation)

SuanIct-Bigdata desktop-final

Designing AI for Humanity at dmi:Design Leadership Conference in Boston

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

Creating An Incremental Architecture For Your System

Oss swot

Talking is (virtual) work -supporting online argumentation--2013-09-18 Malta ...

EDHREC @ Data Science MD

Data Science in 2016: Moving Up

Data Science in 2016: Moving up by Paco Nathan at Big Data Spain 2015

Big Data: the weakest link

More from 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

More from Daniel Bryant (20)