|
1 | 1 | [](https://travis-ci.org/IBM/openwhisk-data-processing-cloudant) |
2 | 2 |
|
3 | 3 | # Cloudant data processing with OpenWhisk |
4 | | -This project shows the power of serverless, event-driven architectures to execute code in response to database change events from Cloudant, thus extracting highly scalable and highly efficient analytics from both technologies. |
| 4 | +This project shows how serverless, event-driven architectures can be used to execute code in response to database change events from Cloudant, thus extracting scalable and efficient analytics from both technologies. |
5 | 5 |
|
6 | 6 | This application shows you two OpenWhisk actions (written in JavaScript) that write and read text and image data to Cloudant, a hosted Apache CouchDB service. The scenario demonstrates how actions can work with data services and execute logic in response to database changes. |
7 | 7 |
|
@@ -37,6 +37,8 @@ Log into Bluemix, provision a [Cloudant database instance](https://console.ng.bl |
37 | 37 |
|
38 | 38 | Copy `template.local.env` to a new file named `local.env` and update the `CLOUDANT_INSTANCE`, `CLOUDANT_DATABASE`, `CLOUDANT_USERNAME`, and `CLOUDANT_PASSWORD` for your instance. |
39 | 39 |
|
| 40 | +> **Note**: The Cloudant service credentials and connectivity details can be automatically bound to the OpenWhisk context with `wsk package refresh`, as they are in the [simpler version of this app](https://github.com/IBM/openwhisk-cloudant-trigger). However, since we are writing more than a simple JSON object back to Cloudant, we will use the Cloudant NPM client directly with the credentials, rather than through the Cloudant packaged write action. |
| 41 | + |
40 | 42 | # 2. Create OpenWhisk actions, triggers, and rules |
41 | 43 | `deploy.sh` is a convenience script reads the environment variables from `local.env` and creates the OpenWhisk actions, triggers, and rules on your behalf. Later you will run these commands yourself. |
42 | 44 |
|
|
0 commit comments