Experience Report

I am currently ingesting a large continuous streaming data set. The most recent data is the most important data. The oldest - either by policy or by least importance needs to be aged-off. Today, we use Neo4J Community Edition. We perform a query to find nodes/relationships older than a specific date and then delete them.

Note: Feature requests are judged based on user

https://cloud.google.com/deployment-manager/docs/

I think everything in setup.sh can be expressed as a deployment in YAML, then refreshing everything would just be a single gcloud invocation. That might also make it easier to schedule a periodic refresh to ensure up-to-date VM images.

Document what happens when target has multiple addresses.

How often do we resolve? What if the IP changes? What if there's multiple addresses? Do we ping all of them, or just the first one?

The problem is that CULT at the moment does not understand that some instructions only modify flags, for example, and it generates a sequence of instructions that has no dependency on each other in such case.

This should be a window where developers can see the routes/components that loaded on the page. It can be toggled on/off and possibly also dragged around the page in case its default position covers page content the dev needs to see. Should not be included in production builds by default.

Add more example tests to src/test/examples

Also maybe move this folder to a location that will be automatically picked up by an IDE (i.e. intellij)