[SC London] "Testing Microservices: from Development to Production

•Télécharger en tant que PPTX, PDF•

1 j'aime•360 vues

Dividing a system into a series of services that communicate over an unreliable network naturally creates challenging conditions for testing inter-service interactions. Each service has its own functional requirements, and performance and fault-tolerance characteristics that need to be validated during development, the QA process, and continually in production. Join Daniel Bryant to learn about the theory, techniques, and practices that can help to overcome these challenges. Overview and learning Outcomes: • Introduction to the challenges of testing distributed microservice systems • Learn tactics for isolating tests within a complex microservice ecosystem • Join a whistle-stop tour of consumer-driven contract testing and API simulation • Understand where to implement fault-injection within doubles in order to validate nonfunctional requirements in development and QA • Understand the benefits of continually validating microservice systems running in production

Logiciels

Testing Microservices:
From Development to Production
Daniel Bryant
@danielbryantuk

tl;dr
● Testing microservices brings additional challenges
● Pay special attention to integration surfaces
● Isolate services for loosely coupled tests
● Include tests that resemble production
● Make security testing a first-class citizen

Who am I?
@danielbryantuk
Product Architect at Datawire
Consultant, Writer
Java Champion, Conference Tourist
@abrahammarin
Developer, Consultant, Writer
Associate of Equal Experts
Software Plumber

Types of tests
From Agile Testing, by Lisa Crispin and Janet Gregory

Challenges
● Cannot share a single environment: test locally
● Full ecosystem unsuitable for local testing
● Lack of control over third-party dependencies

https://medium.com/@copyconstruct/testing-microservices-the-sane-way-9bb31d158c16
Software
Testing Funnel

Isolating Parts: No Isolation
Third Party

Isolating Parts: Unowned Components
Third Party

Test Doubles
Dummy objects: passed around but never actually used.
Fake objects: working implementations not suitable for production
Stubs: provide canned answers to calls made during the test
Spies: stubs that also record some information based on how they were called.
Mocks: objects pre-programmed with expectations which form a specification of the
calls they are expected to receive.
Virtualisations: emulation of services, with expectations (not suitable for production)
https://martinfowler.com/articles/mocksArentStubs.html

API Simulation Thoughts
● Useful when a dependency is “expensive” to
access or tricky to mock
● Facilitates error handling tests when dependency
failure modes are challenging to recreate
● Simulations can be fragile and/or complicated

Use simulations appropriately...
Sometime you need the real thing

Isolating Parts: Service Interaction
Third Party

Focused on
service/function
Focused on
system
Contract Tests

API Contracts
APIs are service contracts
Many are producer-driven
It’s possible to design outside-in:
Consumer-Driven Contracts

Consumer-Driven Contracts
https://www.baeldung.com/pact-junit-consumer-driven-contracts

Consumer-Driven Contract Frameworks
https://docs.pact.io/ https://cloud.spring.io/spring-cloud-contract/

Consumer-Driven Contract Thoughts
● Great in low trust or low communication organisations
○ Act as a cue for a conversation
● Can be used to implement “TDD for the API”
● Resource intensive to create and maintain

Isolating Parts: Single Service
Third Party

Isolating Parts: Single Service
Test
Doubles

Isolating Parts: Single Service
Fault Tolerance
Test double configured to fail

https://technology.cap-hpi.com/blog/unit-testing-what-benefits-you-can-reap/

Isolating Parts: Technicalities
Third Party

Isolating Parts: Technicalities
Test the Real Thing

Isolating Parts: Data
Test Data
● Low Volume
● Low Diversity
Production Data
● High Volume
● High Diversity

Isolating Parts: Data
Marín
Argüelles
d’Hopital
Garçon
Castaña
Strauß
Fønss
Bård
かほる
Александр
สมชาย
Φραγκόπουλος

Isolating Parts: Data
a а
“a” “azǔ”
U+0061 U+0430

www.owasp.org
https://www.owasp.org/index.php/C
ategory:OWASP_Top_Ten_Project

Security: Container Images
github.com/arminc/clair-scanner

