Skip to content

11.1 Choose an Integration Method

Choose an integration method for the project language, ingestion pattern, and deployment environment.

Selection Criteria

RequirementFirst option to consider
Native C/C++ collectorSQLCLI
ODBC manager/DSN applicationODBC
Java/SpringJDBC
Python analytics/automationmachbaseapi
C#/VB.NET.NET Connector
Go collector/serviceNative machgo or database/sql
Node.js/TypeScript backend@machbase/ts-client
R analyticsMachbase ODBC driver with RODBC
Bulk file ingestion/exportmachloader, csvimport, csvexport
Continuous bulk TAG/LOG ingestionThe chosen SDK’s Append API

Do not connect a browser directly to port 5656. Execute queries in a backend and return only the required results.

Decision Sequence

  1. Choose an official driver maintainable in the application language.
  2. Check port 5656 connectivity, operating system support, and runtime compatibility.
  3. Identify required SQL, prepared statement, Append, and transaction features.
  4. Check actual support in the SDK Feature Matrix.
  5. Round-trip sample timestamps, NULLs, numbers, and strings.
  6. Load-test target row sizes, concurrent connections, and batch sizes.

Do not choose a driver on Append support alone. Verify flush latency, server error responses, reconnection, and failed-row handling in the actual SDK. For TRANSACTION DML, check explicit transaction support. Do not assume TAG/LOG Append shares its rollback scope.

Detailed Documentation by Topic

TopicDetailed documentation
SDK installation, connections, APIs, complete codeSDK pages in this chapter
Shared authentication, binding, transactions, retriesCommon Integration Concepts
SDK feature supportSDK Feature Support
SQL, configuration, command-line detailsChapter 16 Reference
Choose ingestion/export methodsData Ingestion and Export

After choosing an integration method, run its SDK installation and connection examples. Check both documented versions and actual deployment artifacts for feature support.

Last updated on