Database

Database databases will be as common as staplers in the workplace. Companies use databases to track salaries, holidays, inventory, and many other tasks worth mentioning. Essentially, when companies use databases, store large amounts of data in this state so that they can be easily retrieved, sorted, and recalled in various ways for end users to read and understand in a variety of ways is needed. The database is widely used in my workplace.

Fragmentation in the world of block chains is similar to database fragmentation in traditional software systems. In traditional databases, partitioning is a horizontal partitioning of the data in the database, and each partition is stored in a separate database server instance. This allows you to distribute the load to different servers. There are several ways to implement messaging. In the case of Ethereum, the approach they adopt is the "receipt" paradigm. When a transaction within a fragment is executed, it can change the state of its own local fragment and generate a "receipt" that is also stored in the distribution. Shared memory. You can see it later (but not changed) later.

Fragmentation is a very old concept in centralized database design. Database partitioning is the horizontal partitioning of the data in the database. Individual partitions are called slices or database slices. Each piece is stored in a separate database server instance to distribute the load. This means that the database is divided into separate databases that do not share public data. Since you can add fragments for unlimited extensions, it allows for horizontal expansion of any database system. Today, most databases such as MongoDB and MySQL support fragmentation. Therefore, technology is mature enough to become mainstream. Block chains have existed for a long time, but mainstream sharding adjustment is still not visible. One of the recommended ways is to use multiple fragments. Each piece can be processed according to the address range of the sender.

The Bluzelle database was built using three key technologies from the outset. One of them is database sharing. Bluzelle realizes massive scalability by splitting all database data and ensuring that fragments are properly stored in a cluster that is Bluzelle's own network partition. Bluzelle Swarm is a series of nodes that duplicate the same data fragmentation. All of these nodes are part of their own network that Bluzelle defines as a group. Although the architectural design of Bluzelle is a database, in the future it is conceptually the same as Etitalum of Vitalik. Today's announcement is a powerful verification statement on the design and direction of Bluzelle himself. This shows how one of the largest and fastest growing block chains uses the same principles as Bluzelle for large scale scalability.