JBilling throughput
Hi,
As per JBilling doc, JBilling can process hundreds of billing events per second. Is it formally a benchmark statement ?
I have my solution which generates huge (in thousands per second) and concurrent (most of the time) billing events.
Can I consider JBilling to process billing events of this scale ?
Another question on scalability:
Does JBilling is ready to deploy Kubernetes environment ? What I see in the doc is that it supports horizontal scaling where I may have to spawn additional VM instances (on-promise) .. Can I deploy JBilling in my own Kuerbetes Cloud environment and utilize K8S scaling techniques to achieve scaling . ?
Thanks,
Ganesh
Keyboard shortcuts
Generic
| ? | Show this help |
|---|---|
| ESC | Blurs the current field |
Comment Form
| r | Focus the comment reply box |
|---|---|
| ^ + ↩ | Submit the comment |
You can use Command ⌘ instead of Control ^ on Mac
1 Posted by rakesh.sahadeva... on 01 Jun, 2020 04:56 AM
HI Ganesh,
We are processing average 5 million calls per day . You can deploy as docker and works well in Open shift. You can try below and let me know any issues. I can share the base DB based on your database
https://hub.docker.com/r/ngecom/ngbilling
2 Posted by Vikas@WebDataTe... on 10 Jul, 2021 10:42 AM
jBilling throughput can be as high as 4 m records per day on a single node,
with 4 core and 8 gb ram. You can cluster it to simply scale that to higher
numbers. There is a feature called batch servers in jbilling where
dedicated servers could be used per batch job. It is configurable through
jbilling.properties file.