4 ms·
One approach I’m experimenting with is that all services communicate via a message channel (e.g. NATS or Pub/Sub). By doing this, I can run a service locally b
by devmunchies 5y ago
One approach I’m experimenting with is that all services communicate via a message channel (e.g. NATS or Pub/Sub).
By doing this, I can run a service locally but connect it to the production pubsub server and then see how it effects the system if I publish events to it locally.
I could also subscribe to events and see real production events hitting my local machine.
- __turbobrew__ 5y agoYea that sounds like a nice way to do things. I could see there being security concerns that devs can directly access data streams from their local setup. For places with data controls I could see this being a no-go. I guess you could have an anonymizer which consumes the production pub-sub and then anonymizes the data for consumption by non-prod environments.