Conclusion
● Testing microservices brings additional challenges
● Pay special attention to integration surfaces
● Isolate services for loosely coupled tests
● Include tests that resemble production
● Make security testing a first-class citizen

Thanks!
Feel free to ask questions...
@danielbryantuk

Semantic Txns / Synthetic Monitoring
https://martinfowler.com/bliki/SyntheticMonitoring.html

https://martinfowler.com/articles/microservice-testing/#conclusion-summary

Contenu connexe

Tendances

Orchestration of Microservices - Google dev fest 2017 Berlin

Zeebe

Digital Transformation through Open Software Defined Infrastructure

Open Networking Summit

Toshimasa Nasu LINE / Blockchain Lab While the LINE Token Economy concept and white paper was published in late August 2018, technical details and future architectural plans were not. This session focuses on key topics surrounding LINE's blockchain technology, including LINE's decision to expand services utilizing blockchain technology, reasons behind LINE to develop/launch its own blockchain platform, current issues and how LINE is working to solve them, LINE Token Economy infrastructure for creating blocks, and architecture for Smart Contracts execution platform.

Shedding Light on LINE Token Economy You Won't Find in Our White Paper

LINE Corporation

Real time web with SignalR

Alessandro Melchiori

Introduction to SignalR

University of Hawai‘i at Mānoa

Workshop on CIFS / SMB Protocol Performance Analysis

PerformanceVision (previously SecurActive)

Camunda launched Zeebe, a new open source project based around microservice orchestration. With Zeebe, you can decompose long-running and asynchronous business logic into microservices which are then orchestrated using visual workflows. Zeebe itself is extremely fast, horizontally scalable, fault-tolerant and highly available. With Zeebe you can reliably processes all your transactions as they happen.

Zeebe - a Microservice Orchestration Engine

camunda services GmbH

SignalR with ASP.NET MVC 6

Tung Nguyen Thanh

Ildikó Váncsa, Chris Price, and Carsten Rossenhövel's presentation at the 2017 Open Networking Summit. Communications service providers (CSPs) have a wide range of options when building virtualized services from the ground up including multiple choices for each functional block in the ETSI NFV reference architecture. CSPs prefer heterogeneous systems with building blocks from different vendors including open source software; for such deployments interoperability becomes a crucial requirement. OpenStack, as the NFVI and VIM, serves as a widely used cloud platform for telecom and NFV use cases. As a common base, OpenStack offers the means for vendors and other open source projects to ease the interoperability challenge by providing a set of open API’s while focusing on upgradeability and backward compatibility. However, when it comes to productization, interoperability testing often falls short and is sometimes left to the carrier as shown by the testing programs actively run by no fewer than 10 organizations today. Join Carsten Rossenhövel from the European Advanced Networking Test Center (EANTC) and the rapporteur (editor) of ETSI’s NFV interoperability standards, Ildikó Váncsa from the OpenStack Foundation, and Chris Price, Ericsson and OpenStack board director to learn more about The ETSI NFV Release 2 interoperability testing activities - standardization and recently completed ETSI PlugTest. Over 40 commercial and open source implementations were tested for interoperability, including 20 virtual network functions, 10 management and orchestration solutions and 10 NFV platforms. The New IP Agency (NIA) interoperability testing campaigns of commercial NFV implementations executed by EANTC, focusing on results, lessons learned and recommendations. How vendors and open source projects are stepping up to the challenge, realizing they must work together. How to stay up-to-date with OpenStack releases and the community. How to get involved to ensure you are aware of the latest developments and contribute what you need to OpenStack. What will I learn from attending this session? CSPs, open source projects and vendors alike will learn more about the recent ETSI PlugTest and NIA-commissioned interoperability testing, their results and how to architect full NFV solutions that will work together. Interoperability API tests and associated marks from OpenStack will be covered, as well as features to help stay current on OpenStack releases. Attendees will also hear from Ericsson about a vendor’s point of view, and how other projects such a OPNFV are evolving and expanding in scope to address this challenge.

The Interoperability Challenge in Telecom and NFS Environments

Open Networking Summit

Micro service architecture

Ayyappan Paramesh

Architecture Sustaining LINE Sticker services

LINE Corporation

