Skip to content

Commit

Permalink
revised to includ @c0c0n3 feedback
Browse files Browse the repository at this point in the history
  • Loading branch information
chicco785 committed Jan 21, 2021
1 parent 85d99f5 commit 6a4ce07
Showing 1 changed file with 9 additions and 4 deletions.
13 changes: 9 additions & 4 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -20,12 +20,17 @@ It currently also experimentally supports the injection of
a backward compatible way with NGSI-v2 API. I.e. you can retrieve NGSI-LD stored data via NGSI v2
API and retrieve data will be describe following NGSI v2 format.

QuantumLeap is not a [real time](https://en.wikipedia.org/wiki/Real-time_computing) API,
its purpose is to process notifications received from the Context Broker and
to create temporal records for them. In general, the whole FIWARE stack, being
based on a micro-service architecture, cannot be regarded as real time
QuantumLeap is not a [real time](https://en.wikipedia.org/wiki/Real-time_computing)
API, its purpose is to process notifications received from the Context Broker
and to create temporal records for them. In general, the whole FIWARE stack,
being based on a micro-service architecture, cannot be regarded as real time
in case you have requirements on guaranteed delivery in a given amount of time.

However, even though hard real time may not be FIWARE's forte, in our experience
a properly tuned FIWARE stack can perform extremely well and
handle very demanding IoT workloads without a glitch - you just need to
configure your infrastructure to handle that :)

Want to know more? Refer to the [docs](https://quantumleap.readthedocs.io/en/latest/)
or checkout the Extra Resources below.

Expand Down

0 comments on commit 6a4ce07

Please sign in to comment.