At Radar we consider dApps to be an application design pattern that augments modern web applications by distributing critical components across a network of peers or nodes.
Radar has a clear vision. If you keep up with our content, you are probably sick of hearing it: onboard the world to the token economy. The difficulty with this vision is that it requires a way for the world to interface with the token economy.
Currently, we believe the best interface to the token economy is through the dApp ecosystem. This is why we are focused on building dApps and using the lessons we learn during the process to contribute to the ecosystem in a meaningful way.
What is a dApp?
The definition of a dApp is dynamic and will continue to change as the decentralized ecosystem matures and naming conventions and definitions solidify.
At Radar we consider dApps to be an application design pattern that augments modern web applications by distributing critical components across a network of peers or nodes.
Decentralization isn’t binary, it’s on a spectrum . A well designed dApp leverages the existing web application foundation AND distributes critical components of the application to mitigate risk while ensuring an excellent user experience.
In the specific use case of Radar Relay, we rely on the 0x protocol and web3 to store a user’s intent to trade without having access to a user’s personal information or tokens. Simultaneously we utilize modern web application infrastructure, such as Kubernetes, for reliable web server infrastructure. This architecture mitigates the risks of storing sensitive information on our private servers while maintaining the efficiency and user experience of a modern web application.
Learn more about Radar Relay’s technical architecture in a previous post.
