Skip to content
This repository was archived by the owner on Dec 9, 2024. It is now read-only.

Conversation

@mthenw
Copy link
Contributor

@mthenw mthenw commented Aug 15, 2017

No description provided.

@mthenw mthenw requested a review from brianneisler August 15, 2017 22:24
The Event Gateway combines both API Gateway and Pub/Sub functionality into a single event-driven experience. It's dataflow for event-driven, serverless architectures. It routes Events (data) to Functions (serverless compute).

## Quick Start
The Event Gateway is a layer-7 proxy and realtime dataflow engine, intended for use with Functions-as-a-Service on AWS, Azure, Google & IBM.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This sounds cool, but I have no idea what "layer-7 proxy and realtime dataflow engine" really means! I do like how you mentioned "event driven" and "serverless architectures" before, as those are terms we're trying to enforce. Thoughts on this @worldsoup ?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's why I split the first paragraph into two sections. The first one is high level, the second in technical explanation for devs. it's important to provide that info for people that want to know on technical level what it is. I'm gonna merge it. Feel free to make any changes in the readme.

@mthenw mthenw merged commit 1656ecc into master Aug 16, 2017
@mthenw mthenw deleted the readme branch August 16, 2017 07:55
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants