Amazon sns slack9/15/2023 ![]() In my taste, you should go with a minialistic approach and try to avoid either of them if you can, especially if your architecture does not fall nicely into event sourcing. Kafka nowadays is much more than a distributed message broker. ![]() But also note that Redis is not a pure message broker (at time of writing) but more of a general purpose in-memory key-value store. I have a good past experience in terms of manageability/devops of the above options with Kafka and Redis, not so much with RabbitMQ. Do you need Pub/Sub or Push/Pull? Is queuing of messages enough or would you need querying or filtering of messages before consumption? Also, someone would have to manage these brokers (unless using managed, cloud provider based solution), automate their deployment, someone would need to take care of backups, clustering if needed, disaster recovery, etc. Why are you considering event-sourcing architecture using Message Brokers such as the above? Won't a simple REST service based arch suffice? Read about CQRS and the problems it entails (state vs command impedance for example). Import base from "./common/sns.I think something is missing here and you should consider answering it to yourself. Send a test event to validate your setup.Optional - Configure Send text as Slack mrkdwn.Optional - Configure Metadata Event Payload.Optional - Configure Metadata Event Type.Optional - Configure Include link to workflow.Configure the Send a Custom Message action. ![]() ![]() When you configure and deploy the workflow, it will run on Pipedream's servers 24x7 for free. This integration creates a workflow with a AWS trigger and Slack action. ![]()
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |