That is how most toll systems work. You load up a balance on the card $10/$20 and it deducts every time you cross a checkpoint.
The difference between this and a micropayment platform would be the fees. In the toll system, the fees are paid once. With a micropayment platform, the fees would be per transaction.
There can be a "self hosted" version of such a platform that say each content-provider can host but I am not sure it will work out against the cost of maintaining it includes much more than just hosting (securty, auditing, refunds, taxes etc).
Scaling is only half of it. There is a lot more to Jira than just CRUD over a few entities. It's trying to be issue tracking and project management rolled into one. For example:
- Workflows
- Access control over fields
- Custom fields
- Release management
- 3P plugins and integrations
- API access
I am far from being a fan of Jira but they do have a rather large set of features. Every time I evaluate the hottest new issue tracking and/or project management solution, there is something lacking as compared to Jira.
I've often half-joked that the road to JIRA is paved with other project management tools and ticketing systems.
I don't think anybody really sets out with the intent of using the one reputedly cumbersome tool that can do anything - but after growth and pivots and new requirements and new teams and special workflows... you end up needing a combination of features that is literally impossible to get with any other tool, and who wants to fracture into multiple tools?
So you get JIRA. And it just does it all, and even if nobody is overjoyed, nobody feels like they lost, either. There's value in that.
I built the first version of IntelliJ plugin[1] to make working with the reactor stuff easier. Doesn't look like there have been much improvements to it.