Create the largest seamless world populated by the most players, objects and systems by building the complexities of server load balancing and object migration across boundaries, enabling a seamless gameplay experience for your players.
The core networking architecture allows for effectively infinite numbers of clients to be connected to a single virtual world without having to create shards that divide the world into overlapping instances. This architecture stems from the result of years of development in eliminating any bottlenecks that would stand in the way of complete linear scaling of all components of the server.
Users create actions through client interactions. Those actions are instantly passed to the server where state is updated and resulting events are broadcast. The system efficiently passes events to only clients that require the state change based on “need to know” principles implemented to reduce traffic and boost efficiency across the entire system.
Actions and events change the contour of the Metaverse, range in scale and amplitude and are never rolled back. The evolving world will be in a constant state of change and all change will be persistent. This new type of persistence that never resets will drive a new paradigm within virtual worlds -- accountability from lasting consequences.
The core server communicates with clients, providing them with real-time updates to the objects in the metaverse. A single cluster is intended to support approximately two million concurrent users. Coordinating multiple clusters to work in tandem will be left for the next phase of development.
The hardware / infrastructure needs to be designed to support the maximum throughput of data required to operate the metaverse. This includes the servers, networking hardware, provisioning, and software configuration. The physical machines will be run from a single data center, however the next phase will require global distribution of hardware.
The metaverse, in part or in full, should be accessible from any device. Applications will likely initially be programmed for Windows and Mac, Android and iOS, as well as Oculus and several other VR headsets. The RP1 metaverse is optimally designed as a 3D/VR experience, however it will be accessible on 2D devices. Additionally, account management and similar features can be offered on any device.
The Metaverse’s virtual world and the infinite content it will contain are years away. The virtual world paired with our phase 2 demo will only be a shell of what will come and is meant to showcase the networking and scalability of the system.
Virtually every facet of the metaverse will touch a database in some fashion. The amount of data collected and stored will be both intricate and massive. In addition to the primary data storage and retrieval functionality of the database, implementations for security, replication, backup, and restoration will need to be implemented.
Over time, an unimaginably large set of worlds and objects will be created by users of the metaverse. These components are divided into four primary domains. Standards will need to be devised for each, and the protocols for insertion, update, deletion, and customization of components within the metaverse maps will need to be defined.
A consistent set of user interface software components will be required across various applications used to access the metaverse. This includes menus, gestures, iconography, and internationalization since it is assumed users from all around the world will be participating. SDKs for accessing these software components will be made for application developers.
Users will need to communicate through speech while present in the metaverse, necessitating a real-time audio channel. Voice input will need to be mixed on the server, while prerecorded sound clips associated with objects can still be mixed on the client. Advanced features such as directionality and volume modulation can always be improved in future phases.
While a majority of processing and storage will be provided by the core servers and databases, specific facets of the metaverse will be relegated to blockchain where transparency and accountability are crucial. The choice of blockchain technology will be based on multiple factors including speed of transactions, hardware, and integrity.
Because users will be able to accumulate wealth in the metaverse, special consideration must be given to securing these assets. It is a certainty that accounts will be compromised and assets stolen from them. Authentication and verifying identity as the basis of ownership while maintaining copious amounts of anonymity must be built into the system from the ground up.
Virtually every aspect of the metaverse will require administrative control, customization, or oversight. Tools to administer the system must be designed in conjunction with the client and server software.
The code of the RP1 Framework is so effecient it can help save the planet. Really.Learn more
We haven't just mapped this journey, we're already on the road. See where we are and where we're headed.Learn more
The RP1 Framework supports an effectively infinite number of active users on fewer machines than you'd probably believe.Learn more