broadway/sensitive-data

helpers for handling sensitive data with Broadway

Maintainers

Details

github.com/broadway/broadway-sensitive-data

Source

Issues

Installs: 16 612

Dependents: 0

Suggesters: 0

Security: 0

Stars: 6

Watchers: 4

Forks: 1

Open Issues: 2

0.4.0 2020-03-07 13:16 UTC

Requires

Requires (Dev)

MIT 9afaad986de83f74e12398c3a3947749a07045f1

  • othillo <othillo.woop@othillo.nl>

This package is auto-updated.

Last update: 2024-12-01 00:11:34 UTC

README

Helpers for handling sensitive data with Broadway.

build status

Installation

$ composer require broadway/sensitive-data

About

In an Event Sourced environment you may have to deal with sensitive (e.g. personal) data ending up in your event stream. You could encrypt your event stream or remove sensitive data from your event stream after a certain amount or time (upcasting). Or you could choose not to store sensitive data in you event stream altogether. That's where this project helps out.

Imagine the use case where a customer wants to pay an order with a credit card and you're not allowed to store the credit card number.

A PayWithCreditCardCommand (with credit card number) should lead to a PaymentWithCreditCardRequestedEvent (without the credit card number) but the Processor that handles the event does need to know the credit card number.

This project introduces a SensitiveDataManager which can be injected into a CommandHandler to capture the sensitive data from the command and make it available to the SensitiveDataProcessor hereby bypassing the event store.

Pros:

  • sensitive data is not stored in your event stream
  • no need for encryption or upcasting of your events

Cons:

  • handling of sensitive data can only be done once per request

Example

A detailed example with a test case can be found in the examples/ directory.

License

This project is licensed under the MIT License - see the LICENSE file for details