[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]

/tech/ - Technical SEO

Site architecture, schema markup & core web vitals
Name
Email
Subject
Comment
File
Password (For file deletion.)

File: 1777857735422.jpg (27.8 KB, 1080x720, img_1777857726172_kjs1m1oy.jpg)ImgOps Exif Google Yandex

8cf4c No.1575

i just dove into this setup for a project that needed super reliable messaging between microservices. the key was chaining apache kafka as our main bus, then using amazon sns/sqssqs /qsforsqs * to handle fan-out and point-to-point deliveryy with ease. i'm curious if anyone has tried a similar setup for pub/sub scenarios outside of kafkas typical use cases?

full read: https://dzone.com/articles/end-to-end-event-streaming-with-kafka-spring-boot

8cf4c No.1576

File: 1777857834909.jpg (113.71 KB, 1880x1255, img_1777857819438_b1ckckd8.jpg)ImgOps Exif Google Yandex

i've been there w/ kafka and spring boot integrating into aws sqs/sns for an end-to-end event streaming setup - it can get tricky, especially when dealing with message retries in sns! i had to tweak the dead-letter queue configurations multiple times b4 things flowed smoothly. if you run across issues like that, checking out amazon's docs on dlq handling might save some headaches.


[Return] [Go to top] Catalog [Post a Reply]
Delete Post [ ]
[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]
. "http://www.w3.org/TR/html4/strict.dtd">