This repository has been archived by the owner on Apr 24, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 10
/
index.html
47 lines (46 loc) · 3.12 KB
/
index.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
---
title: "Homepage"
---
{% include header.html %}
<div class="page-header page-header--homepage">
<div class="inner-container">
<h1>The <strong>stream database</strong> written from the ground up for <strong>event sourcing</strong>.</h1>
<span class="c2a">
<a href="/docs/getting-started" class="btn btn--primary">Get started with Event Store</a>
<a href="/support" class="btn btn--secondary">Get support</a>
</span>
</div>
</div>
<div class="feature-section">
<div class="inner-container">
<ul class="feature-list">
<li class="feature-list__item">
<h2><img src="/images/eventstore.svg" alt="Event sourcing icon"> Event Sourcing</h2>
<p>Event Store stores your data as a series of immutable events over time, making it easy to build event-sourced applications. <a href="/docs/event-sourcing-basics">Learn more about event sourcing in our documentation.</a></p>
</li>
<li class="feature-list__item">
<h2><img src="/images/opensource.svg" alt="Open source icon"> Open Source</h2>
<p>Event Store is licensed under a 3-clause BSD license, whether it runs on a single node or as a high availability cluster. Commercial support services are available. Source code is available on <a href="https://github.com/EventStore/EventStore">GitHub</a></p>
</li>
<li class="feature-list__item">
<h2><img src="/images/ha.svg" alt="High availability icon"> High Availability</h2>
<p>Event Store can run as a cluster of nodes containing the same data, which remains available for writes provided at least half the nodes are alive and connected.</p>
</li>
</ul>
<ul class="feature-list">
<li class="feature-list__item">
<h2><img src="/images/clients.svg" alt="Client interfaces icon"> Client Interfaces</h2>
<p>Event Store has a native HTTP interface based on the AtomPub protocol which is plenty fast enough for the majority of use cases. For high-performance use, there are native drivers for .NET, Akka and Erlang.</p>
</li>
<li class="feature-list__item">
<h2><img src="/images/projections.svg" alt="Projections icon"> Projections</h2>
<p>Projections allow you to react to events as they are written, and to create new events when interesting combinations occur. You can use the same model for writing temporal correlation queries that run over historical data and on into the future.</p>
</li>
<li class="feature-list__item">
<h2><img src="/images/performance.svg" alt="Performance icon"> Great Performance</h2>
<p>Whilst performance depends on configuration and use patterns, we’ve benchmarked Event Store at around 15,000 writes per second and 50,000 reads per second!</p>
</li>
</ul>
</div>
</div>
{% include footer.html %}