Skip to content

Releases: zmyzheng/TweetMap

TweetMap V2.0.0: New Architecture

16 Nov 04:09
Compare
Choose a tag to compare
  1. Use Kafka as message queue.
  2. Use Apache Flink for stream data processing
  3. Support Geographical Tweet Heat Map with Kibana
  4. Support docker and Kubernetes deployment

TweetMap v1.0.1: UI improvement and keywords change

21 Oct 19:06
Compare
Choose a tag to compare

Features:

  1. UI improvement:
    1.1 add username, create time, place to front end UI
    1.2 set the default filter distance to 1000 km

  2. keywords change:
    In v1.0.0, the number of tweets with keyword "job" is much larger than that of other keywords. In this version, we modify some keywords and change them to [ "sports", "family", "movie", "google", "apple", "amazon", "fashion", "food","song", "study"]

TweetMap

21 Oct 00:57
Compare
Choose a tag to compare

Tweet Map with Trends

This project develop and deploys a web application using AWS Cloud services. The web application would collect Twitts and do some processing and represent the Twitts on GoogleMaps. Following are the required steps:

  1. Use Twitter Streaming API (Links to an external site.) to fetch tweets from the twitter hose in real-time. Collect at least one week's worth of tweets.
  2. Use AWS (Links to an external site.) ElasticSearch (Links to an external site.) to store the tweets on the back-end.
  3. Create a web UI that allows users to search for a few keywords (via a dropdown). The keywords (up to 10) can be of your choosing.
  4. Use Google Maps API (Links to an external site.) (or any other mapping library) to render these filtered tweets in the map in whatever manner you want.
  5. Deploy your application on AWS Elastic Beanstalk (Links to an external site.) in an auto-scaling environment.
  6. Use ElasticSearch’s (Links to an external site.) geospatial feature that shows tweets that are within a certain distance from the point the user clicks on the map.