# Object Store

The *Object Store* service can be considered a service type only for storing MobiusFlow objects. It has no functional backend. This means, unlike most other MobiusFlow services, the service will not interact with the objects stored on it.

## Uses

* For storing non-service specific objects such as the *Numeric Value* objects or *String Value* objects (Often these will be used if values are being calculated based on other objects)
* Manually writing to an object type, instead of relying on its functional parent service (e.g. manually writing the data into a LoRaWAN device object from the Flows, instead of using the *LoRaWAN LNS* service)
* Testing
* Diagnostics

<figure><img src="https://241296614-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQoV8xVJhcESUhdKQWDcm%2Fuploads%2F4ei13mXSQnMPVV9MPUWj%2Fimage.png?alt=media&#x26;token=3e5700f1-7dc1-4319-abf7-fb791ff149f4" alt=""><figcaption><p>An example Numeric Value object residing on an Object Store Service</p></figcaption></figure>

## Limitation

Although it is possible to place any object type in an *Object Store* service, because the service has no functional backend, it cannot interact with most object types in fully functional way. For example, adding a LoRaWAN device object to an *Object Store* service is possible, however the object will not be automatically populated by incoming LoRaWAN messages. If the LoRaWAN device object was placed into its functional parent service (*LoRaWAN LNS* service / *LoRaWAN Devices* service) instead, it would function as normal, as these service types have the correct backend to work with this object type.