Scheduling tasks to be run in the future

Integrating Ifacees and Adapters into a KOS app.

Building an adapter that communicates over blink using a custom Iface and the board Iface.

KOS allows users to create and store databases using a combination of SQlite and the JDBI library (Java Database Interface). This article will go into depth on how to create and use databases within KOS.

The `SpawnService` within KOS is a service whose primary responsibility is to start/stop native programs. It preforms this function across the nodes of a device. All the programs started via the service are monitored by KOS and will be restarted using a back-off algorithm in the event they crash.

KOS comes packaged with a FUSE (File System in User Space) filesystem. This allows users to mount KABs directly into the local native filesystem.

Learn how KOS's Virtual File System (VFS) enables efficient content serving to the front end and other applications

A common pattern when developing with KOS is the use of services, which act as managers or coordinators responsible for specific functionality. Services are generally singletons

KOS’s ready protocol ensures services are only used once they are fully initialized, even when setup happens asynchronously. Readiness can work in and outside a BeanContext, and ReadyIndicators let developers coordinate complex, multi-stage initialization.

Move your device to production by verifying KAB artifacts, managing production keys, and transitioning from test mode to a locked production state.