partical.xyz
Web3 native backend as a service
partical.xyz
Web3 native backend as a service
The problem partical.xyz solves
Today, almost all complex DAO tools which claim to be “web3 native” host their data on centralized servers. It is hard to build complex and scalable applications without doing so. Decentralized blockchain networks, alone, are not ideal for complex applications such as productivity tools, content management systems, knowledge management systems etc.
For DAO tools to truly decentralize themselves in a way that they dont need to hold a DAO’s data hostage, they need to use decentralized storage solutions like IPFS or Arweave and decentralized data layers like Ceramic or Tableland. However, using these tools in their current form often leads to other complexities like following.
How does a DAO with multiple contributors own and manage the same data?
How can a developer easily use data networks like Ceramic in their applications?
How does a developer easily find and get started with existing data instead of having to start from scratch?
How do applications interoperate to such a degree that an individual DAO contributor can choose which platform (or experience) she wants to use and yet be able to be in sync (or have common context) with other contributors?
These are the problems we are solving with Partical.
Partical has the following features.
- Dedicated backend server for your app with apis and database and auth
- Data is stored on ceramic
- Ceramic streams are indexed by app server and a global server
- Anyone can query the global server and build frontend on top
- DAO create streams which are controlled by any member of the dao
- DAO dashboard to easily visualize data across apps
- Server side caching for improved performance
Challenges I ran into
Updates:
- Changed approach to create server which improved the server creation time from 2 mins to 10 seconds!
- Added the ability to update the server using docker
- Started using ansible for docker orchestration
Technologies used
Discussion