Skip to content
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.

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

How to treat changing cost? #759

Open
tenjaa opened this issue Jun 16, 2023 · 0 comments
Open

How to treat changing cost? #759

tenjaa opened this issue Jun 16, 2023 · 0 comments

Comments

@tenjaa
Copy link

tenjaa commented Jun 16, 2023

What is the problem?
The cost of a service change from time to time. Savings by scale, inflations, ...
The spec of the catalog says

Periodically, a Platform MAY re-query the service catalog endpoint for a Service Broker to see if there are any changes to the list of services.

I feel like this is not precise enough for billing.

Imagine I, it is 15.6.2023. As a broker, I decided to increase my prices by 10% from 1.7.2023 on.

  • Do I push this change now because the platform only queries it from time to time?
  • Do I push it on 1.7. hoping that the platform queries my catalog daily?
  • Do I push it on 2.7. because then the billing for June should be done?
  • How do I inform my users about the change in advance?

Who does this affect?
I would say mainly platforms but also brokers.

Do you have any proposed solutions?
Right now I could think of two options:

  • Clarify when the cost information are updated. Either by saying daily, each 2nd day of the month or never/must be triggered manually in the platform somehow.
  • Make cost information versioned with a date. So I can say "until 30.6. it is x EUR" and "from 1.7. it is x*1.1 EUR"
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Inbox
Development

No branches or pull requests

1 participant