Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

remove videos and images #4

Closed
wants to merge 2 commits into from
Closed
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 0 additions & 13 deletions website/docs/about.md
Original file line number Diff line number Diff line change
Expand Up @@ -8,19 +8,6 @@ hide_title: false

Bento is a declarative data streaming service that solves a wide range of data engineering problems with simple, chained, stateless [processing steps][docs.processors]. It implements transaction based resiliency with back pressure, so when connecting to at-least-once sources and sinks it's able to guarantee at-least-once delivery without needing to persist messages during transit.

import ReactPlayer from 'react-player/youtube';

<div className='container margin-vert--lg'>
<div className='row row--no-gutters'>
<ReactPlayer
className='col'
height='300px'
url='https://www.youtube.com/embed/88DSzCFV4Ng'
controls={true}
/>
</div>
</div>

It's [simple to deploy][docs.guides.getting_started], comes with a wide range of [connectors](#components), and is totally data agnostic, making it easy to drop into your existing infrastructure. Bento has functionality that overlaps with integration frameworks, log aggregators and ETL workflow engines, and can therefore be used to complement these traditional data engineering tools or act as a simpler alternative.

Bento is ready to commit to this relationship, are you?
Expand Down
15 changes: 1 addition & 14 deletions website/src/pages/index.tsx
Original file line number Diff line number Diff line change
Expand Up @@ -185,7 +185,6 @@ output:
const features = [
{
title: 'Takes Care of the Dull Stuff',
imageUrl: 'img/Blobboring.svg',
description: (
<>
<p>
Expand All @@ -199,7 +198,6 @@ const features = [
},
{
title: 'Well Connected',
imageUrl: 'img/Blobborg.svg',
description: (
<>
<p>
Expand All @@ -211,22 +209,12 @@ const features = [
</>
),
},
{
description: (
<ReactPlayer
className={classnames('col col-6 padding--lg')}
url='https://youtu.be/uvbp2LCmQMY'
controls={true}
/>
),
},
{
title: 'Reliable and Operationally Simple',
imageUrl: 'img/Blobscales.svg',
description: (
<>
<p>
Delivery guarantees <a href="https://youtu.be/QmpBOCvY8mY">can be a dodgy subject</a>. Bento processes and acknowledges messages using an in-process transaction model with no need for any disk persisted state, so when connecting to at-least-once sources and sinks it's able to guarantee at-least-once delivery even in the event of crashes, disk corruption, or other unexpected server faults.
Delivery guarantees can be a dodgy subject. Bento processes and acknowledges messages using an in-process transaction model with no need for any disk persisted state, so when connecting to at-least-once sources and sinks it's able to guarantee at-least-once delivery even in the event of crashes, disk corruption, or other unexpected server faults.
</p>
<p>
This behaviour is the default and free of caveats, which also makes deploying and scaling Bento much simpler. However, simplicity doesn't negate the need for observability, so it also exposes <a href="/docs/components/metrics/about">metrics</a> and <a href="/docs/components/tracers/about">tracing</a> events to targets of your choice.
Expand All @@ -236,7 +224,6 @@ const features = [
},
{
title: 'Extendable',
imageUrl: 'img/Blobextended.svg',
description: (
<>
<p>
Expand Down
Loading