You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Our current billing / credit management system was quickly hacked together in order to release Airbyte Cloud. It lacks features desired by our product team (e.g. adding/deducting credits for a user in a UI, automatic credit expiry, generating usage reports), and uses up valuable engineering time to maintain and improve. The bottom line is that Airbyte is not a billing company, and we shouldn’t try to be.
In order to reduce the amount of changes we are making in the first iteration of this solution, we will keep the existing CreditProcessingCronJob and continue to write CreditConsumptionRecords to the database for each attempt, but it will be changed to stop tracking and managing additions and deductions to credit balance, and instead just report usage to the billing vendor. This way we will still maintain our own record of credit consumption which will be helpful in validating that our billing vendor integration is working correctly, and it also maintains the existing setup of keeping credit consumption tracking completely isolated from the job lifecycle.
Describe the alternative you’ve considered or used
Tell us about the problem you're trying to solve
Our current billing / credit management system was quickly hacked together in order to release Airbyte Cloud. It lacks features desired by our product team (e.g. adding/deducting credits for a user in a UI, automatic credit expiry, generating usage reports), and uses up valuable engineering time to maintain and improve. The bottom line is that Airbyte is not a billing company, and we shouldn’t try to be.
See tech spec for more details: https://docs.google.com/document/d/1WLr7Leaj5Iyy5bBEjr1TGhNL8HhSB_evbM_psEwKyAI/edit#
Describe the solution you’d like
In order to reduce the amount of changes we are making in the first iteration of this solution, we will keep the existing CreditProcessingCronJob and continue to write CreditConsumptionRecords to the database for each attempt, but it will be changed to stop tracking and managing additions and deductions to credit balance, and instead just report usage to the billing vendor. This way we will still maintain our own record of credit consumption which will be helpful in validating that our billing vendor integration is working correctly, and it also maintains the existing setup of keeping credit consumption tracking completely isolated from the job lifecycle.
Describe the alternative you’ve considered or used
See tech spec
Execution
Additional context
Are you willing to submit a PR?