Why does `broadway_sqs` not support writing to SQS?

sigmaml · June 5, 2026, 4:29pm

Hello —

I am trying to use Broadway for the first time. I see that broadway_sqs is a “producer” that enables pulling messages from SQS and processing them.

My processing pipeline involves certain operations on the pulled messages and then enqueuing them into a second SQS queue (to be processed by a different stage/consumer).

Do I need to use a different library such as ex_aws_sqs to write to SQS? What are the reasons why this — in my experience — common case seems not enabled by Broadway? Am I missing something?

Thanks.

al2o3cr · June 5, 2026, 6:10pm

FWIW, that library’s already used by broadway_sqs (line 30):

github.com/elixir-broadway/broadway_sqs

mix.exs

main


      
          
          def application do
            [
              extra_applications: [:logger]
            ]
          end
          
          defp deps do
            [
              {:broadway, "~> 1.0"},
              {:ex_aws_sqs, "~> 3.2.1 or ~> 3.3"},
              {:nimble_options, "~> 0.3.7 or ~> 0.4 or ~> 1.0"},
              {:telemetry, "~> 0.4.3 or ~> 1.0"},
              {:saxy, "~> 1.1"},
              {:hackney, "~> 1.9", only: [:dev, :test]},
              {:bypass, "~> 2.1.0", only: :test},
              {:ex_doc, ">= 0.19.0", only: :docs}
            ]
          end
          
          defp docs do

sigmaml · June 6, 2026, 3:53am

Noted, thanks.

I didn’t — apparently — phrase my question properly.

The way Broadway has producer, processors, and batchers, it doesn’t seem to have an optional enqueuer that could send the successfully processed items to a downstream queue (SQS/Kafka/RabbitMQ/…).

What are the reasons behind this design decision?

Thanks.

krasenyp · June 6, 2026, 7:33am

The reasons are that “Broadway is a concurrent, multi-stage tool for building data ingestion and data processing pipelines”.

felix-starman · June 7, 2026, 4:00pm

It’s meant to be an implementation detail left up to the user of the library.

Not everyone needs to send things back to a separate queuing system, and making a consumer that puts things back onto an external queue is fairly straightforward, so the library doesn’t bake it in as a fundamental concept

sigmaml · June 7, 2026, 11:39pm

Noted, thanks!