Yes that does sound pretty cool, on a technical level.

I've never built a system that was based around microservices but if it's a way of doing things that you enjoy and have experience in (or want experience with!) then go for it :D

Yes, exactly. The Sublinks Service (which I considered calling Interact Service) allows for multiple indexes to be used. A single Index Service isn't as powerful. Plus, the Index Service doesn't have a UI for users. I see how combining them could simplify it, but I think having them separate gives more power. I want to build the Sublinks Service as more of a front-end framework, so that new UIs are built on it rather than everyone reinventing the wheel each time they want a new look. This will allow people to create their own view of the Fediverse.

Thanks! The Mobile apps would operate much like a Sublinks instance, choosing which identity services and indexes to show. I would imagine they'd just allow all of them. An alternative approach would be for the Mobile App developer to create a web service to manage those decisions and build their own API for their app to integrate with.

This microservice plan allows more people to hold different parts and reduces the risk of duplication and total loss when one instance goes down.

So, microservices architecture? Lots of ink spilled debating the pros and cons of that already, I won't add to it.

With federation with other software and with mobile apps involved via an API it already feels like we have a lot of moving parts spinning at different speeds making it hard to keep it cohesive. Throwing a microservices architecture in there would probably increase the systemic incoherence issues even more? Dunno. Seems risky.

I like your choice of python though 😎

Ooh interesting, I remember seeing this some time ago, glad you are still thinking about it. So are these various services intended to be federated and cross compatible between instances? Like if I were to spin up my own identity service, I can post under an identity I provided and authenticated myself, to a Group Service hosted by someone else, through a Sublinks UI service provided by a 3rd party?

What is the difference between the index service and sublink service? Aside from a UI, it sounds to me like the index service can do a lot of what the sublink service would offer on the content feed provisioning side.