...
Nwave’s APIs are based on three technologies
HTTP
AMQP
GraphQL
Type | Technology | API | Advantages | Disadvantages | Typical applications |
---|---|---|---|---|---|
Push | HTTP |
|
|
| |
AMQP |
|
|
| ||
Pull | HTTP |
|
|
Generates a lot of traffic and excessive server load when pulled frequently
|
|
| |||||
|
|
| |||
Push & Pull | GraphQL |
|
|
|
HTTP Caller
Diagram:
HTTP Caller API is one of the simplest types of API but provides little functionality to users. This API sends HTTP requests to your configured endpoints. HTTP requests are formed based on raw sensor events. During downtime, Nwave’s cloud will make at up to 100 retries for each request which can lead to high traffic spikes.
...
Nwave provides two types of parking data through RabbitMQ:
RabbitMQ RTA (Real-Time Availability) gives you enriched parking occupancy information about every parking event. This lets you receive comprehensive application occupancy data for unmarked bays (when one car can occupy more than one sensor). | RabbitMQ Parking Session Logging saves your time and resources on developing and maintaining the code for storing occupancy history. RabbitMQ session is logging data which is already enriched by Nwave cloud (for marked and unmarked bays): session start, end time, session restoration in case of partial message loss and SDI data. |
More details about these API can be found here:RabbitMQ.
...