Split analytics API

[javisantana]

Right now Maps API is 3 things:

• tile rendering api
• map stats data provider
• analytics library

Obviously the last one does not fit, we've found several cases where having analysis and rendering tied is not the best (for example, now knowing the output of an analysis we can't set the right cartocss)

So the proposal is to split the API in 2, one for analytics and the other one for rendering.

Maybe we should not create a new server right away but before releasing this as a public API we should split it.

Technical things to solve:

• Public API: I think we have a analysis attribute inside the maps api json so kind of stragithforward
• How maps api and analysis api would connect (right not uses source:'a0' but I don't think that's enough)
• How cartodb.js would interact with those?

cc @rochoa

[rochoa]

🎁 🙈 👀 💣 😂 ...😱 💥 !!!