Polyglot Architecture is a feature of microservices that allows each microservice to be built using a different technology stack. This approach provides developers the freedom to select the best tools for the job and allows them to be more creative with their solutions. However, like with any powerful tool, it can have negative consequences if it isn't used properly. CHAPTERS.
From vehicle communication to predictive maintenance, real-time ingestion, analysis, and control has become an increasingly important characteristic of the machines we use in everyday life.
The Branch by Abstraction Pattern is a method of trunk-based development. Rather than modifying the code in a separate branch, and merging the results when finished, the idea is to make modifications in the main branch. An abstraction layer is used to ""branch"" the code along an old and new path. This approach has some key advantages, especially when decomposing a monolith.
Lucia Cerchie explains what an Apache Kafka® cluster is, and why it's unique. Learn how Kafka supports speed, scalability, and durability through its cluster structure.
The Strangler or Strangler Fig Pattern is a process for decomposing a monolith into microservices. It allows rapid delivery of business value while reducing risk. This video introduces the pattern and outlines how it can be used to decompose a monolith.
Data ownership is a critical feature of microservices. Without it, many of the benefits vanish. In this video, you'll learn how to implement data ownership in your own microservices.
Over the last few years, DISH Wireless has turned to AWS partners like Confluent to build an entirely new type of telecommunication infrastructure—a cloud-native network built to empower developers. Discover how data streaming allows DISH Wireless to: Deliver data products that turn network data into business value for customers Harness massive volumes of data to facilitate the future of app communications Seamlessly connect apps and devices across hybrid cloud environments.
Autonomous microservices are more robust and scalable. By avoiding synchronous dependencies, they avoid potential bottlenecks and failures. Learn key principles in this video.