Reactor · part of brewlytics
ReactorSkip the schedule. React to your data.
Every feed, sensor and system streams in. The moment something matters, the right brewlytics model runs.
The everyday problem
Data never stops arriving. A schedule only checks in now and then.
The reading that matters hides in the noise. A sensor that goes silent looks like a quiet day. By the next scheduled check, the moment has passed.
Clock or stream
Tasks follow the clock. Reactor follows your data.
Over a day, every 'wait until the next run' adds up. With Reactor there's nothing to add up.
From anywhere
One HTTP call. You're streaming.
Any system that can make a web request can publish to a topic. Reactor checks the message against the topic's schema, and your flows react in the same breath.
Prefer not to write code? brewlytics connectors bring in the feeds you already run, and people and models post too. Every source lands on a topic.
curl -X POST \
"$BREWLYTICS/api/reactor/topics/vessel-tracks" \
-H "Authorization: Bearer $TOKEN" \
-d '{"vessel": "Corran Star",
"lat": 36.84, "lon": -75.97,
"speed_kn": 14.2}'How it works
Topic. Flow. Model. That's the whole idea.
Messages land on a topic. A flow decides which ones matter. Your brewlytics model runs for each one, with the message as its input.
You build a flow by dragging boxes onto a canvas and joining them.
Flows in action
Four ways to react. Pick the one that fits.
A flow is the rule that decides when your model runs.
Filter
Only what matters reaches your model.
New imagery pours in. Only the clear frames reach the analyst queue; the rest go to the archive, out of the way. One message can follow several paths, each to its own model.
Match
Pair events from two places, the instant they meet.
A vessel track crosses into the area of interest, and the analysis is already running. Run once each time they meet, on every update while close, or now and then — your choice.
Batch
500 scans. One run.
Warehouse scanners fire all shift long. A Batch flow collects them and runs your shift summary once per 500, not 500 times. You choose when a batch closes — after 500 messages or 60 seconds, whichever comes first — and your model receives the whole batch as one list.
Gone quiet
Silence is a signal. Reactor hears it.
Pump 7 checks in every couple of minutes, until it doesn't. A Gone quiet flow notices and opens a maintenance ticket after 10 minutes — one alert per silence, no repeat alarms. Choose any wait from 1 minute to 24 hours, and add an all-clear when it reports again.
A flow, end to end
One satellite pass. Three sources. Zero waiting.
A satellite's footprint sweeps the area. Its imagery lands, gets checked for cloud cover, and is matched against vessel broadcasts and RF detections. A ship that stopped broadcasting gets flagged, the model posts to the Watch floor, and that post starts the next flow.
Live topics
Every message, and what it set off.
A topic is a live channel for one kind of update. Its chat room shows each update the moment it lands, who sent it, and every run it started. Models post their results right back into the conversation. Something went wrong? Run it again from the same spot.
Safe and dependable
Built to be trusted with real work.
One message, one run.
Built so a message never starts the same run twice by accident.
Calm under heavy traffic.
When thousands of messages arrive at once, they wait their turn instead of swamping your models.
Picks up where it left off.
If a server stops, another takes over from the last message that was finished.
Problems stay contained.
If one path of a flow has trouble, only that path stops. Restart just that one.
Your access, respected.
A flow uses only what the person who switched it on is allowed to use.
Everything on the record.
Each message shows who sent it, what ran, and how it went, with a link to the run.
Schemas, as strict as you like.
Off, Warn or Reject. A message that doesn't fit gets a one-line reason.
Who sees, who sends, who sets the rules.
Can see only · Can send and see · Owners.
A flow runs as the person who switched it on.
If they lose access to the topic, the flow stops.
Scale
Built for heavy traffic.
Many servers share the work. A rush waits its turn. Paths never block each other.
1,000+
messages gathered into a single run by one Batch
100 by default
64+
runs of one flow going at the same time
4 by default
100,000+
devices one Gone quiet path can watch at once
10,000 by default
Starting points, not ceilings. Each is a setting an administrator raises to fit the job. Not speed-test results.
Each flow goes to the least busy server, and another takes over if one stops.
Messages wait in line — kept 7 days by default, up to 90 — and each flow works through them at its own pace.
Each path of a flow has its own queue, so a busy path never holds up the rest.
Get started
Up and running in three steps.
Create a topic.
Give it a name, choose structured fields or plain text, and add a schema if you like.
Build a flow.
Drag in your topic, add a Filter, Match, Batch or Gone quiet, and pick the model to run.
Switch it on.
Watch results arrive in the chat room, and share the topic with your team.
Already on brewlytics? Ask your administrator to turn Reactor on for your team.