Skip to main content
Version: 5.x.x

Core Data Flow

We try to provide the deepest possible knowledge about the architecture of our library; feel free to write any adapters, plugins, or additions. The flow of a request through the Hyper Fetch system is presented below. The steps from the moment of adding a request to the dispatcher to passing data to the component are included.

Request_Lifecycle
create request
use of send() method
Check online status
pick request from queue and send to adapter
Save Data
Emit Data
Emit Event
Emit Event
Emit Event
Emit Event
Emit Event
Events
Events
Request_Start
Upload
Response Start
Download
Response
App Manager
Request Manager
Request
Dispatcher
Http Adapter
Client
Cache
Component

Cache​

The cache saves data under cacheKey values, which allows us to easily use it.

GET_/users?page=1
GET_/users/1
GET_/users
unique key
Cache Storage
Cache Key #1
Cache Key #2
Cache Key #3
Cache Key ...

Response event flow​

The diagram below shows how mutation is propagated in our system.

data mutation
mutation
emit new data
new Data #3
Cache Storage
Cache Listeners
Data#1
Data#2
Data#3