-
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
long answer: amp is a full framework including other context-specific components like event loops, web framework, etc. It is too bloated for the usual use case in our community (which is primarily phar plugins for PocketMine-MP). await-generator only provides the basic async executor (which dispatches the generator) plus a few basic context-agnostic synchronization primitives like async iterators, mutex and channels. It does not depend on any runtime (it does not even have a scheduler). furthermore, I am not a fan of the Promise/Generator split in amp, which increases the cognitive complexity of an API. btw, await-generator is not Promise/A+ compliant using the equivalent definitions, because a lack of runtime implies it is unable to satisfy 2.2.4 (execute subsequent operations with clear stack), i.e. exceptions thrown after yielding might end up generating enormous stack traces (await-generator has manual tail recursion optimization to mitigate this). You could always write a framework-specific function that takes in a generator and yields from it after the framework finishes the current stack though.