Server Scalability - Revision history

JET OOTO at 19:46, 3 June 2025

2025-06-03T19:46:04Z

← Older revision		Revision as of 19:46, 3 June 2025
Line 1:		Line 1:
			6/3/25
			JET: Its an interesting concept! I think an adaptation of the AT Protocol is possible for this: https://docs.bsky.app/docs/advanced-guides/federation-architecture
			* Implementing something like this is pretty ambitious and you would need some (a team) high-level software/cloud engineers to work through this. I'll see if I can come up with a concept/design. At the very least from what I'm reading, OSE is relying more on docker/containerization so you can host your own registry for containers which would act like a packaged server someone could deploy given they have hosting and knowledge of docker. It would be nice to complete the federation process automatically when ever a new container/node comes up online.
	6/2/25		6/2/25

	I think we can evolve an amazing scaling strategy the way we are going now. If we succeed at true modularity and portability of wiki etc - we can do what Amazon does: spin up more capacity on demand. We can do this ina distributed way if other people can readily clone and sync additional secure servers at times of peak demand, such as swarm design where thousands are participating actively. What do you think it would take to do that?		I think we can evolve an amazing scaling strategy the way we are going now. If we succeed at true modularity and portability of wiki etc - we can do what Amazon does: spin up more capacity on demand. We can do this ina distributed way if other people can readily clone and sync additional secure servers at times of peak demand, such as swarm design where thousands are participating actively. What do you think it would take to do that?

Marcin at 00:29, 3 June 2025

2025-06-03T00:29:08Z

← Older revision		Revision as of 00:29, 3 June 2025
Line 1:		Line 1:
	6/2/25		6/2/25

	I think we can evolve an amazing scaling strategy the way we are going now. If we succeed at true modularity and portability of wiki etc - we can do what Amazon does: spin up more capacity on demand. We can do this ina distributed way if other people can readily clone and sync additional secure servers at times of peak ~~sldemans~~, such as swarm design where thousands are participating actively. What do you think it would take to do that?		I think we can evolve an amazing scaling strategy the way we are going now. If we succeed at true modularity and portability of wiki etc - we can do what Amazon does: spin up more capacity on demand. We can do this ina distributed way if other people can readily clone and sync additional secure servers at times of peak demand, such as swarm design where thousands are participating actively. What do you think it would take to do that?

Marcin: Created page with "6/2/25 I think we can evolve an amazing scaling strategy the way we are going now. If we succeed at true modularity and portability of wiki etc - we can do what Amazon does:..."

2025-06-03T00:28:19Z

Created page with "6/2/25 I think we can evolve an amazing scaling strategy the way we are going now. If we succeed at true modularity and portability of wiki etc - we can do what Amazon does:..."

New page

6/2/25

I think we can evolve an amazing scaling strategy the way we are going now. If we succeed at true modularity and portability of wiki etc - we can do what Amazon does: spin up more capacity on demand. We can do this ina distributed way if other people can readily clone and sync additional secure servers at times of peak sldemans, such as swarm design where thousands are participating actively. What do you think it would take to do that?