GuidesEcosystem

Development Clients & SDKs

Tacnode's PostgreSQL compatibility ensures seamless integration with your existing development tools and workflows. Whether you're building applications in Java, Python, Go, or other languages, you can leverage familiar drivers, ORMs, and development practices.

Supported Programming Languages

Java Ecosystem

Framework/DriverSupport LevelExample Guide
Hibernate ORM✅ Fully SupportedCRUD Operations
MyBatis✅ Fully SupportedComing soon
Spring Data JPA✅ Fully SupportedComing soon
JDBC✅ Fully SupportedComing soon
jOOQ✅ Fully SupportedComing soon

Python Ecosystem

Framework/DriverSupport LevelExample Guide
SQLAlchemy✅ Fully SupportedCRUD Operations
psycopg2✅ Fully SupportedComing soon
psycopg3✅ Fully SupportedComing soon
Django ORM✅ Fully SupportedComing soon
FastAPI✅ Fully SupportedComing soon
asyncpg✅ Fully SupportedComing soon

Go Ecosystem

Framework/DriverSupport LevelExample Guide
GORM✅ Fully SupportedCRUD Operations
lib/pq✅ Fully SupportedComing soon
pgx✅ Fully SupportedComing soon
sqlx✅ Fully SupportedComing soon

Node.js Ecosystem

Framework/DriverSupport LevelStatus
pg (node-postgres)✅ Fully SupportedComing soon
Sequelize✅ Fully SupportedComing soon
TypeORM✅ Fully SupportedComing soon
Prisma✅ Fully SupportedComing soon
Knex.js✅ Fully SupportedComing soon

.NET Ecosystem

Framework/DriverSupport LevelStatus
Npgsql✅ Fully SupportedComing soon
Entity Framework Core✅ Fully SupportedComing soon
Dapper✅ Fully SupportedComing soon

Migration Guide

From PostgreSQL Applications

If you're already using PostgreSQL, migration to Tacnode is straightforward:

  1. Update connection string - Replace your PostgreSQL endpoint with Tacnode cluster details
  2. Update credentials - Use your Tacnode username and password
  3. Test compatibility - Verify your queries work as expected (99%+ compatibility)

Example Connection String Update:

# Before (PostgreSQL)
postgresql://user:password@localhost:5432/mydb

# After (Tacnode)
postgresql://user:password@your-cluster.tacnode.io:5432/mydb

From Other Database Systems

Migrating from MySQL, SQL Server, Oracle, or other databases requires additional steps:

1. Schema Migration

  • Export your existing schema using native tools
  • Convert DDL statements to PostgreSQL-compatible syntax
  • Handle data type differences between database systems
  • Update entity classes to match new schema if needed

2. Configuration Updates

  • Update database URLs to use PostgreSQL format
  • Change driver dependencies in your project
  • Update dialect configurations in ORM frameworks

3. Driver and Dialect Changes

Java/Hibernate Example:

<!-- Before (MySQL) -->
<dependency>
    <groupId>mysql</groupId>
    <artifactId>mysql-connector-java</artifactId>
</dependency>
 
<!-- After (Tacnode/PostgreSQL) -->
<dependency>
    <groupId>org.postgresql</groupId>
    <artifactId>postgresql</artifactId>
</dependency>
# Before (MySQL dialect)
hibernate.dialect=org.hibernate.dialect.MySQLDialect
 
# After (PostgreSQL dialect)
hibernate.dialect=org.hibernate.dialect.PostgreSQL10Dialect

Python/Django Example:

# Before (MySQL)
DATABASES = {
    'default': {
        'ENGINE': 'django.db.backends.mysql',
        'NAME': 'myproject',
        'USER': 'myuser',
        'PASSWORD': 'mypassword',
        'HOST': 'localhost',
        'PORT': '3306',
    }
}
 
# After (Tacnode/PostgreSQL)
DATABASES = {
    'default': {
        'ENGINE': 'django.db.backends.postgresql',
        'NAME': 'myproject',
        'USER': 'myuser',
        'PASSWORD': 'mypassword',
        'HOST': 'your-cluster.tacnode.io',
        'PORT': '5432',
    }
}

Best Practices

Connection Management

  • Use connection pooling for production applications
  • Configure appropriate timeouts for your use case
  • Implement retry logic for transient network issues
  • Monitor connection health and metrics

Performance Optimization

  • Use prepared statements to improve query performance
  • Implement proper indexing strategies
  • Batch operations when inserting large datasets
  • Leverage Tacnode's distributed architecture for parallel processing

Security Considerations

  • Use SSL/TLS connections in production
  • Implement proper authentication and authorization
  • Avoid SQL injection with parameterized queries
  • Follow the principle of least privilege for database users

Development Workflow

  • Use migrations for schema changes
  • Implement comprehensive testing with database fixtures
  • Use ORM features for type safety and productivity
  • Monitor query performance during development

Getting Started

  1. Choose your programming language from the supported ecosystems above
  2. Install the PostgreSQL driver for your chosen framework
  3. Configure your connection using Tacnode cluster details
  4. Follow the specific integration guide for detailed examples
  5. Test your integration with sample queries and operations

The familiar PostgreSQL interface means you can leverage existing knowledge, tools, and libraries while gaining the benefits of Tacnode's distributed, cloud-native architecture.