# Architecture

## <mark style="color:purple;">🔅 Game Technology</mark>

Currently our games will be built using Unity. The functions behind the game will be run in a simulation coded in pure C++ that will execute the game instances in less than a few milliseconds. This will then be hooked up to Unity, where it is visualized. Ultimately we plan to expand into other gaming development platforms like Unreal Engine.

## <mark style="color:purple;">**🔅 Hosting**</mark>

We plan to have our backend hosted on the Amazon Web Services (AWS). Our core backend services will eventually be built using a serverless model with AWS Lambda. This will enable us to provide effectively unlimited scalability whilst also maintaining a cost-effective solution. We plan to have our primary persistence mechanism to be DynamoDB, where we plan to leverage transactional features to provide an atomic, consistent, isolated durable and highly available solution. Under the hood we plan to leverage the full gamut of AWS monitoring and security services including CloudWatch, GuardDuty, Inspector, Detective and Security Hub.

## <mark style="color:purple;">**🔅 Storage**</mark>

Hunycomb Games plans to utilize LevelDB for its Blockchain Storage. For State Storage, Hunycomb Games plans to use a KhaosDB in the full-node memory that can store every one of the recently forked chains produced inside a specific timeframe and supports observers to change from their own active chain quickly into another principal chain. It can likewise safeguard blockchain storage by making it more table from terminating unusually in an intermediate state.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://hunycomb-games.gitbook.io/docs/ecosystem/myhive-rewards/architecture.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.