Package Exports
- mongodb-activity-feed
This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (mongodb-activity-feed) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.
Readme
Activity Feed Node & Mongo DB
Simple example of how to build a news feed with Node and MongoDB. I created it for this blogpost: "Building Activity Feeds with MongoDB vs the alternatives"
https://docs.google.com/document/d/11gfMOPgE476fLsb2sXYy955X2G4egUv4p7-zlXdf8hU/edit
It uses CRDTs to reduce the need for locks.
Install
yarn add mongodb-activity-feedMongoDB & Redis Activity Feed
brew install redis mongodb
brew services start redis
brew services start mongodbInitialization
Here's a very short example
import { FeedManager } from 'mongodb-activity-feed'
const fm = new FeedManager(mongoConnection, redisConnection, {
bull: false,
firehose: false,
})And a bit longer one:
import { FeedManager, FayeFirehose } from 'mongodb-activity-feed'
import Redis from 'ioredis'
import mongoose from 'mongoose'
const redis = new Redis('redis://localhost:6379/9')
const mongo = mongoose.connect(
'mongodb://localhost:27017/mydb',
{
autoIndex: true,
reconnectTries: Number.MAX_VALUE,
reconnectInterval: 500,
poolSize: 50,
bufferMaxEntries: 0,
keepAlive: 120,
},
)
const fayeFirehose = new FayeFirehose('http://localhost:8000/faye')
const fm = new FeedManager(mongo, redis, { bull: true, firehose: fayeFirehose })The bull option determines if activity fanout is done over a bull queue or synchronous. The firehose option allows you to listen to feed changes in realtime using Faye.
Timeline MongoDB
Here's a quick tutorial on a simple timeline with mongodb-activity-feed
const timelineScott = await fm.getOrCreateFeed('timeline', 'scott')
const userNick = await fm.getOrCreateFeed('user', 'nick')
await fm.follow(timelineScott, userNick)
const activity = {
actor: 'user:nick',
verb: 'watch',
object: 'video:123',
}
await fm.addActivity(activity, userNick)
const activities = await fm.readFeed(timelineScott, 0, 10)Notification System MongoDB
Here's a quick tutorial on a simple timeline with mongodb-activity-feed
const notificationBen = await fm.getOrCreateFeed('notification', 'ben')
// lets say you want to notify Ben that Nick likes his post
const activity = {
actor: 'user:nick',
verb: 'like',
object: 'post:123',
}
await fm.addActivity(activity, notificationBen)
// group together all activities with the same verb and actor
const aggregationMethod = activity => {
return activity.verb + '__' + activity.actor
}
const groups = await fm.readFeed(notificationBen, 0, 3, null, aggregationMethod)Adding an activity
Add an activity like this.
const activity = {
actor: 'user:nick',
verb: 'like',
object: 'post:123',
}
fm.addActivity(activity, feed)Removing an activity
Remove an activity:
const activity = {
actor: 'user:nick',
verb: 'like',
object: 'post:123',
}
fm.removeActivity(activity, feed)Follow a feed
// follow with a copy limit of 10
const timelineScott = await fm.getOrCreateFeed('timeline', 'scott')
const userNick = await fm.getOrCreateFeed('user', 'nick')
await fm.follow(timelineScott, userNick, 10)Follow Many Feeds
// follow with a copy limit of 10
const source = await fm.getOrCreateFeed('timeline', 'scott')
const target = await fm.getOrCreateFeed('user', 'nick')
const target2 = await fm.getOrCreateFeed('user', 'john')
await fm.followMany([{ source, target }, { source, target2 }], 10)Unfollow a feed
const timelineScott = await fm.getOrCreateFeed('timeline', 'scott')
const userNick = await fm.getOrCreateFeed('user', 'nick')
await fm.unfollow(timelineScott, userNick)Create Many Feeds at Once
const feedReferences = [
{ group: 'timeline', feedID: 'scott' },
{ group: 'notification', feedID: 'ben' },
]
const feedMap = await fm.getOrCreateFeeds(feedReferences)Reading a feed from MongoDB
Basic Read
const notificationAlex = await fm.getOrCreateFeed('notification', 'alex')
await fm.readFeed(notificationAlex, 0, 10)Ranked Feed
const notificationAlex = await fm.getOrCreateFeed('notification', 'alex')
// asumes that you have a property on your activity called "popularity"
const rankingMethod = (a, b) => {
return b.popularity - a.popularity
}
const activities = await fm.readFeed(notificationAlex, 0, 3, rankingMethod)Aggregated Feed
const notificationAlex = await fm.getOrCreateFeed('notification', 'alex')
// group together all activities with the same verb and actor
const aggregationMethod = activity => {
return activity.verb + '__' + activity.actor
}
await fm.readFeed(notificationAlex, 0, 10, null, aggregationMethod)Activities are unique on the combination of foreign_id and time.
If you don't specify foreign id the full activity object will be used.
Firehose Configuration
// socket (recommended)
const firehose = new SocketIOFirehose(SOCKET_URL)
// faye
const firehoseFaye = new FayeFirehose(FAYE_URL)
// dummy firehose
const firehoseDummy = new new DummyFirehose(message => {})()
fm = new FeedManager(mongo, redis, { firehose: firehose, bull: false })Pros/Cons
MongoDB is a nice general purpose database. For building activity feeds it's not a great fit though. Cassandra and Redis will in most scenarios outperform a MongoDB based solution.
Dedicated activity feed databases like Stream are typically 10x more performant and easier to use.
So in most cases you shouldn't run your activity feed on MongoDB. It only makes sense if your traffic is relatively small and you're not able to use cloud hosted APIs. Unless you really need to run your feeds on-prem you should not use this in prod.
If you do need to run on-prem I'd recommend the open source Stream-Framework
Contributing
Pull requests are welcome but be sure to improve test coverage.
Running tests
yarn testLinting
yarn lintPrettier
yarn prettierBenchmarks
Benchmark prep
You'll want to configure the following environment variables
STREAM_APP_ID=appid
STREAM_API_KEY=key
STREAM_API_SECRET=secret
MONGODB_CONNECTION=connectionstring
SOCKET_URL=http://localhost:8002
REDIS_HOST=localhost
REDIS_PORT=6379You can create a .env file to make this easier
For dev purposes you can use this setup:
git clone https://github.com/GetStream/mongodb-activity-feed.git
yarn build
pm2 start process.jsonThis will start a worker and socket.io cluster.
Benchmark 1 - Read latency
Note: Babel-Node is convenient during development. Use the compiled version in the dist dir for production benchmarks.
MongoDB
# flush your mongo instance before running this
REPETITIONS=1 CONCURRENCY=1 babel-node read_latency_mongo.jsStream
REPETITIONS=1 CONCURRENCY=1 babel-node read_latency.jsThe blogpost runs the benchmark with 10 repetitions and concurrency set to 5, 10 and 20.
Benchmark 2 - Fanout & realtime latency
MongoDB
# flush your mongo instance before running this
REPETITIONS=1 CONCURRENCY=1 babel-node fanout_latency_mongo.jsStream
REPETITIONS=1 CONCURRENCY=1 babel-node fanout_latency.jsThe blogpost runs the benchmark with 1, 3 and 10 for the concurrency. Repetitions is set to 1.
Benchmark 3 - Network Simulation/ Capacity
MongoDB
# flush your mongo instance before running this
REPETITIONS=1 CONCURRENCY=1 babel-node capacity_mongo.jsStream
REPETITIONS=1 CONCURRENCY=1 babel-node capacity.js