🔥 Tech Blips #23.8
In this technology newsletter: Team API, EventCatalog, Tekton and Dapr.
I'm pleased to bring you the latest Tech Blips, the monthly technology newsletter for CTOs, tech leads, software architects and software engineers - in short, for all technology enthusiasts!
What teams are you currently interacting with? What are the modes and purposes of these interactions? Just like software systems, teams also have an "API". The Team API is based on some of the ideas in the popular book Team Topologies. Each team in the organization can use the Team API template to describe its API. It is worth taking a look at it.
Event-Driven Architectures (EDAs) are becoming more popular, but the ecosystem still needs improvement. Tools like EventStorming and EventModeling help us design events together, but the information can get lost over time. EventCatalog is a promising tool to help people understand, document, and discover their EDAs.
Standardizing CI/CD tooling and processes across vendors, languages, and deployment environments is a challenge. Tekton addresses this challenge by providing a flexible and extensible framework for creating CI/CD systems. Tekton abstracts the underlying implementation, so you can focus on building the pipelines that you need. This makes it a valuable tool for teams that want to standardize their CI/CD processes and improve their efficiency.
Connectivity between microservices is a complex topic, with many common challenges. Dapr can help you address these common challenges by providing APIs that abstract away the complexity of common tasks that developers face when building distributed applications.
I hope you enjoy this technology newsletter.
Kind regards
A Team API is a description of how a team can be interacted with. It can be useful to define a Team API for each team in an organization, as it can help to improve clarity of purpose and collaboration.
By defining a Team API, other teams and individuals can understand how to work with the team and what they can expect from them. This can help to improve communication and collaboration, and ultimately lead to better outcomes for the organization.
The Team API technique is based on the ideas in the book Team Topologies by Matthew Skelton and Manuel Pais. In the book, the authors argue that teams should be designed to be loosely coupled and highly cohesive. A team API can help to achieve this by providing a clear and concise way for teams to interact with each other.
The template for describing a Team API can be found on GitHub. The template is designed to be easy to use and can be customized to fit the specific needs of each team.
If you are interested in learning more about team APIs, I recommend reading the book Team Topologies. You can also find more information on the teamtopologies.org website.
TeamTopologiesEvent-Driven Architectures (EDA) have been around for awhile now, but it’s becoming more accessible with things like serverless offerings it is now easier now more than ever to get started.
Event Architectures are proving they can give some great benefits but parts of the ecosystem still need to be improved.
Over the past decade we have seen tools like EventStorming and EventModeling take off. These practises encourage us to talk and design our Events together.
Shared understanding and context goes into the creation of our Events, Bounded Context and Services but unfortunately this information get's lost over time.
EventCatalog is designed to help people understand, document and discover their Event Architectures.
EventCatalog is a tool that can help to address the challenges of managing event-driven architectures. EventCatalog provides a central repository for all of your events, their relationships, and their documentation. This can help you to keep track of your events and make it easier to understand your architecture.
EventCatalog also provides a number of other features that can help you to manage your EDA, such as:
- Event discovery: EventCatalog can help you to discover all of the events in your architecture.
- Event lineage: EventCatalog can track the lineage of events, so you can see how they are related to each other.
If you are considering adopting an EDA, EventCatalog is a tool that you should consider. It can help you to manage your EDA and get the most out of it.
boyney123Tekton is an open-source framework for creating CI/CD systems. It is powerful and flexible, and it can be used to build, test, and deploy across cloud providers and on-premise systems.
Tekton standardizes CI/CD tooling and processes across vendors, languages, and deployment environments. This makes it easy to create CI/CD pipelines that are consistent and reusable.
Tekton also works well with other popular CI/CD tools, such as Jenkins, Jenkins X, Skaffold, and Knative. This makes it easy to integrate Tekton into your existing CI/CD infrastructure.
Tekton is a powerful tool that can help you to improve the efficiency and reliability of your CI/CD pipelines. If you are looking for a flexible and scalable CI/CD framework, Tekton is a great option.
tektoncd
The Distributed Application Runtime (Dapr) provides APIs that simplify microservice connectivity. Whether your communication pattern is service to service invocation or pub/sub messaging, Dapr helps you write resilient and secured microservices.
By letting Dapr’s sidecar take care of the complex challenges such as service discovery, message broker integration, encryption, observability, and secret management, you can focus on business logic and keep your code simple.
Dapr provides you with APIs that abstract away the complexity of common challenges developers encounter regularly when building distributed applications. These API building blocks can be leveraged as the need arises - use one, several or all to develop your application faster and deliver your solution on time.
dapr
Comments ()