Skip to content

componentLikeButton

Jump to bottom Edit New page
Patrik Schmidt edited this page Sep 11, 2013 · 38 revisions

The like button can be embedded by other websites. Entities within Metalcon also have a like button. Once a user clicks a like button the system will share this information with his social environment and subscribe the user to information provided by this entity.

The LikeButton API will be widely used by other components/services to gain informations within the social context

  • recommendations
    • friends, bands, venue, news
    • recommendations for tagging images
  • interaction with newsstream ?
  • improved search results ?
  • what more ?

** Please fill in your service, if you will use the Likebutton API **

API

Method Signature Description
log void log(String uuid1, String uuid2) where uuid1 and uuid2 are entity-ids
like (write) void like(String uuid1, String uuid2, VOTE.UP or VOTE.DOWN) create new link between uuid1 and uuid2 in the social graph
commons String getCommons(String uuid1, String uuid2) retrieves all common entities (e.g. bands) between two given entities (e.g. users)
like (read) String getIn(String uuid) retrieves all nodes to given entity (e.g. which entities likes me/are befriend with me)
String getOut(String uuid) retrieves all nodes from given entity (e.g. which entities do I like, are befriend with)

Detailed description

log

void log(uuid1, uuid2) where uuid1 is the user-cookie ID and uuid2 is the entity-cookie ID.

Logs standard interactions (pagevisits?, frequency?) with e.g. non-loggedin users

like (write)

void like(String uuid1, String uuid2, VOTE.UP or VOTE.DOWN) and void unlike(String uuid1, String uuid2)

Creates a new edge to the social graph between uuid1 and uuid2. Will be invoked when like-button is pushed. Furthermore, the enumeration value VOTE.UP or VOTE.DOWN indicates, if a given entities will be upvoted or downvoted.

QUESTION: What will be the default behavior where voting is not applicable? QUESTION: Shall the method return a boolean value to enable callbacks for frontend developer?

Therefore, unlike will delete the edge between uuid1 and uuid2.

like (read)

String getIn(String uuid) or String getOut(String uuid)

Retrieves all incoming/outgoing edges

  • getIn all incomming edges to given entity as a JSON array named with edges:
{
"uuid": 213,
"edges": [ uuid1 uuid2 uuid3 ]
}
  • getOut all outgoing edges to given entity as a JSON array named with edges;
{
"uuid": 213,
"edges": [ uuid1 uuid2 uuid3 ]
}

commons

String getCommons(String uuid1, String uuid2)

Retrieves all common entities (e.g. bands, friends, ...) between two given entities as a JSON array named with commons:

{
"uuid-from": 213,
"uuid-to": 42
"commons": [ uuid1 uuid2 uuid3 ]
}

Datamodel

Graph

Benchmarking graph is stored as plain csv file (directed)

1,2
1,3
1,5
2,1
2,5
2,4
3,1
3,5
4,2
4,5
5,1
5,2
5,4

Graph data model in lucene

Document
nodeid
----------
neighbour1
neighbour2
neighbour3
...

** Neighbourhood **

Document
from
to
----------
entity1
entity2
entity3
...

Statistics

10mio uri (big metal site has about 100k URI and we have about 100 metalsites.)

metalhammer has about 100 requests per second we assume metal hammer has 2.5% market share ==> 4k request per sec

we assume 1M metalfans in Germany (certainly it won't be more)

150B per request (64Byte cookie + 64Byte uri + timestamp + additional stuff)

HTTP Logging: 4k req / sec * 3600 s * 24 / day * 150 Byte --> 330MB logs pro tag --> 120 GB per year

This calculation comes down to 350 requests per user per day

this seems even large taking into consideration that in metal.de a user creates about 10 page views per visit.

Assuming that every metalcon user (see facebook stats on Wikipedia) fires 3 likes per day. This leads to following calculation: 1000M likes per year / (360 days * 24h * 3600s) --> aprox. 50 write requests triggered by likes

we did not take into consideration: 9k band websites and 2k venue websites

a band website could embed one global like-button or on each of their web pages.

###venue

max. 30 events per month --> aprox. 300 events per year --> 1 events (per day) * 2k venues --> 2k requests per day --> 85 requests per hour

  • each event provides a like-button

Requirements

  • Fans: share information with social environment
  • Fans: beginner friendly (metalcon already knows what content people surfed on in the past)
  • Band / Venue: wants to know fans
  • Band / Venue: Promotion
  • University: usage behavior / high scaling system (handling many http requests is an interesting research question)

Page metrics from other websites

based on google indices

metal.de: 368.000 pages

  • based on their media factsheet
    • 352.000 PageImpressions / month -> 10000 per Day -> 10 per second

metal-hammer.de: 158.000 pages

  • factsheet
  • 4.918.812 PageImpressions / month -> 170000 per Day -> 120 per second

metal-inside.de: 83.000 pages powermetal.de: 437.000 pages metal1.info: 20.000 pages

requirements

components

  • data storage
  • entry point (load balancer)
  • stupid recommender
    • (who of my friends likes this entities?)
    • who in general likes this page (how many)
  • AI recommender
    • (you might also like … (friend, band, city, web site,...))

open questions

  • how many estimated requests will have to be handled (read/write/disk access)
  • what are the different domains/modules/services within this component
  • on which services do the like-button rely on
  • concerning security
    • what are common attack vectors
    • how to prevent them

Features

  • tracking users on different sites which implemented our metalcon like-button
  • display like button with personal information
    • obtain User ID
    • gather context specific information

If user presses the like-button

  • assign entity to users "preferences"
  • maybe update newsstream of users friends

Technologies

Responsible Developer

  • Patrik
Add a custom footer
Add a custom sidebar
Clone this wiki locally