Feat: ACK Request #6
Description
Feature Request
Currently in this implementation, the user has to implement a strategy manually in case there's an intermittent issue in handling the request. It might be nice to have something like Kafka and Google Cloud Pub/Sub that has ability to ack a message manually if configured.
Use case example
When the end-result involves saving into database, and there's a network partition error.
Others
Open for discussion, this project is still very new. This issue isn't rigid. Any contribution to the project vision is highly appreciated.