camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Ford (JIRA)" <>
Subject [jira] [Commented] (CAMEL-4400) Consumer Endpoint for AWS SNS Service
Date Sun, 12 Jul 2015 13:08:04 GMT


Mark Ford commented on CAMEL-4400:

in terms of revenue, AWS is on track to grow 49% this year and is accelerating. One could
infer from the revenue that they are gaining in popularity but of course it could be a smaller
number of users spending more each year, I really don't know.

irrespective of whether AWS is popular, I think there have only been a few requests for this
in 4+ years. I would leave it open as a feature request and encourage someone from the community
to do the work. Maybe I'll have some time this summer if nobody gets to it. I've been away
from SNS for a long time but I'm active in other AWS and Camel services.  

> Consumer Endpoint for AWS SNS Service
> -------------------------------------
>                 Key: CAMEL-4400
>                 URL:
>             Project: Camel
>          Issue Type: New Feature
>          Components: camel-aws
>            Reporter: Kai Wähner
>             Fix For: Future
> Contrary to S3 and SQS, Camel only offers a producer endpoint for this AWS service. You
can only create topics and send messages via Camel. The reason is simple: Camel already offers
endpoints for consuming these messages: HTTP, Email and SQS are already available.
> But there is a huge tradeoff: A consumer cannot subscribe to topics using Camel. The
AWS Management Console has to be used.
> The original contribution of camel-sns contained a consumer for easily configuring and
consuming the data from the topic. This was not included in the release.
> The SNS consumer should be added, because otherwise Camel is missing a core feature of
the AWS SNS service.

This message was sent by Atlassian JIRA

View raw message