Application Deployments on Nife

App and Services are Deployments can be deployed on the platform

You describe a desired state of the application in a Deployment

The Desired state of an application includes multiple states including Apps, Builders and Network


Nife deals with Stateless Applications and Edge Native Applications

Understanding Stateless applications#

A stateless app does not save data generated in one session for use in the next session with that client. Each execution is carried out as if it was the first time and responses are not dependent upon data from a previous execute and state. In contrast, a stateful application saves data about each client session and uses that data the next time the client makes a request.

Understanding Jamstack Applications#

Jamstack is the new standard architecture for the web. Using Git workflows and modern build tools, pre-rendered content is served to a CDN and made dynamic through APIs and serverless functions. Technologies in the stack include JavaScript frameworks, Static Site Generators, Headless CMSs, and CDNs.

Understanding Edge Native Applications#

Edge-native applications are built to run on a distributed network.

Specifically, edge-native applications must be:

โ€“ Highly modular to enable ease of deployment to multiple locations

โ€“ Run in real-time to unlock the value of ultra-low latency processing at the edge of the network

โ€“ Flexible and portable to be able to run on all types of edge hardware from a server to a Raspberry Pi.


Typical Usescases

Creating a deployment