Bâtissez votre pont vers le cloud en temps réel avec la plateforme Confluent 7.0 et Cluster Linking | Lire le blog

Testing Event Driven Architectures: How to Broker the Complexity

Quality Matters … and as event-driven architectures (EDA) become increasingly popular in the microservices space, ensuring the delivery and performance of your EDA increases in importance. But while it’s powerful architecture, it does come with its challenges, especially from a testing perspective. For example, most organizations are not reliant on Kafka alone, but a multitude of interconnected APIs like REST, GraphQL and gRPC. One of the questions that arise from this challenge: How do you build end-to-end tests when the APIs are completely different technologies—without relying on fragile scripts? In our talk, we’ll tackle this question and many more when it comes to the testing of Apache Kafka endpoints and your services architecture. We’ll cover what makes testing in EDA difficult; technologies that can help you; and how we at SmartBear are thinking about these testing problems and, most importantly, how we are trying to solve for them.

Présentateurs

Frank Kilcommins

Frank has over 15 years’ experience in the technology industry, with his roles spanning from software engineering to enterprise architecture. His mission is to inspire, engage with and support the API community and SmartBear customers across the end to end API Development Lifecycle and Management space. Prior to joining SmartBear, his most recent roles have been focused on API led Digital Transformations and architecture modernization within multi-national enterprises.

Temil Sanchez

Temil Sanchez is a product owner who is currently responsible for driving product roadmap and optimizing each component of the development lifecycle. For the past 10 years Temil has had a focus on creating best API practices in testing, development and design via different roles in QA, support, solutions engineering and product. With the varying roles he brings a great deal of perspective to the API lifecycle and its future