I’ve looked into pubsub and the base aspects of how it’s supposed to work. With plans to make a platform that runs entirely within IPFS, it definitely looks like what I’ll want to go with for things like chat and notifications and search! However there is one fundamental problem, which I don’t fully understand yet and depending on the answer might throw a wrench in my idea of using this system.
Can pubsub messages be persisted and ultimately used as a database? Or are they sent in a similar fashion to TCP packets, meaning they’re only sent once and lost if the receiver isn’t currently online? If it’s the later scenario, is there some alternative to have a persistent flexible database within the network?
My plans definitely involve using some sort of database, which is where IPFS makes things tricky as you can’t use stuff like mysql the way you can on a conventional web server. Pubsub looks like it would perfectly do the trick if used intelligently, but it’s useless for this if it’s not a persistent database. I’m hoping I’d be able to use the JS API to dynamically generate a channel for each user and site component that needs it, from which information (stored as messages) can be retrieved at any given moment.