In this updates, we fix all found bugs and improve some designs. We are expecting more feedbacks.
Guzz is a DB framework designed for large-scaled system. Most of time, it is used to cut big tables and distribute them in several machines with user-defined sharding rules.
All features are designed for busy and large systems running in REAL world, not just demos.
guzz’s database layer full stack solution:
guzz has 6 features for database solution:
- You have too many tables in a database, or they took too much resource for one machine. Distribute them in different database machines with dbgroup in chapeter 3: http://code.google.com/p/guzz/wiki/TutorialGuzzXml
- Some table is too big. Spit them into small ones with ShadowTable in chapter 15: http://code.google.com/p/guzz/wiki/TutorialShadowTable
- Your business is special, for example a shopping site; each table may/should own its special columns. Ok, split them with CustomTable in chapter 16: http://code.google.com/p/guzz/wiki/TutorialCustomTable
- Big tables are split, but the split small tables are too many or too big in total to store together. Distribute the small tables in different database machines with VirtualDB in chapter 17: http://code.google.com/p/guzz/wiki/TutorialVirtualDB
- Some column is too big to store in the database, or should be treated very special. Store it in File System, in memcached, or in anything you like with CustomColumnLoader in chapter 11: http://code.google.com/p/guzz/wiki/TutorialLazyLoad
- The system is really very very busy, a single database is absolutely impossible to achieve your mission. Ok, deploy more READ machines with the native read-write separation support in guzz.
Guzz can work with hibernate and ibatis, and can also work alone. If your system meets something of lacking database-scale ability, deploy more database machines and introduce guzz to upgrade database-scale related modules.
Read more about us: http://code.google.com/p/guzz/