You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
40 lines
3.3 KiB
40 lines
3.3 KiB
2 years ago
|
# DTP System Architecture
|
||
|
|
|
||
|
|
This is just a high-level explanation of the DTP system architecture so you can understand your node's place within it and how to get the most out of it. DTP is a Distributed Service Oriented Architecture. It is made of nodes. Some nodes have special capabilities that define the DTP Grid.
|
||
|
|
|
||
|
|
OAuth2 is used heavily throughout the system to authenticate and authorize users to services. Services can then publish information about events. Those events can then become notifications.
|
||
|
|
|
||
|
|
This is accomplished by establishing some nodes as Core nodes. A Core node has a user database, people sign up for accounts on it, it does things for them, and it is an OAuth2 provider.
|
||
|
|
|
||
|
|
All other nodes are OAuth2 consumers that can ask any connected Core to authorize and authenticate people to then publish actions and create events on their network(s).
|
||
|
|
|
||
|
|
## DTP Base
|
||
|
|
https://git.digitaltelepresence.com/digital-telepresence/dtp-base
|
||
|
|
|
||
|
|
Base is the base project from which all others are derived. It implements the common development and service framework for this entire software platform. It also implements Kaleidoscope, the protocol the DTP network uses to share information about people and their events.
|
||
|
|
|
||
|
|
## DTP Core
|
||
|
|
https://git.digitaltelepresence.com/digital-telepresence/dtp-core
|
||
|
|
|
||
|
|
Core implements a user account database, notification system, global search, network message routing, core user account services, and it's community members' home page and home feed. Cores connect to each other to form a globally distributed and fully decentralized network of online communities that share information in real time.
|
||
|
|
|
||
|
|
## DTP Venue
|
||
|
|
|
||
|
|
Venue is DTP's live streaming and media hosting platform. It generates events when channels go live, upload new videos to their VoD library, finish a stream and have the episode appear on DVR, or post news updates.
|
||
|
|
|
||
|
|
Venue is not an open source project because you do not want to try to operate a "Venue" instance. It is uncommon technology with uncommon requirements. DTP works with select partners who do contribute to the development, testing, and leading-edge use of Venue, but it is not an open project and does not accept public contributions.
|
||
|
|
|
||
|
|
## DTP Sites
|
||
|
|
https://git.digitaltelepresence.com/digital-telepresence/dtp-sites
|
||
|
|
|
||
|
|
Sites is the DTP blogging platform. People can easily create a website with us and publish pages and articles on it. Other people on our network can follow the whole site or specific authors on it. They will receive optional notifications and entries in their global feed when new articles are published or replies are received to their comments (for example).
|
||
|
|
|
||
|
|
## DTP Social
|
||
|
|
https://git.digitaltelepresence.com/digital-telepresence/dtp-social
|
||
|
|
|
||
|
|
Social is a simple open source social network designed to let people follow people and get their updates in real time. Social can route messages through Cores to other nodes just like anything else in the DTP ecosystem, making them incredibly powerful for quickly distributing information.
|
||
|
|
|
||
|
|
## DTP Links
|
||
|
|
https://git.digitaltelepresence.com/digital-telepresence/dtp-liberty-links
|
||
|
|
|
||
|
|
Links offers members a profile page where they can list various links. This gives them a very easy to use and straightforward landing page they can use to direct their audience to their various online destinations with some basic analytics.
|