- Home
- Skills
- Giuseppe Trisciuoglio
- Developer Kit
- Aws Sdk Java V2 Messaging
aws-sdk-java-v2-messaging_skill
- Python
99
GitHub Stars
1
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill giuseppe-trisciuoglio/developer-kit --skill aws-sdk-java-v2-messaging- SKILL.md11.0 KB
Overview
This skill provides ready-to-use AWS messaging patterns implemented with the AWS SDK for Java 2.x, covering SQS queues and SNS topics. It includes client setup, queue/topic management, message send/receive, FIFO and DLQ support, subscription wiring, and Spring Boot integration examples. Use it to speed up production-grade message-driven and pub/sub architectures with clear best practices.
How this skill works
The skill supplies code examples and patterns for creating SQS queues and SNS topics, sending and receiving messages, configuring FIFO behavior and dead-letter queues, and subscribing endpoints (SQS, Lambda, email, SMS). It shows client configuration for the SDK, long-polling and batch operations for SQS, publish/subscribe flows for SNS, and Spring Boot service wiring for seamless integration. It also covers testing approaches using LocalStack or Testcontainers and recommendations for monitoring and retries.
When to use it
- Building queue-based processing with Amazon SQS (standard or FIFO)
- Publishing events and notifications via Amazon SNS with multiple subscribers
- Implementing DLQs and retry strategies for robust message handling
- Integrating AWS messaging into Spring Boot microservices
- Creating SNS-to-SQS subscriptions for durable pub/sub pipelines
- Testing messaging flows locally with LocalStack or Testcontainers
Best practices
- Use long polling (waitTimeSeconds) to reduce empty receives and API costs
- Batch send/receive operations to improve throughput and lower call volume
- Make processing idempotent to handle duplicate deliveries and retries
- Configure appropriate visibility timeouts and set up DLQs for failures
- Apply SNS filter policies and message attributes to route notifications
- Keep region consistency and secure access with IAM and encryption
Example use cases
- Order processing: publish orders to SNS and fan out to multiple SQS queues for different microservices
- Async task processing: push jobs to an SQS queue, consume with workers using long polling and batch deletes
- Notification system: publish alerts to an SNS topic with email, SMS, and SQS subscribers
- FIFO workflows: enforce ordering and deduplication for transactional message streams
- Error handling: route failed messages to DLQs for later inspection and replay
FAQ
SQS and SNS payloads should be kept under 256 KB; use S3 for larger payloads and pass references in messages.
How do I test messaging locally?
Use LocalStack or Testcontainers to run SQS/SNS emulation for integration tests and CI pipelines.