# Basic Requirements

### <mark style="color:green;">You application is stateless</mark> <a href="#id-1-1-keep-your-application-stateless" id="id-1-1-keep-your-application-stateless"></a>

It is explicit by saying that *web applications should be stateless*, as *web applications should be stateless unless there is a very good reason to have a state*. A *shopping cart* is a stateful feature by design and denying that is counterproductive. What our proposal is to make these state persevere on the client-side rather than at the server-side. If it is not possible, keep a shared resource for instances to store that data and retrieve. IndustryApps platform expects your application to be stateless, so we can increase and decrease the number of instances based on the load.

### <mark style="color:green;">Your application supports multitenancy</mark> <a href="#id-1-5-should-support-multitenancy" id="id-1-5-should-support-multitenancy"></a>

IndustryApps is a platform used by multiple clients called tenants. We must take care not to share the data of each tenant. ie if your application needs to store some data, you must be cautioned on tenants. Currently, tenant is a Key combination of companyId and plantId of each user.

{% hint style="info" %} <mark style="color:green;">IndustryApps focuses on Industrial solutions. Your product should be proven and already deployed in at least 1 reference factory site any where in the world. It is always a best practice to provide references to support customers decision.</mark>&#x20;
{% endhint %}

### &#x20;<a href="#id-1-2-keep-your-application-sync-with-application-registry" id="id-1-2-keep-your-application-sync-with-application-registry"></a>