Download as PDF, PPTX
![@danielbryantuk
Telepresence: Local-to-Remote bridge
$ telepresence intercept dataprocessingnodeservice --port 3000
37
Using deployment dataprocessingnodeservice
intercepted
State : ACTIVE
Destination : 127.0.0.1:3000
Intercepting: HTTP requests that match all of:
header("x-telepresence-intercept-id") ~= regexp ("76a1e848-1829-74x-1138-e3294c1e9119:dataprocessingnodeservice")
Preview URL : https://[random-subdomain].preview.edgestack.me
www.youtube.com/watch?v=W_a3aErN3NU](https://image.slidesharecdn.com/craftconf-microservicetestingtechniques-mocksvsservicevirtualizationvsremocaltools-230522061539-36ad302e/85/CraftConf-2023-Microservice-Testing-Techniques-Mocks-vs-Service-Virtualization-vs-Remocal-Tools-37-320.jpg)
Uploaded byDaniel Bryant
CraftConf 2023 "Microservice Testing Techniques: Mocks vs Service Virtualization vs Remocal Tools
The document discusses various microservice testing techniques including mocks, service virtualization, and remote-to-local (remocal) tools, emphasizing their respective advantages and disadvantages. It highlights the challenges of testing with microservices, especially when using Kubernetes, and suggests the use of Telepresence for efficient development. Choosing the appropriate testing strategy is crucial to mitigate the complexities encountered with multiple services in a system.
More Related Content
Similar to CraftConf 2023 "Microservice Testing Techniques: Mocks vs Service Virtualization vs Remocal Tools
![[DW Webinar] Effective Management of APIs and the Edge when Adopting Kubernetes](https://cdn.slidesharecdn.com/ss_thumbnails/webinareffectivemanagementofapisandtheedgewhenadoptingkubernetes-200312104752-thumbnail.jpg?width=640&height=640&fit=bounds)
CraftConf 2023 "Microservice Testing Techniques: Mocks vs Service Virtualization vs Remocal Tools
- 1. Microservice Testing Techniques: Mocksvs Service Virtualization vs Remocal Tools Daniel Bryant @danielbryantuk
- 2. @danielbryantuk tl;dr 2 • The innerdev/test loop can be painful with microservices & Kubernetes • The pain increases as the number of services within your system increase • You have options with +/- : mocks, service virtualisation, remocal tools • Telepresence enables remote-to-local “remocal” development • Choose your dev/test approach wisely!
- 3. @danielbryantuk Testing Microservices: Whatto use, when 3 Mocks Service virtualization Remocal Unit tests ✅ Integration tests ✅ ✅ Component tests ✅ ✅ ✅ End-to-end tests ✅ ✅ Poking around an existing API ✅ Building an API ✅ ✅
- 4.
- 5.
- 6. @danielbryantuk Inner and outerdev loops 6 Hat tip to Mitch Denny (now 404): https://mitchdenny.com/the-inner-loop/ http://jorgemoral.es/posts/2020_03_17-develop_apps… Local: “You’ll pry localhost from my cold dead hands!" Remote: “CI/CD/envs as a Service”
- 7. @danielbryantuk You are buildingcontainerised microservices, right? 7
- 8. @danielbryantuk SOA: There’s justmore stu ff (and dependencies) 8
- 9. @danielbryantuk So, let’s runeverything locally… 9
- 10. @danielbryantuk tl;dr 10 “My laptop onlyhas 16GB RAM and you’re asking it to run Kubernetes and a JVM and a database???”
- 11. @danielbryantuk Okay, let’s runeverything remotely… 11
- 12. @danielbryantuk Inner and outerdev loops with K8s can be the same 12 • Write code • Build container • Push to registry • Deploy to cluster • Test And can be …. SLOW.
- 13.
- 14. @danielbryantuk tl;dr 14 But you wanta really fast inner loop (no docker build/push) …
- 15. @danielbryantuk tl;dr 15 And youwant to use your own tools.
- 16. @danielbryantuk tl;dr 16 And you wantto avoid the “works on my machine” production vs local dev debacle
- 17.
- 18. @danielbryantuk Testing Strategies ina Microservice Architecture 18 https://martinfowler.com/articles/microservice-testing/
- 19. @danielbryantuk What are youroptions? 19 • Mocks • Mockito, PowerMock(ito), EasyMock, JMockit • Service virtualisation • TestContainers, LocalStack, (Embedded Datastore/middleware?) • Hoverfly, WireMock, Mountebank • Remocal tooling • Devspace, Okteto • Telepresence, Gefyra
- 20.
- 21. @danielbryantuk Mocks 21 • Good • Idiomatic(familiar language constructs etc) • Quick and cheap • Can help build your mental model (TDD-like) • Bad • Implicit assumptions coded in (“the three realities conundrum”) • Di ff icult to keep up to date and share/coordinate • Needs a test runner
- 22. @danielbryantuk Testing Microservices: Whatto use, when 22 Mocks Unit tests ✅ Integration tests ✅ Component tests ✅ End-to-end tests Poking around an existing API Building an API ✅
- 23.
- 24.
- 25.
- 26. @danielbryantuk Service virtualisation 26 • Good •More realistic than mocks (can be the “real thing”, albeit resource constrained) • Enables (wire-level) deterministic test of failure scenarios • Easy to use large(r) amounts of data • Bad • Slower than mocks to initialise • Can be tricky to configure • Challenging to keep up to date and share (unless you use dedicated tooling/SaaS)
- 27. @danielbryantuk Testing Microservices: Whatto use, when 27 Service virtualization Unit tests Integration tests ✅ Component tests ✅ End-to-end tests ✅ Poking around an existing API Building an API ✅
- 28.
- 29. @danielbryantuk Remocal tooling 29 • Good •Enables testing against (and poking of) the real thing • Data sets can be large scale (as resources can be scaled on remote cluster) • No need to build mental model of dependency (both good and bad!) • Bad • Need a solid network connection • Mutating remote shared state can be an issue • Lack of language bindings
- 30. @danielbryantuk Testing Microservices: Whatto use, when 30 Remocal Unit tests Integration tests Component tests ✅ End-to-end tests ✅ Poking around an existing API ✅ Building an API
- 31.
- 32. @danielbryantuk What is Telepresence 32 •“Fancy Kubernetes VPN for development” • “kubectl port-forward on steroids” • “kubectl proxy all-the-things” • A network bridge between your laptop and the Kubernetes cluster
- 33.
- 34.
- 35.
- 36. @danielbryantuk Telepresence: Local-to-Remote bridge 36 telepresenceconnect • Open a tunnel to the remote cluster; exposes “in-cluster” services/network/DNS telepresence intercept my-service —port 3000 • Re-routes (intercepts) tra ff ic to my-service in the remote cluster to my local machine telepresence login & telepresence intercept • Create preview URL to isolate and share results of the intercept
- 37. @danielbryantuk Telepresence: Local-to-Remote bridge $telepresence intercept dataprocessingnodeservice --port 3000 37 Using deployment dataprocessingnodeservice intercepted State : ACTIVE Destination : 127.0.0.1:3000 Intercepting: HTTP requests that match all of: header("x-telepresence-intercept-id") ~= regexp ("76a1e848-1829-74x-1138-e3294c1e9119:dataprocessingnodeservice") Preview URL : https://[random-subdomain].preview.edgestack.me www.youtube.com/watch?v=W_a3aErN3NU
- 38. @danielbryantuk Headers for selectiveintercepts 38
- 39. Docker Desktop Extensionfor Telepresence 39 getambassador.io/testing-with-telepresence-and-docker
- 40.
- 41.
- 42. @danielbryantuk Testing Microservices: Whatto use, when 42 Mocks Service virtualization Remocal Unit tests ✅ Integration tests ✅ ✅ Component tests ✅ ✅ ✅ End-to-end tests ✅ ✅ Poking around an existing API ✅ Building an API ✅ ✅
- 43. @danielbryantuk Conclusion 43 • The innerdev/test loop can be painful with microservices & Kubernetes • The pain increases as the number of services within your system increase • You have options with +/- : mocks, service virtualisation, remocal tools • Telepresence enables remote-to-local “remocal” development • Choose your dev/test approach wisely!
- 44. @danielbryantuk Thank you! Questions? 44 getambassador.io/products/telepresence getambassador.io/testing-with-telepresence-and-docker EasyDebugging of Spring Boot Microservices Running on Kubernetes AL Developer O ff ice Hours db@datawire.io / @danielbryantuk