# Problems in Data Storage Process

As the current Internet ecosystem grows based on cloud computing, most IoT services are also provided based on cloud computing. In cloud computing, almost all data is shared through a cloud server system, and cloud computing services are currently operated by a small number of centralized companies. Such a centralized system has the advantage that the service provider is clear and fast, but has a problem in that the dependence on a specific company increases as time goes by, and the monopoly of the service provider company is accelerated. In addition, no matter how secure the cloud server is, if it is subjected to intensive cyber-terrorism or physical attack, it will not be able to perform its normal functions.

In opposite, if a specific company or organization manages data too strictly in a centralized system, efficient mutual use of each data becomes impossible. This Data Silo phenomenon accelerates inefficiencies in data storage and extraction.

As long as the IoT system is too dependent on the centralized system, it will inevitably have great limitations in efficiently using the vast amount of data generated in the IoT ecosystem.

The Ontact Protocol intends to provide a new solution to the existing centralized IoT service by utilizing blockchain technology, a process of trust. We want to build a blockchain-based IoT ecosystem where all data producers can manage and trade their data fairly and freely, crossing the boundaries of individuals and businesses, industries and countries.


---

# 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://ontactprotocol-team.gitbook.io/ontactprotocol_en/challenges-in-existing-iot-market/problems-in-data-storage-process.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.