|
|
|
|
|
by mwetzler
4649 days ago
|
|
Hmm... that does make your data collection tricky. Ideally you have something that captures events as they happen, in a nice format, rather than waiting on summary report views. Looks like you already built an API similar to ours, but if you ever reach scale/maintenance/availability bottlenecks then check us out. Most of our customers use charts that query in realtime when the page loads or the user adds a filter or whatever, but batching reporting like you describe is a way to optimize the page load time. Generally we want to help developers before they already built the solution themselves. I think your homegrown solution is probably exactly what you need right now to validate your product in the market. When you want to invest more in your architecture for improved performance, scalability, or reliability, then you can consider building v2.0 on Keen IO :) |
|