Real-time ASP.NET with SignalR

Alexander Konduforov

SignalR for ASP.NET Developers

Shivanand Arur

SignalR

Troy Miles

Lisa Caywood and Colin Dixon's presentation at the 2017 Open Networking Summit. OpenDaylight has become a nexus for open source integration, creating a new open networking stack and enabling a new generation of open source, agile IT infrastructure. The fifth “Boron” release provides new tooling and documentation to support application developers, as well as greater integration with industry frameworks from OPNFV and OpenStack to CORD and Atrium. Boron also brings a practical focus on two leading types of deployments: (1) direct control of virtual switches to provide network virtualization and NFV and (2) management and orchestration of existing networks to provide new features and automation. This talk will cover trends in open SDN and cloud networking, with a focus on Boron milestones. In particular, it dives into the architecture across OpenStack and OpenDaylight to enable OpenStack service function chaining support in OpenDaylight.

State of the OpenDaylight Union

Open Networking Summit

Creating responsive and interactive web applications has always been one of my hidden dreams. One of the biggest show stopper has been the communication between server and clients. The rise of websockets now open some space for a brand new kind of applications; but we need a library that makes things 'easy' for us and that is able to fall back on previous solutions when the latest technologies are not available. Suddenly on the ASP.NET scene appears SignalR: a persistence connection abstraction library that helps ASP.NET developers deal with 'real time' client-server communication sceneries.

«Real Time» Web Applications with SignalR in ASP.NET

Alessandro Giorgetti

WSO2Con ASIA 2016: DevOps & Cloud: Lessons & Stories

WSO2

Microservices have transformed the way developers are building and deploying applications in the era of modern cloud infrastructure. Microservices architectures are designed to separate components into discrete functional elements or individual services. Developers benefit from this new model with reduced complexity and increased scalability. Smaller, more granular compute services which can be developed and deployed independently are easier to maintain, repair, and update. Microservices delivers more agile capabilities so software developers can quickly respond to today's changing environments.

Microservices: Breaking Apart the Monolith

Iron.io

signalr

Owen Chen

A brief overview of the significance of API Gateways in microservices architecture by providing Kong as an example. Slide 2: Monolith Vs Microservices Monolith: Pros- Simple to implement Less integration test - easy to test Easy to ship Fast development Cons- Violates Open-Close principle Nightmare when it comes to managing the code Difficult to enhance Bigger artifacts Hard to replace individual components like DB, Logger etc. Microservices- Pros- Easy to manage One reason to change Dynamic scaling Single responsibility Cons- Multiple points of failure Hard to test - rich integration tests required Heterogeneity in infrastructure Slide 3: API Gateway Pattern It is microservices design pattern. An API gateway is a service which is the entry point into the application from the outside world. It’s responsible for request routing, API composition, and other functions, such as authentication. There are a lot of issues when client is talking to multiple components to get the job done. These include multiple proxies at client side, different logic to handle different calls, client needs to know the implementation details of server. A much better approach is for a client to make a single request to what’s known as an API gateway. An API gateway is a service which is the single entry-point for API requests into an application. It’s similar to the Facade pattern from object-oriented design. Like a facade, an API gateway encapsulates the application’s internal architecture and provides an API to its clients. It might also have other responsibilities, such as authentication, monitoring, and rate limiting. These are also termed as BFF - Backend For Frontend Slide 4: API Gateway in Action It acts as a “backend for the frontend”. The clients do not know which services they are talking to. They communicate with a single interface - API Gateway. The gateway resolves the client requests and distributes them to respective services. Slide 7: Kong Architecture Kong is a cloud-native, fast, scalable, and distributed Microservice Abstraction Layer (also known as an API Gateway, API Middleware or in some cases Service Mesh). Made available as an open-source project in 2015, its core values are high performance and extensibility. Actively maintained, Kong is widely used in production at companies ranging from startups to Global 5000 as well as government organizations.

Api gateway in microservices

Kunal Hire

Tendances (20)

Orchestration of Microservices - Google dev fest 2017 Berlin

Digital Transformation through Open Software Defined Infrastructure

