Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Last revision Both sides next revision | ||
|
en:possible_integration_options_3_in_biostar_2 [2020/04/14 15:10] yjjung [What is different from BioStar 2 Device SDK?] |
en:possible_integration_options_3_in_biostar_2 [2020/04/29 08:27] yjjung [Summary of G-SDK] |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ==== Possible Integration Option 3 : G-SDK ==== | ==== Possible Integration Option 3 : G-SDK ==== | ||
| \\ | \\ | ||
| - | Download : https://github.com/biostar-dev/g-sdk/ \\ | + | In addition to the integration method using BioStar2 SW API or BioStar2 Device SDK, G-SDK is recently released as a new integration option for device management, user management, and log management. \\ |
| - | Manual : https://biostar-dev.github.io/g-sdk/ | + | |
| + | ==== What is G-SDK? ==== | ||
| + | G-SDK is one of the integration options for communicating with BioStar 2 devices. It is a lightweight, scalable, and cross-platform solution which will expedite your development. \\ | ||
| \\ | \\ | ||
| - | ==== Summary of G-SDK ==== | + | |
| - | ** Supported OS ** \\ | + | ==== How G-SDK works? ==== |
| - | Windows, x86/Arm Linux, Mac OS \\ | + | {{:en:gsdk_gsdkarchitecture.png?550|}} \\ |
| - | ** Maximum number of devices ** \\ | + | ** [Figure 1. G-SDK architecture] ** \\ |
| - | Up to 1,000 \\ | + | |
| - | ** Supported Language ** \\ | + | |
| - | C++, Java, Python, Go, Ruby, C#, Node.js, Android Java, Objective-C, PHP, Web \\ | + | |
| - | ** Supported API ** \\ | + | |
| - | The basic AC APIs except advanced features such as Zone, Wiegand, RS485 features. \\ | + | |
| - | ** Supported Device ** \\ | + | |
| - | All BioStar 2 devices \\ | + | |
| \\ | \\ | ||
| - | ==== What is G-SDK? ==== | + | G-SDK consists of Device Gateway in gRPC Server and gRPC Client Libraries. \\ |
| - | G-SDK is one of integration options for communicating with BioStar 2 devices. It is a lightweight, scalable, and cross-platform solution which will expedite your development. \\ | + | Based on gRPC, it supports many programming languages such as Java, C#, Python, Node.js, Go, etc.\\ |
| - | Based on gRPC, it supports many programming languages such as Java, C#, Python, Node.js, Go, etc. \\ | + | (gRPC (gRPC Remote Procedure Calls) is an open source remote procedure call (RPC) system initially developed at Google in 2015.) \\ |
| \\ | \\ | ||
| ** Multi-language support ** | ** Multi-language support ** | ||
| * Language-neutral IDL | * Language-neutral IDL | ||
| * Native client libraries | * Native client libraries | ||
| - | |||
| - | \\ | ||
| \\ | \\ | ||
| + | ** Device Gateway ** that communicates with BioStar 2 device can be run on a server or cloud. ** Core modules ** use BioStar 2 protocols and written by GO language.\\ | ||
| {{:en:gsdk_structure.png?400|}} \\ | {{:en:gsdk_structure.png?400|}} \\ | ||
| - | ** [Figure 1. Device Gateway Structure] ** \\ | + | ** [Figure 2. Device Gateway Structure] ** \\ |
| \\ | \\ | ||
| - | ** Device Gateway ** that communicates with BioStar 2 device can be run on a server or cloud. ** Core modules ** use BioStar 2 protocols and written by GO language.\\ | ||
| - | |||
| ==== What is different from BioStar 2 Device SDK? ==== | ==== What is different from BioStar 2 Device SDK? ==== | ||
| Line 37: | Line 30: | ||
| Let's take a look for an easy comparison between BioStar 2 Device SDK and G-SDK. \\ | Let's take a look for an easy comparison between BioStar 2 Device SDK and G-SDK. \\ | ||
| {{:en:gsdk_comparison.png?600|}} \\ | {{:en:gsdk_comparison.png?600|}} \\ | ||
| - | ** [Figure 2. BioStar 2 Device SDK vs G-SDK] ** \\ | + | ** [Figure 3. BioStar 2 Device SDK vs G-SDK] ** \\ |
| \\ | \\ | ||
| \\ | \\ | ||
| Line 44: | Line 37: | ||
| This is a limitation of BioStar 2 Device SDK due to the structure. \\ | This is a limitation of BioStar 2 Device SDK due to the structure. \\ | ||
| {{:en:gsdk_devicesdkstructure.png?900|}} \\ | {{:en:gsdk_devicesdkstructure.png?900|}} \\ | ||
| - | ** [Figure 3. BioStar 2 Device SDK structure] ** \\ | + | ** [Figure 4. BioStar 2 Device SDK structure] ** \\ |
| \\ | \\ | ||
| Line 55: | Line 48: | ||
| {{:en:gsdk_gsdkstructure.png?900|}} \\ | {{:en:gsdk_gsdkstructure.png?900|}} \\ | ||
| - | ** [Figure 4. G-SDK structure] ** \\ | + | ** [Figure 5. G-SDK structure] ** \\ |
| \\ | \\ | ||
| Line 66: | Line 59: | ||
| Master Gateway helps you handle multiple Device gateways and it can be deployed on a cloud server or provide mobile direct accessibility too. \\ | Master Gateway helps you handle multiple Device gateways and it can be deployed on a cloud server or provide mobile direct accessibility too. \\ | ||
| {{:en:gsdk_mastergateway.png?600|}}\\ | {{:en:gsdk_mastergateway.png?600|}}\\ | ||
| - | ** [Figure 5. Device Gateway vs Master Gateway] ** \\ | + | ** [Figure 6. Device Gateway vs Master Gateway] ** \\ |
| \\ | \\ | ||
| Line 78: | Line 71: | ||
| \\ | \\ | ||
| + | ==== Summary of G-SDK ==== | ||
| + | ** Supported OS ** \\ | ||
| + | Windows, x86/Arm Linux, Mac OS \\ | ||
| + | \\ | ||
| + | ** Recommended Requirements **\\ | ||
| + | 2.0GHz CPU, 4GB(32bit) or 8GB(64bit) RAM \\ | ||
| + | \\ | ||
| + | ** Minimum Requirements **\\ | ||
| + | 1.0GHz CPU, 1GB(32bit) or 2GB(64bit) RAM\\ | ||
| + | \\ | ||
| + | ** Maximum number of devices ** \\ | ||
| + | Up to 1,000 \\ | ||
| + | \\ | ||
| + | ** Supported Language ** \\ | ||
| + | C++, Java, Python, Go, Ruby, C#, Node.js, Android Java, Objective-C, PHP, Web \\ | ||
| + | \\ | ||
| + | ** Supported API ** \\ | ||
| + | The basic AC APIs(Access control, User management, Event log etc) except advanced features such as Zone, Wiegand, RS485 features. \\ | ||
| + | \\ | ||
| + | ** Supported Device ** \\ | ||
| + | All BioStar 2 devices \\ | ||
| + | \\ | ||
| + | ** Download ** \\ | ||
| + | https://github.com/biostar-dev/g-sdk/ \\ | ||
| + | \\ | ||
| + | ** Manual ** \\ | ||
| + | https://biostar-dev.github.io/g-sdk/\\ | ||
| + | \\ | ||
| + | \\ | ||