|
| 1 | +title: Event Streams |
| 2 | +category: page |
| 3 | +slug: event-streams |
| 4 | +sortorder: 1002 |
| 5 | +toc: False |
| 6 | +sidebartitle: Event Streams |
| 7 | +meta: An event stream is a log of one or more events. |
| 8 | + |
| 9 | + |
| 10 | +Event streams are a log of one or more "things that happen", which are |
| 11 | +usually referred to as events. Event streams are |
| 12 | +conceptually focused around things that happen rather than objects, |
| 13 | +which are the typical storage unit for |
| 14 | +[relational databases](/databases.html). |
| 15 | + |
| 16 | +Apache Kafka and Gazette are a popular open source implementations of event |
| 17 | +streams. Amazon Web Services' Kinesis and |
| 18 | +[Azure Event-Hubs](https://azure.microsoft.com/en-us/services/event-hubs/) |
| 19 | +are proprietary hosted implementations. |
| 20 | + |
| 21 | + |
| 22 | +## How are event streams stored? |
| 23 | +Some applications, such as aggregating millions of sensors, or thousands |
| 24 | +of constantly streaming cameras, throw off large amounts of data. It's |
| 25 | +difficult to process those large volumes of data in traditional data stores, |
| 26 | +so event streams are built off of a simpler data structure: logs. |
| 27 | + |
| 28 | +Logs are ordered sequences of events and they typically have less constraints |
| 29 | +than a database. Logs can handle the high throughput writes needed to keep |
| 30 | +up with the constant flood of data from the source of an event stream. |
| 31 | + |
| 32 | + |
| 33 | +## Event stream resources |
| 34 | +* [What is Apache Kafka?](https://www.youtube.com/watch?v=FKgi3n-FyNU) sounds |
| 35 | + like it just focuses on Kafka but it actually covers the fundamental |
| 36 | + concepts behind event streams and how they fit into |
| 37 | + [microservices](/microservices.html) architectures. |
| 38 | + |
| 39 | + |
0 commit comments