Shedding Light on LINE Token Economy You Won't Find in Our White Paper

Real time web with SignalR

Introduction to SignalR

Workshop on CIFS / SMB Protocol Performance Analysis

Zeebe - a Microservice Orchestration Engine

SignalR with ASP.NET MVC 6

The Interoperability Challenge in Telecom and NFS Environments

Micro service architecture

Architecture Sustaining LINE Sticker services

Real-time ASP.NET with SignalR

SignalR for ASP.NET Developers

SignalR

State of the OpenDaylight Union

«Real Time» Web Applications with SignalR in ASP.NET

WSO2Con ASIA 2016: DevOps & Cloud: Lessons & Stories

Microservices: Breaking Apart the Monolith

signalr

Api gateway in microservices

Similaire à [SC London] "Testing Microservices: from Development to Production

Testing microservices is challenging. Dividing a system into components (à la microservices) naturally creates inter-component dependencies, and each service has its own performance and fault-tolerance characteristics that need to be validated during development, the QA process, and continually in production. Attend this session to learn about the theory, techniques, and practices needed to overcome this challenge. You will • Get an introduction to the challenges of testing distributed microservice systems • Learn how to isolate tests within a complex microservice ecosystem • Hear about several tools for automating vulnerability and security scanning for code, dependencies, and deployment artifacts SPEAKERS Abraham Marin-Perez, Developer, Equal Experts Daniel Bryant, Principal Consultant, Big Picture Tech

CodeOne SF 2018: "Testing Java Microservices: From Development to Production"

Daniel Bryant

Testing microservices is challenging. Dividing a system into components (à la microservices) naturally creates inter-component dependencies, and each service has its own performance and fault-tolerance characteristics that need to be validated during development, the QA process, and continually in production. Attend this session to learn about the theory, techniques, and practices needed to overcome this challenge. Join us, and: Get an introduction to the challenges of testing distributed microservice systems Learn how to isolate tests within a complex microservice ecosystem Hear about several tools for automating vulnerability and security scanning for code, dependencies, and deployment artifacts

Devoxx UK 2019: "Testing Java Microservices: From Development to Production

Daniel Bryant

Testing java microservices: from development to production

Abraham Marin-Perez

Testing microservices is challenging. Dividing a system into components (à la microservices) naturally creates inter-component dependencies, and each service has its own performance and fault-tolerance characteristics that need to be validated during development, the QA process, and continually in production. Attend this meetup to learn about the theory, techniques, and practices needed to overcome this challenge. You will: • Get an introduction to the challenges of testing distributed microservice systems • Learn how to isolate tests within a complex microservice ecosystem • Hear about several tools for automating vulnerability and security scanning for code, dependencies, and deployment artifacts

Testing Java Microservices: From Development to Production

Daniel Bryant

Testing microservices is challenging. Dividing a system into components naturally creates inter-service dependencies, and each service has its own performance and fault-tolerance characteristics that need to be validated during development, the QA process, and continually in production. Join Daniel Bryant to learn about the theory, techniques and practices needed to overcome this challenge. Learning Outcomes: – Introduction to the challenges of testing distributed microservice systems – Learn tactics for isolating tests within a complex microservice ecosystem – Whistle stop tour of consumer-driven contract testing and API simulation – Implementing fault-injection testing to validate nonfunctional requirements in development and QA – An introduction and discussion of the need for continually validating microservice systems running in production, both through observability and practices like chaos engineering

deliver:Agile 2019 "Testing Microservices: From Development to Production

Daniel Bryant

Taking your code to production

muayyad alsadi

Some time ago, when refactoring code or adding business logic, my tests failed -> leaving me unsure if I did break something or not. How to write tests, where you can completely change the implementation and verify that it still works without breaking any test? Feels like a utopia? Come and see how to do this with "real" project example! Github project: https://github.com/gmiejski/dvd-rental-tdd-example

Tests immutable when refactoring - SegFault Unconference Cracow 2019

Grzegorz Miejski

Introduce Test Harness for Direct To Consumer Solutions.pdf

Knoldus Inc.

DDD with Behat

Anton Serdyuk

