DADI is an acronym for Decentralised Architecture for a Democratic Internet.
You read about the Crowdsale and how to participate here
DADI does things differently. There are no data centers and no single points of failure. DADI is made up of tens of thousands of decentralized network nodes, organised by blockchain technology to ensure the fastest possible performance for your custommers and the lowest possible cost for you.
DADI provides a ready-to-roll Web Services framework with data at its heart, enabling the creation of real time, individually targeted experiences.
It’s Open Source, end to end; and it powers some of the largest and most popular products on the Web.
With DADI you can easily create versatile, content centric products. To see why others have chosen DADI, check out the success stories on DADI.tech.
You can register your interest to join the network as a Miner. You wil be contacted as soon as the network is open for participation.
Contributing guidelines for DADI Web Services can be found at the top level of their respective repositories in Git:
DADI values innovation and stability. The engineering team are careful about sacrificing one for the other, so work on balance. Because DADI is used widely in production, every single line of code that goes into DADI’s core is meticulously scrutinized. Most changes to core go through dozens, if not hundreds, of revisions before being included.
The DADI team is also aware of the time that great software design, development, translation, and testing takes. Because the technology is built around a microservices architecture, and because the teams focus is on keeping the core of the platform to essential functionality, encouraging contributed modules to extend it, the version release cycle happens a far greater pace than alternative solutions.
DADI’s release cycle schedule uses Semantic Versioning 2.0.0:
Given a version number MAJOR.MINOR.PATCH, increment the:
Additional labels for pre-release and build metadata are available as extensions to the MAJOR.MINOR.PATCH format.
Yes. And given the development pace achievable with DADI, doing so does not usually represent a significant amount of work. Data mappings to import your content into DADI API will be required and your templates will need to be moved to DADI Web (which supports multiple template languages, meaning that you probably don’t need to redevelop them). And that’s about it.
“Products built with DADI are delivered in days and weeks, not weeks and months.”
A key Web Service in the platform is DADI API, a high-performance RESTful API layer that is perfect for powering mobile applications. You can use API with DADI Publish to provide a CMS for iOS/Android/Windows Phone. And when chained with DADI Predict and DADI Track, you can start to make real time content decisions based on data intelligence.
Yes. Follow the DADI Coding Standards found within the Contributing Guidelines for each DADI app when submitting any code for inclusion in the DADI project.
To ensure consistency throughout the source code, keep these rules in mind as you are working:
You can, but it is recommend that you don’t. Hacking the core means that you won’t be able to take advantage of updates from the DADI team – including any security updates – without losing your changes. It also makes it much less likely that bugs you create will be fixed by the community. Instead, make use of the data sources, events and the hooks framework within individual DADI Web Services.
Reach out to the DADI team Slack. Or drop them a line via email. The issue queue in Git for each of the apps in the DADI platform is how we bring issues to the community’s attention.