help me understand the following conversation:

NAME_1
  5:38 PM
@NAME_2
 I have some points to validate if you can help us when you have time please
5:38
Repository: RetailSucces - Shopify
 - Will have the objects necessary to match with shopify flow
 - Response and Request model too
 Integration API - SynchronizeOrdersShopifyToBless
 - Will have the configuration of the AWS SNS and AWS SQS
 - Will have the configuration of the dead letter queue
 - Will have a worker to process the messages of the SQS.
 - Will have the configuration to notifiy the NAME_3 when a message arrive.
 - Will have endpoints to process when the webhook of shopify update inventory or completed an order.
 - Will call libraries of NAME_4 to create an order after process a message of SQS for example.
 - Will have enpoints to update NAME_4 too? like when NAME_4 updated the inventory, will call some endpoint here(Integration API) to update the inventory of shopify?







NAME_2
  5:50 PM
So the integration API will send a message to the SNS topic. It should not need to know about SQS  or the handler. I would expect the API to be in a separate repo from the handler that makes the API call as those are separate deliverables.
SNS-SQS-handler and DLQ connections are managed in terraform via an infrastructure repo.
There will be a dedicated SNS->SQS-Handler process to upload inventory changes to Shopify via the RetailSuccess.Shopify.Client that will be triggered by the existing API endpoint(s) that get called when the retailer makes a change in app or on the management portal.
So like this:
Repository: RetailSuccess.Shopify
 - Will have the objects necessary to match with Shopify flow
 - Response and Request model too
Repository: RetailSuccess.Integration.Shopify  ( coming soon to a Github near you )
 Integration API for both inventory and order messages from Shopify
 - Will have the configuration of the AWS SNS for both orders and inventory
Repository: RetailSuccess.Shopify.OrderReceived.Lambda ( coming soon to a Github near you )
- Will have a worker to process the messages of the SQS.
- Will have the configuration to notify the NAME_3 when a message arrive.
- Will call libraries of NAME_4 to create an order after processing a message of SQS for example.
Repository: RetailSuccess.Shopify.InventoryChangeReceived.Lambda ( coming soon to a Github near you )
- Will have a worker to process the messages of the SQS.
- Will call libraries of NAME_4 to alter NAME_4 inventory after processing a message of SQS for example.
5:51
I'm about to hop in