![](\"https://img.shields.io/badge/-Join%20us%20on%20Slack-green?logo=slack&logoColor=34d28B&labelColor=150d11&color=34d28B&logoWidth=18&link=https%3A%2F%2Fpipedream.com%2Fcommunity&link=https%3A%2F%2Fpipedream.com%2Fcommunity)](https://pipedream.com/community\"){kind=icon}
\n ![](\"https://img.shields.io/twitter/follow/pipedream?label=Follow%20%40pipedream&style=social\")
\n\n
![](\"https://i.ibb.co/m0bBsSL/deploy-clean.png\")
\n\nor:\n\n[Install the Pipedream CLI](https://docs.pipedream.com/cli/install/), then deploy the Hacker News \"new stories by keyword\" component from the registry:\n\n```bash\npd deploy hacker_news-new-stories-by-keyword\n```\n\nOr, deploy the \"new comments by keyword\" component from the registry:\n\n```bash\npd deploy hacker_news-new-stories-by-keyword\n```\n\nSubmit your keyword and deploy your component.\n\n**You have turned the Hacker News API into a real time event stream!**\n\n![](\"https://i.ibb.co/cbTZ0T4/Screen-Shot-2020-04-10-at-1-11-31-PM.png\")
\n\n## Docs\n\n- [Why use components?](#why-use-components)\n- [Component API](COMPONENT-API.md)\n- [Event Sources](https://docs.pipedream.com/event-sources/)\n- [HTTP Event Sources Quickstart](https://github.com/PipedreamHQ/pipedream/tree/master/interfaces/http)\n- [REST API Reference](https://docs.pipedream.com/api/rest/)\n- [SSE Reference](https://docs.pipedream.com/api/sse/)\n- [CLI Reference](https://docs.pipedream.com/cli/reference/)\n- [Workflows](https://docs.pipedream.com/workflows/)\n\n## Why use components?\n\nComponents are similar to serverless functions, like those offered by AWS Lambda. You don't have to manage the server that runs the code — components are hosted on Pipedream infrastructure — and they run on specific events like HTTP requests and timers.\n\nBut we believe components are simpler to learn, write, and maintain for many use cases. They let you focus more on the code, and less on the configuration of the function and its associated services:\n\n- You can configure an HTTP server [via props](/COMPONENT-API.md#http), and can use a [built-in key-value store](/COMPONENT-API.md#db) to manage state. Components creates the HTTP interface for you on deploy, and the key-value store comes for free: there's no need to create these resources manually.\n- Components are meant to be reusable. They can accept input via [props](/COMPONENT-API.md#props), which a user sets on deploy.\n- Components are self-contained. Their name, version, props, and code are all defined in one file. This makes components easy to understand at a glance, and easy to fork and modify.\n\nThis is also an early release. [The component API](/COMPONENT-API.md) will improve over time. **Right now, we're looking for any and all [feedback](https://pipedream.com/community)**. Tell us what you're building, what works and what doesn't, and anything you think would improve the product.\n\n## Pricing\n\nPipedream is currently free, subject to the [limits noted below](#limits). Paid tiers for higher volumes are coming soon.\n\nIf you exceed any of these limits, please [reach out](https://docs.pipedream.com/support/).\n\n## Limits\n\nComponents are subject to the [limits of the Pipedream platform](https://docs.pipedream.com/limits/).\n\n## Found a Bug? Have a Feature to suggest?\n\nAny bugs or feature requests for specific components can be raised in this repo as new Github issues or pull requests.\n\nPipedream also operates [a roadmap](https://github.com/PipedreamHQ/roadmap) to solicit feature requests for the Pipedream platform at large (the [pipedream.com UI](https://pipedream.com), [workflows](https://docs.pipedream.com/workflows/), the CLI, etc).\n\nYou can always [reach out to our team](https://docs.pipedream.com/support/) - we're happy to discuss feedback or help fix a bug.\n","readmeFilename":"readme.md"}