Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Table of Contents
minLevel1
maxLevel7

What is MachLake?

MachLake is

...

You can store a lot of sensor IoT data as well as extract so fast through Rest API. Moreover, you can share your data in your lake to anyone who want to navigate or download it.

...

an API as a Service that provides a Micro-Data Lake.

The concept of Micro-Data Lake is a storage representing a data space that stores data of the edge with the same structure on Edge Computing.

There are times when all data cannot be stored at the edge due to various limitations of data processing required in the customer's Edge Computing environment, or must inevitably be transmitted to the cloud for data sharing.

In this case, MachLake can solve the cost and difficulty of processing your data very easily. This is because Micro-Data Lake in the cloud eliminates the need to install, maintain, or upgrade

...

separate software for IoT data processing at the edge.

MachLake allows users to significantly lower the cost of maintaining huge amounts of IoT sensor data, which is very useful for their customers' application development.

...

This is implemented through Machbase, the world's fastest time series DBMS which is ranked #1 on TPC.org and guarantee you the best performance.

Use cases for MachLake

...

Machlake

...

User is the entity that manages multiple lakes. You can create as many lakes as you want, and you can store different types of sensor data indefinitely.

Lake

Lake is a repository that holds sensor data structures called tags and actual data called values. When data is inserted into this lake, the tag name which symbolize the name of the sensors and values are saved together. A typical single data is a set of value composed of (tag name, time, numerical value)

Tag

Tag is an object representing a specific sensor to be stored. Typically this tag has a "name" in the form of a string. And, this "name" is used as a delimiter to indicate where the actual data to be stored in the lake belongs.

For example, if there are two (A, B) sensors that indicate temperature in a specific device, the two tags will have the names of A and B respectively.

This tag must have a name expressed as a string, and if the user wants, more information can be given to the tag through additional columns.

Value

Value must have a time and numeric value that actually constitutes the tag. Therefore, the minimum column input to Lake consists of tag name, input time, and numeric value, respectively. However, in some cases, the value of this tag is not one, but several, so the extended column can be configured as the user wants. However, the first tag value must be in the form of a number.

Different types of Lakes

...

Service Lake

Service lake is the basic lake created by the user and where all operations on data are possible. You can backup a lake and share it to any user.

(Lake-A, Lake-B, Lake-C)

Backup Lake

Backup lake refers to data stored in a separate, inexpensive storage for long-term storage of data that is not needed right now. User can't read any data in Backup lake. However, this backup lake can leverage the mount capabilities it provides to create a mount lake to instantly extract and visualize data.

(Lake A1, A2, C1, C2, C3)

Mounted Lake

Mount lake is a temporary lake where the backed-up lake is mounted in a form from which data can be immediately extracted. Because the mount process is very fast, users can easily search for and utilize the past lakes backed up through this feature.

(Mounted Lake-A1, Mounted Lake-C3)

Shared Lake

Share Lake is a lake created for the purpose of easily sharing data between users. The desired sensor and time range data can be easily shared with users registered in MachLake, and can be easily shared even in the Internet space through a simple web link.

(Share Lake-B, Shared Mounted Lake-A1)can easily and quickly integrate and utilize data from most edge devices, which can greatly help in the development of user applications. Depending on the number of edge devices used and the size of data generated, various plans can be used to manage data in 1:1 or N:1 or N:M combination between edge devices and Micro Data-Lake.

Smart Building Management System

Machlake excels at integrating and managing IoT data originating from Edge devices, and is very easily integrated into user applications through Rest API. In addition, by utilizing various plans according to the number of edge devices used and the size of data generated, Edge IoT data can be managed in 1:1 or N:1 or N:M combination between edge devices and Micro Data-Lake.

Smart Robot Management System

The data generated by many robots such as logistics and transportation is very important for not only checking the health of the equipment, but also for the progress of work and detection of abnormalities.
Although it is possible to respond in a local environment through the establishment of Edge Computing, it is very important to transmit and integrate data to Micro Data-Lake for macroscopic insight and management of multiple robot movements.

Mobile Edge Computing System

A moving Edge machine's real-time interaction with its road environment is critical. In addition, long-term operation history and data collection for failure detection have a significant impact on business continuity.
Micro Data-Lake is a service optimized for large-scale IoT data management at the edge, and it helps customers to operate their business quickly and quickly at low cost in managing multiple vehicles.

Network Gateway Management System

In order to manage the status of devices in charge of network processing in different regions, data is periodically transmitted to the designated Micro Data-Lake. Through this, end-user applications can monitor and visualize data from multiple Micro Data-Lakes that retain data, which can greatly help improve business efficiency.