Project Blog for Ochan. An ImageBoard.

 

Scalability Stage 1

Service level sharding.

Ochan is now capable of a scaleable deployment model in the development version. I’m going to do some more testing before making this the 1.0 version of Ochan. But, this isnt the end of the road of scalability and the pursuit of the most flexible image board software on earth.

How does it work?

The standard Ochan release contains everything you need, as usual. But, now, you can deploy the application as:

  1. The synchro service (the master service commander)
  2. The middle tier with attached/embedded database
  3. The web tier

The basic deployment just works with it all configured to run on its own.

But, you can deploy all tiers seperately. The synchro service can be load balanced for high availability. The web tier can be load balanced for increased traffic handling and high availability. And the middle tier can go as big as you want (but, like a raid 5.. if 1 fails, the whole thing fails…. (unless you load multiplex each middle tier deployment with a backup (raid 10)).

And, well, this is going to have to be the solution until berkeleydb java edition grows up and adds replication.. and then.. the synchro goes away, and the web tier can be its own distributed middle tier.

I am going to build up some tools for re-sharding an existing database.. as, well, everytime you contract or expand the shard, it’ll require some effort to redistribute the data.