这是一个很好的问题,我认为有几种方法可以解决这个问题。这里最困难的部分是,您将找到一种方法来提出“哪些订阅对此位置的事件感兴趣”这个问题。这是一种可能的前进道路。
以下假设这些架构部分:
// Whatever custom object has a location
type Post {
id: ID!
title: String
location: Location
}
input PublishPostInput {
id: ID!
title: String
location: Location
subscriptionID: ID
}
type PublishPostOutput {
id: ID!
title: String
location: Location
subscriptionID: ID
}
type Location {
lat: Float,
lon: Float
}
input LocationInput {
lat: Float,
lon: Float
}
# A custom type to hold custom tracked subscription information
# for location discover
type OpenSubscription {
subscriptionID: ID!
location: Location
timestamp: String!
}
type OpenSubscriptionConnection {
items: [OpenSubscription]
nextToken: String
}
type Query {
# Query elasticsearch index for relevant subscriptions
openSubscriptionsNear(location: LocationInput, distance: String): OpenSubscriptionConnection
}
type Mutation {
# This mutation uses a local resolver (e.g. a resolver with a None data source) and simply returns the input as is.
publishPostToSubscription(input: PublishPostInput): PublishPostOutput
}
type Subscription {
# Anytime someone passes an object with the same subscriptionID to the "publishPostToSubscription" mutation field, get updated.
listenToSubscription(subscriptionID: ID!): PublishPostOutput
@aws_subscribe(mutations:["publishPostToSubscription"])
}
假设您使用 DynamoDB 作为主要事实来源,请设置一个调用“PublishIfInRange”lambda 函数的 DynamoDB 流。 “PublishIfInRange”函数看起来像这样
// event - { location: { lat, lon }, id, title, ... }
function lambdaHandler(event) {
const relevantSubscriptions = await callGraphql(`
query GetSubscriptions($location: LocationInput) {
openSubscriptionsNear(location:$location, distance: "10 miles") {
subscriptionID
}
}
`, { variables: { location: event.location }})
for (const subscription of relevantSubscriptions) {
callGraphql(`
mutation PublishToSubscription($subID: ID!, $obj: PublishPostInput) {
publishPostToSubscription(input: $obj) {
id
title
location { lat lon }
subscriptionID
}
}
`, { variables: { input: { ...subscription, ...event }}})
}
}
您需要维护一个按位置索引的订阅注册表。一种方法是让您的客户端应用程序调用一个突变,该突变创建一个具有位置和订阅 ID 的订阅对象(例如,mutation { makeSubscription(loc: $loc) { ... } } 假设您使用 $util.autoId() 在解析器中生成订阅 ID)。获得订阅 ID 后,您可以通过 graphql 进行订阅调用,并将订阅 ID 作为参数传入(例如subscription { listenToSubscription(subscriptionID: "my-id") { id title location { lat lon } } })。当您进行上述订阅调用时,AppSync 会创建一个主题并授权当前用户订阅该主题。主题对于被调用的订阅字段和传递给订阅字段的参数集是唯一的。也就是说,主题只接收对象
现在,无论何时创建对象,记录都会通过 DynamoDB 流转到 lambda 函数。 lambda 函数在 elasticsearch 中查询该对象附近的所有开放订阅,然后将记录发布到每个开放订阅。
我相信这应该可以让您走得更远,但如果您有数百万用户处于紧张状态,您可能会遇到扩展问题。希望这会有所帮助