Postgres Architectural Design

Service Overview

Partner with an EDB Solution Architect to design, optimize, or expand your Postgres architecture. We analyze your database, operational, infrastructure, and solution requirements to build a roadmap for success, whether for a single application or a complex enterprise project.

This engagement is designed for self-managed deployments, covering both on-premises and cloud environments.

To best fit your specific needs, we offer three tiers of design engagement:

Scope of Services

Our architects gather information on your environmental requirements and operational practices to recommend viable architectures. Key focus areas include:

• Availability & Continuity: Defining tiers, operational expectations, and disaster recovery strategies
• Infrastructure & Tooling: Reviewing existing/target infrastructure and tooling options
• Security & Compliance: Addressing security requirements and data segmentation plans
• Workload Analysis: Evaluating application design patterns and workload characteristics

For Medium and Large engagements, we define Strategies and Standard Operating Procedures (SOPs). We design workflows for critical scenarios such as:

• Failover/Switchover: Planned switchovers, primary/standby and data center failures

• Recovery: Point-in-time recovery (PITR), full backups, and restoring failed nodes
• Monitoring: Identify key metrics and thresholds for optimal database performance
• Maintenance: Minor/Major upgrades, patching, and application connections
• Resilience: Data center failures (for Large/Multi-DC scopes) and multiple node failures

• Security: Auditing and Role Based Access Controls

Deliverables

At the conclusion of the engagement, EDB will provide:

Comprehensive Architectural Design Document: A detailed document providing a comprehensive summary of your planned use case and proposed architecture identifying:

• EDB-supported software recommendations for:
  • Postgres Version
  • High Availability
  • Backup and Recovery
  • Monitoring
  • Connection Pooling
• Physical Layout for all Database and Database tooling nodes

• CPU core, Memory and Storage sizing  based on your proposed use case

For Medium/Large engagements

• Strategies and Standard Operating Procedures for:
  • Failover/Switchover and DR scenarios
  • Backup and Recovery
  • Monitoring
  • Patching
  • Major/Minor Upgrades
  • Auditing
  • User Management

Report Review: A review of the report and findings with the customer via web conference

Roles and Responsibilities

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

EDB Solution Architect: Technical Lead, responsible for workshop delivery, preparation, validation and documentation of Architecture Design and Strategies. 

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

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

Assumptions

• A project kickoff will be conducted to review the service scope and confirm the schedule
• This service is delivered remotely unless otherwise agreed
• 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.
• The proposed design and sizing are based strictly on Customer-provided workload metrics. EDB does not guarantee performance outcomes if actual workloads deviate from provided prerequisites.

Prerequisites

• Customer will provide resource availability for workshop planning and a point of contact for coordination. 
• Customer is responsible for providing all necessary internal design and project related documentation and requirements where EDB is required to analyze, , evaluate, or provide recommendations for customer implemented systems. This includes, but is not limited to:
  • RTO/RPO Requirements
  • Application Read/Write Ratios, Transactions Per Second (TPS), and estimated workload 
  • Estimated Database Size and Growth Rate