Skip to content

Document queue/table usage #20

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
kzu merged 1 commit into from
Apr 8, 2025
Merged

Document queue/table usage #20

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 12 additions & 0 deletions readme.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -132,6 +132,18 @@ corresponding access token for it. To get a permanent access token for
use, you'd need to create a [system user](https://business.facebook.com/latest/settings/system_users)
with full control permissions to the WhatsApp Business API (app).

## Scalability and Performance

In order to quickly and efficiently process incoming messages, the library uses
Azure Storage Queues to queue incoming messages from WhatsApp, which provides
a reliable and scalable way to handle incoming messages. It also uses Azure Table Storage
to detect duplicate messages and avoid processing the same message multiple times.

If `QueueServiceClient` and `TableServiceClient` are registered in the DI container
before invoking `UseWhatsApp`, the library will automatically use them. Otherwise,
it will register both services using the `AzureWebJobsStorage` connection string,
therefore sharing storage with the Azure Functions runtime.

## License

We offer this project under a dual licensing model, tailored to the needs
Expand Down