| copyright | lastupdated | ||
|---|---|---|---|
|
2017-06-16 |
{:shortdesc: .shortdesc} {:new_window: target="_blank"} {:codeblock: .codeblock} {:pre: .pre} {:screen: .screen} {:tip: .tip}
{: #getting-started}
The Getting Started guides are designed to guide you through the basics of developing a ready-for-production end-to-end IoT prototype system with {{site.data.keyword.iot_short_notm}} and are written for developers who are new to working with {{site.data.keyword.iot_short_notm}}. {:shortdesc}
Each guide provides a step-by-step process that quickly leads you to a deployed and running solution that demonstrates one or more {{site.data.keyword.iot_short_notm}} features.
{: #using-guides} In each guide, you get at least one GitHub-sourced sample that is coded according to {{site.data.keyword.iot_short_notm}} best practices. These samples can be scaled, secured, integrated with systems, and can generally fit right into your devOps development and build processes.
The technically inclined can expand on the quick solution by adapting the sample code to their own environment or by complementing the quick solution with hardware examples that more closely simulates what you might encounter in your production environment. The guides provide additional links to task-relevant documentation, API docs, client libraries (SDKs), instructional videos, and other training material.
You can follow the guides in order, where the first guide provides a foundation upon which the following guides build. If you want to jump around and follow your own path through the series, each guide also comes with a list of requirements. For example, if you already have a {{site.data.keyword.iot_short_notm}} organization set up, you can jump straight into guides number two and three and start exploring rules, actions, and a sample monitoring app. The requirements tell you the format of the device data that these guides require, and you can set up your own environment accordingly. {: tip}
{: #list-of-guides}
The following guides are available:
| Guide | Description |
|---|---|
| 1. Connecting a conveyor belt device | Get started by installing an {{site.data.keyword.iot_short_notm}} organization and then connect a sample GitHub-sourced conveyor belt simulation application, or if you prefer something more physical, your own Raspberry-Pi-based conveyor belt simulator. Then set up some basic {{site.data.keyword.iot_short_notm}} dashboard cards to visualize and monitor your device data. |
| 2. Using basic real-time rules and actions | With one or more devices connected to your {{site.data.keyword.iot_short_notm}} organization and sending data, you can now set up business rules and trigger actions to, for example, notify a plant operator if the speed of his conveyor belt drops below a certain threshold. |
| 3. Monitoring your device data | Expand on the built-in {{site.data.keyword.iot_short_notm}} device monitoring dashboards by connecting a Node.js or widget-library-based monitoring app to see conveyor belt data in real time. |
| 4. Simulating a large number of devices | Expand on the simple device simulation by adding large numbers of device simulators to your environment to test drive the analytics and monitoring from the previous guides in a more realistic, multi-device environment. Important: The application requires 512 MB of memory, which is more than is allocated by default and which also exceeds the amount available to free trial accounts, which must first be upgraded to a Subscription or Pay-As-You-Go account. |