Skip to content

Commit 9bf220c

Browse files
committed
working on new page for event streams
1 parent 409d0dc commit 9bf220c

File tree

3 files changed

+62
-0
lines changed

3 files changed

+62
-0
lines changed

content/pages/04-web-development/15-web-design.markdown

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -83,6 +83,11 @@ this short list as my absolute favorites that help developers become
8383
design principles for building user experiences. Highly recommended even
8484
if just to see how the information is presented.
8585

86+
* [Building your color palette](https://refactoringui.com/previews/building-your-color-palette/)
87+
explains why color pickers are not useful for most user interfaces
88+
and how you should actually go about selecting your color palette
89+
for a real world application.
90+
8691
* [How I Work with Color](https://medium.com/@JustinMezzell/how-i-work-with-color-8439c98ae5ed)
8792
is a fantastic article from a professional designer on how he thinks
8893
about color and uses it for certain effects in his designs.
Lines changed: 39 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,39 @@
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+
Lines changed: 18 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,18 @@
1+
<h3>What topic do you want to learn next?</h3>
2+
<div class="row">
3+
<div class="c4">
4+
<div class="well select-next">
5+
{% include "choices/buttons/databases.html" %}
6+
</div>
7+
</div>
8+
<div class="c4">
9+
<div class="well select-next">
10+
{% include "choices/buttons/application-dependencies.html" %}
11+
</div>
12+
</div>
13+
<div class="c4">
14+
<div class="well select-next">
15+
{% include "choices/buttons/development-environments.html" %}
16+
</div>
17+
</div>
18+
</div>

0 commit comments

Comments
 (0)