@benjamenpyle @awsdevelopers Hey @benjamenpyle loved the article! I couldn't DM but the patient entity example looks to be the same as the address entity in the article
@boyney123@ghohpe We have steam filters enabled on dynamodb and have a modified timestamp on the root aggregate so that when a separate entity is saved it modifies the timestamp so the stream is notified
@thdxr@samgoodwin89@arktypeio I do the same, we define the events in the application and they get pushed to the registry when an event is published to ensure we keep our events backwards compatible
@thdxr@samgoodwin89@arktypeio Not sure if you've looked at this but we use JSON schema to define our events and can validate at runtime with ajv library. We publish our events to Kafka for cross cloud communication but it also works with eventbridge https://t.co/fMrxr6aAfU
@MrLarrieu @rmoff@bbejeck@apachekafka@awscloud@ksqlDB AWS would use their own code that is abstracted away as a consumer and would invoke your lambda, so all you need to worry about is your function being invoked, this section talks about how it scales for the function https://t.co/wM5MHDgoWE
Hello, world! Our first book has been published and released. Please check out A Gentle Introduction to @apachekafka by Mitch Seymour: https://t.co/GFsP2OjMnx