blocks|key|495527|text|选项1:配置SQS以根据类型触发不同的lambda函数|type|blockquote|depth|inlineStyleRanges|entityRanges|data|495528|在type被lambda消耗之前，您不可能知道它的情况。所以这次是不可能的。|unstyled|offset|length|style|CODE|495529|选项2:配置一个lambda函数，它可以检查类型，然后根据其类型调用其他lambda函数|495530|是的，这是第一个选择的“可能”方式。但它可能会花费“更多”取决于你的使用。当您在批处理模式下使用sqs时，您必须通过进行多个检查来调用多个lambda。|495531|选项3:为每个lambda创建单独的队列。通过将消息添加到适当的队列来控制哪个lambda处理消息。|495532|在我看来，这可能是最好的选择。您可以为每个队列配置不同的DLQ，根据业务规则设置不同的批处理大小，不需要额外的lambda来增加“复杂性”。|495533|entityMap^0|0|1|4|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|T|8|@$E|U|F|V|G|H]]|9|@]|A|$]]|$1|I|3|J|5|6|7|W|8|@]|9|@]|A|$]]|$1|K|3|L|5|D|7|X|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|Y|8|@]|9|@]|A|$]]|$1|O|3|P|5|D|7|Z|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|D|7|10|8|@]|9|@]|A|$]]]|R|$]]

<blockquote>
 Option 1: Configure SQS to trigger a different lambda function depending on the type
</blockquote>

You can't know about the <code>type</code> until it is consumed by the lambda. So this one is not possible.

<blockquote>
 Option 2: Configure one lambda function which can check type and then call the other lambda functions depending on its type
</blockquote>

Yes it is the "possible" way of first option. but it may cost "more" depending on your usage. When you consume the sqs in batch mode, then you have to invoke multiple lambdas by making multiple checks. 

<blockquote>
 Option 3: Create separate queues for each lambda. Control which lambda processes the message by adding the message to the appropriate queue.
</blockquote>

In my opinion, this could be the best option. You can configure different DLQ for each queue, set different batch size depending on your business rules, no need for extra lambda to increase "complexity".

blocks|key|495565|text|您应该而不是将多个Lambda函数配置为单个SQS队列的触发器。这是因为SQS中的消息将传递给任何一个使用者，当该消息由该使用者处理时，它将不会对其他人可见。因此，您将无法决定哪种“类型”的消息属于哪个函数，因此选项1是无效的。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|495566|备选案文2和3都应正常工作。如果您不期望将许多消息传递到您的队列中，因此不必担心Lambda标度，我将选择选项2。还要注意，可以在一个批处理中将多条消息传递给Lambda触发器，因此您必须相应地实现您的逻辑。|495567|如果您期望收到大量的消息，那么选项3将更适合。|495568|entityMap|0|LINK|mutability|MUTABLE|url|https://docs.aws.amazon.com/lambda/latest/dg/with-sqs.html#events-sqs-scaling^0|3|3|0|14|8|0|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@$9|S|A|T|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|U|8|@]|D|@$9|V|A|W|1|X]]|E|$]]|$1|H|3|I|5|6|7|Y|8|@]|D|@]|E|$]]|$1|J|3|-4|5|6|7|Z|8|@]|D|@]|E|$]]]|K|$L|$5|M|N|O|E|$P|Q]]]]

You should not configure multiple Lambda functions as triggers for a single SQS queue. This is because the message in SQS will be delivered to any one consumer and while this message is being processed by that consumer, it would not be visible to others. Thus, you wouldn't be able to decide which "type" of message goes to which function, so Option 1 is invalid.

Both Option 2 and 3 should work fine. I would select Option 2 if you do not expect that many messages to be delivered to your queue, thus not having to worry about <a href="https://docs.aws.amazon.com/lambda/latest/dg/with-sqs.html#events-sqs-scaling" rel="noreferrer">Lambda scaling</a>. Also note, multiple messages can be delivered in a single batch to the Lambda trigger, so you would have to implement your logic accordingly.

If you're expecting a large number of messages, then Option 3 would be better suited.