Until recently, major public cloud providers have offered relatively basic toolsets for identifying suspicious activity occurring inside customer accounts that may indicate a compromise. Some organizations have invested significant resources to build their own tools or have leveraged industry vendor offerings to provide this visibility. The reality is, that barrier has meant that a large number of organizations haven't dedicated those resources to this problem and therefore operate without sufficient detection and response capabilities that monitor their cloud accounts for compromise. Amazon Web Services, Google Cloud Platform, and Microsoft Azure have recently launched a new set of native platform threat and anomalous behavior detection services to help their customers better identify and respond to certain issues and activities occurring inside their cloud accounts. From detecting crypto-currency mining to identifying bot-infected systems to alerting on suspicious cloud credential usage to triggering on cloud-specific methods of data exfiltration, these new services aim to make these kinds of detections much easier and simpler to centrally manage. But what new and unique insights do they offer? What configuration is required to achieve the full benefits of these detections? What types of activities are not yet covered? What attack methods and techniques can avoid detection by these systems and still be successful? What practical guidelines can be followed to make the best use of these services in an organization? Follow along as we attempt to answer these questions using practical demonstrations that highlight the real threats facing cloud account owners and how the new threat detection capabilities perform in reducing the risks of operating workloads in the public cloud.

Detecting Malicious Cloud Account Behavior: A Look at the New Native Platform...

Priyanka Aash

Testing strategies in microservices

GeekNightHyderabad

Mobile App Quality Roadmap for DevTest Teams

Perfecto by Perforce

"The twelve-factor app principle is a methodology for building software as a service application and these best practices are designed to enable applications to be built with portability and resilience when deployed to the web. Lagom is a well-known framework for developing microservices. In this knolx session, we would be discussing the twelve-factor app principle with respect to lagom development. "

Twelve Factor App With Lagom

Knoldus Inc.

Keeping IoT stack in quality check - meetup IoT Under Test

Silvair

Not my problem - Delegating responsibility to infrastructure

Yshay Yaacobi

WebRTC Standards & Implementation Q&A - Testing WebRTC 1.0

Amir Zmora

Opticon18: Developer Night

Optimizely

See what pitfalls companies are facing when running Liferay portal. In the previous year, our company has audited 5 real-life projects based on Liferay Portal which are now running in production mode and serving many users. The audits were focused on architecture, infrastructure, technical design and implementation. During the presentation, we will show you common anti-patterns we have found during the audits and their impacts and consequences on the portal.

Liferay portals in real projects

IBACZ

Testing Microservices

Nagarro

An often overlooked aspect of a microservices architecture is its UI. Oracle JavaScript Extension Toolkit (Oracle JET) offers a complete solution to meet this challenge with Web Components. This session demonstrates putting together the building blocks of a micro-front-end architecture using Oracle JET’s Web Components, Node.js, and Docker. It also demonstrates testing components in isolation with Karma/Jasmine and Selenium, and finally—to round things out—a complete pipeline based on Oracle Developer Cloud Service is built to enable CI/CD.

Micro Front Ends for Micro Services using Oracle JET

Vijay Nair

Similaire à [SC London] "Testing Microservices: from Development to Production (20)

CodeOne SF 2018: "Testing Java Microservices: From Development to Production"

Devoxx UK 2019: "Testing Java Microservices: From Development to Production

Testing java microservices: from development to production

Testing Java Microservices: From Development to Production

deliver:Agile 2019 "Testing Microservices: From Development to Production

Taking your code to production

Tests immutable when refactoring - SegFault Unconference Cracow 2019

Introduce Test Harness for Direct To Consumer Solutions.pdf

DDD with Behat

Detecting Malicious Cloud Account Behavior: A Look at the New Native Platform...

Testing strategies in microservices

Mobile App Quality Roadmap for DevTest Teams

Twelve Factor App With Lagom

Keeping IoT stack in quality check - meetup IoT Under Test

Not my problem - Delegating responsibility to infrastructure

WebRTC Standards & Implementation Q&A - Testing WebRTC 1.0

Opticon18: Developer Night

Liferay portals in real projects

Testing Microservices

Micro Front Ends for Micro Services using Oracle JET

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)