- Newest
- Most votes
- Most comments
I agree with you - splitting data sources (DynamoDB and IoT registry) with AppSync and a Lambda function is not necessarily an anti-pattern, but it can add complexity. Potential Performance Impact.
Alternative Solution Options:
1/ AWS IoT Core Thing Groups
Leverage AWS IoT Core Thing Groups to categorize devices by county (attribute).
Store telemetry readings directly in DynamoDB with a foreign key referencing the Thing Group (county).
Use AppSync resolvers to directly query DynamoDB based on county (Thing Group) and filter telemetry readings for the specific device ID.
Cons : Requires additional configuration and management of Thing Groups.
2/ Or Maybe
Combine Thing Groups for coarse-grained filtering by county.
Use GSIs(Global Secondary Indexes) within DynamoDB for efficient retrieval of specific device telemetry data.
Remember, there's no one-size-fits-all solution.
Evaluate your specific needs and choose the approach that offers the best balance between simplicity, performance, and cost.
Relevant content
- asked 2 years ago
- Accepted Answerasked a year ago
- Accepted Answerasked 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 4 months ago
- AWS OFFICIALUpdated 10 months ago
- AWS OFFICIALUpdated 2 years ago