blocks|key|528764|text|您可能应该发布到一个SNS主题，并让多个lambda订阅该主题，并根据他们的意愿处理事件。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|528765|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

You should probably post to an SNS topic and have multiple lambdas subscribe to the topic and process the event as they wish.

blocks|key|528821|text|这里的最佳选择是根本不直接将消息发送到队列。您可以使用SNS或EventBridge作为消息的目的地。然后，您应该为每种类型的消息都有一个队列。然后，您可以将每个队列订阅到源(SNS或EventBridge)，并且只接收对该队列有意义的消息。使用EventBridge，您可以对整个有效负载进行相当数量的筛选。对于SNS，您需要将类型添加到属性中，以便它可以用于筛选。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|528822|​|528823|📷|atomic|offset|length|528824|528825|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://developer.qcloudimg.com/http-save/yehe-900000/689a02dd88adb711194f2fa5ef6942af.png|imageAlt^0|0|0|0|1|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|T|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|U|8|@]|9|@$G|V|H|W|1|X]]|A|$]]|$1|I|3|C|5|6|7|Y|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|Q|R|-4]]]]

Your best option here would be to not send the messages directly to the queue at all. You can use either SNS or EventBridge as the destination for the message. Then you should have one queue for each type of message. You can then subscribe each queue to the source (SNS or EventBridge) and only receive the messages that make sense for that queue. With EventBridge you can do a fair amount of filtering on the entire payload. For SNS you'd need to add the type to the attributes so it can be used for filtering.
<a href="https://i.stack.imgur.com/zJBK6.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/zJBK6.png" alt="enter image description here" /></a>

blocks|key|1478835|text|使用不同订阅过滤器订阅SNS的多个lambda在这里看起来是最好的选择。好处。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1478836|最低限度的管理。|ordered-list-item|1478837|订阅者(Lambdas)在收到消息后不必担心过滤，每个lambda将根据订阅筛选器中给定的条件获得特定的消息进行处理。|1478838|SNS将负责基于订阅过滤器的路由部分。|1478839|唯一需要注意的额外部分是使消息头中的类型字段可用，以应用于订阅筛选器。|1478840|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$]]|$1|E|3|F|5|D|7|O|8|@]|9|@]|A|$]]|$1|G|3|H|5|D|7|P|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|Q|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|R|8|@]|9|@]|A|$]]]|L|$]]

Multiple lambda subscribing to SNS with different subscription filters looks best option here.
Benefits.
<ol>
<li>Minimum infra to manage.</li>
<li>Subscribers (Lambdas) do not have to worry about the filtering after receiving the message, each lambda will get specific message for processing based on the condition given in subscription filters.</li>
<li>SNS will take care of routing part based on the subscription filter.</li>
</ol>
Only additional piece you have to take care is make the type field available in Message Headers to apply to the subscription filters.

I'm not sure if I understand AWS Lambda - SQS triggers correctly. Can I possibly configure it in such a way that one SQS queue can trigger different lambda functions depending on the message body or a message attribute?

My use case: I have three different lambda functions (processCricket, processFootball, processTennis) each of which perform a unique function. I have a single queue (processGame) which receives messages. Each message on the queue has a attribute "type" which is either "Cricket", "Football" or "Tennis". Can I invoke a different lambda function depending on the "type" on the message?

Option 1: Configure SQS to trigger a different lambda function depending on the type (Not sure if I can do this)

Option 2: Configure one lambda function which can check type and then call the other lambda functions depending on its type

Option 3: Create separate queues for each lambda. Control which lambda processes the message by adding the message to the appropriate queue.

Triggering multiple lambda functions from one SQS trigger

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我不确定是否正确理解AWS Lambda - SQS触发器。我可以将其配置为这样一种方式:一个SQS队列可以根据消息体或消息属性触发不同的lambda函数吗？My用例：我有三个不同的lambda函数(processCricket、processFootball、processTennis)，每个函数都执行一个唯一的函数...

问从一个SQS触发器触发多个lambda函数
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问从一个SQS触发器触发多个lambda函数EN