Releases: quarks-edge/quarks
Quarks v0.4.0
Quarks v0.4.0
Release that matches the code that will be imported to the Apache Software Foundation for incubation of Quarks as a podling
Please see http://quarks-edge.github.io/ for more information.
Quarks is an open source programming model and runtime for edge devices that enables you to analyze data and events at the device. When you analyze on the edge, you can:
- Reduce the amount of data that you transmit to your analytics server
- Reduce the amount of data that you store
A Quarks application uses analytics to determine when data needs to be sent to a back-end system for further analysis, action, or storage. For example, you can use Quarks to determine whether a system is running outside of normal parameters, such as an engine that is running too hot.
If the system is running normally, you don’t need to send this data to your back-end system; it’s an added cost and an additional load on your system to process and store. However, if Quarks detects an issue, you can transmit that data to your back-end system to determine why the issue is occurring and how to resolve the issue.
Quarks enables you to shift from sending a continuous flow of trivial data to the server to sending only essential and meaningful data as it occurs. This is especially important when the cost of communication is high, such as when using a cellular network to transmit data, or when bandwidth is limited.
The following use cases describe the primary situations in which you would use Quarks:
- Internet of Things (IoT): Analyze data on distributed edge devices and mobile devices to:
- Reduce the cost of transmitting data
- Provide local feedback at the devices
- Embedded in an application server instance: Analyze application server error logs in real time without impacting network traffic
- Server rooms and machine rooms: Analyze machine health in real time without impacting network traffic or when bandwidth is limited
Deployment environments
The following environments have been tested for deployment on edge devices:
- Java 8, including Raspberry Pi B and Pi2 B
- Java 7
- Android
Documentation
Please read the Documentation including Javadoc.
New in 0.4.0
- Sample scripts for running on Windows
- Batch processing of a stream
- Websocket connectors
- Job name support
- Publish-subscribe model (step towards a full device scenario)
- Json Control service (step towards a full device scenario)
Quarks v0.3.0
Quarks v0.3.0
Please see http://quarks-edge.github.io/ for more information.
Quarks is an open source programming model and runtime for edge devices that enables you to analyze data and events at the device. When you analyze on the edge, you can:
- Reduce the amount of data that you transmit to your analytics server
- Reduce the amount of data that you store
A Quarks application uses analytics to determine when data needs to be sent to a back-end system for further analysis, action, or storage. For example, you can use Quarks to determine whether a system is running outside of normal parameters, such as an engine that is running too hot.
If the system is running normally, you don’t need to send this data to your back-end system; it’s an added cost and an additional load on your system to process and store. However, if Quarks detects an issue, you can transmit that data to your back-end system to determine why the issue is occurring and how to resolve the issue.
Quarks enables you to shift from sending a continuous flow of trivial data to the server to sending only essential and meaningful data as it occurs. This is especially important when the cost of communication is high, such as when using a cellular network to transmit data, or when bandwidth is limited.
The following use cases describe the primary situations in which you would use Quarks:
- Internet of Things (IoT): Analyze data on distributed edge devices and mobile devices to:
- Reduce the cost of transmitting data
- Provide local feedback at the devices
- Embedded in an application server instance: Analyze application server error logs in real time without impacting network traffic
- Server rooms and machine rooms: Analyze machine health in real time without impacting network traffic or when bandwidth is limited
Deployment environments
The following environments have been tested for deployment on edge devices:
- Java 8, including Raspberry Pi B and Pi2 B
- Java 7
- Android
Documentation
Please read the Documentation including Javadoc.