Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

If it takes you more than a few days to put together a basic analytics platform and reporting system, you're a script kiddie.

Not hard to track page hits, time on, time off, and arbitrary events.

EDIT:

Seriously? Folks, it's a table for analytics events, a few SQL queries to do basic reporting (at least in Postgres), a little bit of client-side JS to post the events, and a bit of server-side code to create the routes and maybe display the report page.

I guess if it doesn't include Kafka, Mesos, Kubermetes, Neo4j, and Docker, it isn't delivering business value.

ffs.



It is quite costly to write to the database for each hit, I guess most downvotes is because of this. If you limit writes by keeping them in some memory cache it's doable for slightly higher loads.


If you're Google, sure. Most of the startups here aren't Google.

People are prematurely optimizing if they fear is "but but but mah datamoose".

Also, it's not prohibitively costly if you do even slight batching of the events, say batch load between every five minutes or an hour.

I'd love to hear somebody with war stories chime in though!


You criticize people for _premature optimization_ while in the same breath advocating rolling your own, shitting implementation for page views? Right...


Incorrect--remember, there is no way of guaranteeing privacy of users *if you outsource analytics for your page.

You're missing the point of why "rolling your own shitting [sic] implementation" is worth it: it's not the speed, it's the privacy.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: