Open solvaholic opened 2 years ago
Between the drawing and the photo I'd changed authorization into extract destination.
Looking at it from above, so to speak, helps me see how [generally available parts] can plug in different places.
Important to me is abstracting notification rules away from notification sources. The system envisioned here knows of three types of notifications:
A destination tag is added to the event during extractor processing. After extractor processing completes, route each event to one or more destinations. "Trash" is events that have no destination.
What I'm interested in with this project is not providing a novel solution. I'm interested in contributing to an open source framework for a social media data pipeline.
If such a thing, or components of such a thing, already exist, then prefer using those over creating new solutions.
If such a thing, or components of such a thing, already exist, then prefer using those over creating new solutions.
I think socioboard looks like it'd cover all of what I'm looking for: https://github.com/socioboard/Socioboard-5.0/tree/master/socioboard-api
Socioboard Api's is created with Node.js, Express, MongoDB and Sequelize ORM. Socioboard Api are classified to four micro services. They are namely
User Services - Responsible for Managing User, Team, Payment, App Insights and Admin functionalities.
Publish Services – Responsible for Managing Media Uploads, Scheduling, Publish now and Report functionalities through respective Social Network Api's.
Feed Services – Responsible for fetching Feeds from Social network API's and various popular trending networks such as Pixabay, Imgur, Daily motion, Flickr and so on.
Notification Services – Responsible for sending emails and notify the user activities through Socket.io