In the Cloud-native K8S environment, the logging architecture almost always assumes that all needed logs are sent to the stdout. It works as a unified source of logs where different tools read them, re-organize if needed, and route to the destinations like Analytics Dashboards etc.

Hazelcast Diagnostics are very useful when troubleshooting the performance and stability issues but currently, it

There are two static analyzers in an LLVM project:

• https://clang.llvm.org/extra/clang-tidy/
• https://clang-analyzer.llvm.org/

Would be nice to check tarantool source code with these analyzers, fix warnings and errors and add it in Tarantool CI.

The leadership changes section made me nervous because it looks like there is some reliance on the nodes perceived Raft status (which may not be the Raft status). I traced the code and indeed on proposal, the node's local Raft status is determined to decide whether that node is the leader or not. During network partitions however, a node ma

RediSQL support multiple statements in the same "EXEC", hence it is possible and correct to do something like:

REDISQL.EXEC DB "INSERT INTO foo VALUES(1,2,3); INSERT INTO bar VALUES(2,3,4);" 

Which is quite convenient when mixed with BEGIN, COMMIT and ABORT instruction.

One problem is that all the statements are first prepared all together, and then executed, all together.

This

I am a little confused on how and when to use memfs, unionfs, linkfs, patchFs, patchRequire, jest-plugin-fs etc.

There are a lot of pieces to make a great vehicle but the instructions on how assembling them together are not well organized. A lot of documentation is sparse across different repos and issues on those repos. Outdated info in old issues and changes in the state of the

We need to implement integration/unit tests for internal/transport package.

ObservableMap can be built on top of Map. All the documentation needed to built this type is available on the documentation site.

I do not have any concrete requirements on how the APIs would look like but Observable types should make it simple to attach listeners and react to changes in the database.

Another option

First thank you for your work.

I wanted to use this fake implementation of Mongo for GeoSpatial queries also.
But there is missing operators in file QueryOperator.java

When I try to do near queries I got the following mistake because $nearSphere is missing:

Tracking issue

Currently, the Go client does not support Hazelcast's paging predicates.

Native promises have increased performance in Node.js 10+, so bluebird doesn't have a significant advantage anymore. Also, bluebird maintainers advice to switch to native promises, when possible. We should experiment with the switch, do some benchmarks and decide whether we should switch now.

If we do the switch, we don't need #524 at all.