EDB Postgres Application Integration

 

Service Overview

EDB Postgres Application Integration is a specialized service designed to provide expert support for organizations integrating or migrating their critical business applications to the EDB Postgres platform. The EDB resource will work hand-in-hand and collaboratively with your application development and operations teams throughout the entire integration and migration lifecycle, minimizing post-migration issues and accelerating time-to-value for the adoption of the EDB Postgres platform.

EDB will assess and size the schema conversion appropriately for our Small, Medium, and Large tiers.

 

Scope of Service

An EDB consultant will guide your team through the foundational migration execution, focusing on the following key activities:

  • Performance Tuning and Optimization: Analyze application workload characteristics, identify potential database bottlenecks, and implement performance-enhancing changes to both the application's data access layer (e.g., tuning queries, configuring ORMs, database drivers) and the EDB Postgres database configuration (e.g., adjusting memory, parallelism, and indexing strategies).
  • Scalability Design: Review application architecture and data modeling to ensure the solution handles current and future growth. This includes guidance and tuning on features like partitioning, connection pooling, and read/write distribution.
  • Application Code Review: Assist application teams in adapting and refactoring database interaction code (e.g., SQL statements, stored procedures, transaction logic) to leverage native Postgres features, ensuring compatibility and adhering to best practices for the EDB platform.

 

Deliverables

At the conclusion of the engagement, EDB will provide the following:

  • Comprehensive Performance Tuning Report: Including the following recommendations for:
    • Database related application code and data access layer changes
    • EDB Postgres configuration adjustments
    • Partitioning
    • Connection Pooling configurations
    • Read/write configurations
    • SQL Query Tuning

 

Roles and Responsibilities

EDB Project Manager:  Responsible for initial planning, task alignment, and project closeout.

EDB Senior Consultant: Technical Lead, responsible for execution of schema conversion, MTK deployment, configuration, validation and documentation.

Customer Team: Responsible for providing the main point of contact for requirements and prerequisites gathering. . Resources and Roles (or similar Technical Stakeholders) where input may be needed for the engagement include:

  • Database Administrator
  • System Architect
  • Application Owner(s)
  • Infrastructure Manager 
  • Network Administrator
  • Security Officer 

 

Assumptions

  • A project kickoff will be conducted to review the service scope and confirm the schedule.
  • This service is delivered remotely unless otherwise agreed.
  • EDB will provide a secure fileshare for customer to share prerequisites for analysis.
  • Customer will provide the names, title, email, phone number, and area of responsibility of those participating. One person will be designated as the main contact, and will be able to provide access to the people most knowledgeable about the topics to be discussed or examined. 
  • Customer will make appropriate personnel available to assist EDB in the performance of the services as needed and requested by EDB in a timely manner so as not to disrupt the project schedule. 
  • Customer will not provide Personal Data (as defined in applicable law). Customer agrees that it will work with EnterpriseDB to ensure that all such data is not provided.  
  • Customer will ensure timely access to all systems through screen sharing and experts including third parties as required. 
  • Customer will assign the appropriate resources with the appropriate privileges for the task being planned for any screen sharing sessions as needed throughout the engagement.
  • Customer will provide timely feedback on all deliverables. Deliverables without commentary within 5 business days will be deemed as delivered.
  • Schema and Object counts are unchanged and consistent with the migration assessment performed and documented by EDB.
  • Current Databases available for migration include: 
    • Oracle
    • MySQL
    • MariaDB
    • DB2
    • Sybase
    • SQL Server


Prerequisites

  • Customer will provide resource availability for workshop planning and a point of contact for coordination. 
  • Customer is responsible for gathering all data for analysis including:
    • DDL extracts 
    • Migration Questionnaires
    • SQL extracts or example application code
  • Customer is responsible for executing Application regression testing and Performance tuning, EDB will provide recommendations. 
  • Customer is responsible for providing all necessary internal design and project related documentation and requirements where EDB is required to analyze, operate, or modify customer implemented systems.
  • Customer will coordinate availability of Application teams to support any migration related queries.
  • Customer will make all Application related changes. EDB will provide recommendations only. 
  • Customer acknowledges that during the engagement there may be work required by Customer’s team related to configuration changes, performance, testing activities, and other efforts related to the Migration effort.  
  • Customer understands that moving from Customer’s current drivers to the latest Postgres drivers may require configuration changes and testing by the Customer during the engagement. 
  • Customer is responsible for upstream and downstream applications, APIs, data validation and testing requirements.
  • Customer understands that stored procedure updates may require configuration changes and testing by the Customer during the engagement. 
  • Customer will make no database and/or schema changes during the engagement period