Which Postgres is Right for You? - Part 2

© 2016 EDB. All rights reserved. 1
So many Options, but
which Postgres is right for you?
Part 2 of 3

•  The Enterprise Challenge
•  Enterprise Postgres
•  Evaluation guidelines
•  Scenarios
−  PostgreSQL without commercial support
−  Creating your own PostgreSQL fork
−  EDB Postgres Standard
•  Summary
•  Resources
Agenda

The Enterprise Challenge
Little Money For
New Initiatives
Competitive
Disadvantage
$
t
$
Revenue
DBMS
Customer
Engagement

The Enterprise Challenge:
Open Source to the Rescue
35% 80% 80%
Software infrastructure
budget on DBMSs (1)
In-House applications
candidates to move off
expensive DBMSs (2)
Cost savings (3)
(1) Gartner, Forrester and EDB analysis
(2) The State of Open-Source RDBMS, 2015, Gartner, April 2015
(3) The State of Open-Source RDBMS, 2015, Gartner, April 2015; EDB analysis of customer experiences and market prices

POSTGRES
innovation
ENTERPRISE
reliability
24/7
support
Services
& training
Enterprise-class
features, tools &
compatibility
Certifications
Product
road-map
Control
Thousands
of developers
Fast
development
cycles
Low cost
No vendor
lock-in
Advanced
features
Enabling commercial
adoption of Postgres
Enterprise Postgres

Enterprise Postgres: EDB Postgres Platform

•  PostgreSQL without
commercial support
•  Creating your own
PostgreSQL fork
•  EDB Postgres Standard
•  PostgreSQL without
commercial support
•  PostgreSQL with a consulting
partner
•  EDB Postgres Enterprise
Scope
Today's webinar June webinar

Evaluation guidelines: Risks
Technical Risks Business Risks
Capabilities
Roadmap
Tech Support
Time to Market
Cost
Relationships
Software Control

•  Mission-Critical Apps
•  Non-Mission-Critical Apps
•  Non-Production Apps
•  Time-to-Market Sensitivity
•  High Security and Performance
•  Oracle Compatibility
•  Access to Source Code
Evaluation guidelines: Usage Profiles

User works directly with community PostgreSQL binaries
without commercial assistance and works entirely within
the community participation process.
Scenario:
PostgreSQL without commercial support

Pros
•  Mature, capable
RDBMS
•  SQL standards
compliance
•  OLTP, READ,
mixed workloads
•  Unstructured
data support
Cons
•  Performance: Limited partitioning capabilities,
no workload manager, limited performance
diagnostics
•  Security: No SQL injection attack protection, no
password policy management, no enhanced
auditing
•  Limited developer usability and features
•  No integrated tool suites for monitoring,
management, tuning, high availability, backup
and recovery, or migration
•  No Oracle compatibility
Capabilities

Pros
•  A public wish list is
maintained by the Postgres
community
•  Your organization may
contribute code for features
Cons
•  Little insight into Community
database engineering
•  Little to no influence over
database roadmap
•  No guaranteed acceptance or
timelines for code submitted
Roadmap

Pros
•  Multiple community forums/
mailing lists for free technical
support
•  Postgres developers fix bugs
on an ongoing basis
Cons
•  No dedicated technical support
team
•  No service level agreements
(SLAs)
•  No hot fixes
•  No issue tracking portal
•  No regionally based support
Tech Support

Pros
•  No procurement time
Cons
•  Slower learning curve without
assistance
•  Longer time to set up, configure,
and tune database and tools
•  More difficult and therefore longer
migration from Oracle due to code
rewrites or refactoring
Time to Market

Pros
•  No upfront license fees
•  No maintenance/support fees
Cons
•  Cost for internal resources to
manage and support
•  Costs for training
•  Unpredictable costs for downtime
or slow performance
Cost

Pros
•  Flexibility to source vendors on
an as-needed basis
Cons
•  No commercial responsiveness or
incentives for mutual success
•  No direct access to Postgres
engineering resources
Relationships

Pros
•  Access to source
code
•  Liberal Postgres
license avoids
software
contamination
Cons
•  No influence over release schedules for the
database
•  Unknown levels of community QA testing
•  Self-reliability to manage software updates
and security alerts
•  Uncoordinated and inconsistent releases,
documentation, support and quality across
tools
•  No extended lifecycle support available
•  Potential public exposure of your
confidential and competitive information via
community interactions
Software Control

User takes the PostgreSQL source code as a starting
point for developing own version of PostgreSQL while
creating and maintaining its own development effort.
Scenario:
Creating your own PostgreSQL fork

Pros
•  Mature, capable
RDBMS
•  SQL standards
compliance
•  OLTP, READ, mixed
workloads
•  Unstructured data
support
•  Well-structured and
well-documented
source code
Cons
•  Performance: Limited partitioning
capabilities, no workload manager, limited
performance diagnostics
•  Security: No SQL injection attack protection,
no password policy management, no
enhanced auditing
•  Limited developer usability and features
•  No integrated tool suites for monitoring,
management, tuning, high availability,
backup and recovery, or migration
•  Possible compromising of core code/
features
Capabilities

Pros
•  Knowledge of all internal
database engineering efforts
•  High degree of influence over
the database roadmap
Cons
•  Must refactor fork with each new
community release or forego new
community features
•  Changes to source code may
break existing Postgres features in
your fork
•  Possible inconsistencies and
incompatibilities with other open
source solutions and platforms
Roadmap

Pros
•  Multiple community forums/
mailing lists for free technical
support
•  Postgres developers fix bugs
on an ongoing basis
Cons
•  No dedicated technical support
team
•  No service level agreements
(SLAs)
•  No hot fixes
•  No issue tracking portal
•  No regionally based support
•  No community support for
modified source code
Tech Support

Pros
•  No procurement time
•  Shorter development cycle
for customizations
•  After clearing initial learning
curve, development cycles
accelerate
Cons
•  Longest learning curve without
assistance and >1M lines of code
•  Longer time to set up, configure,
and tune database and tools
•  Long process to recruit, train and
integrate Postgres developers into
operations
Time to Market

Pros
•  No upfront license
fees
•  No maintenance/
support fees
Cons
•  Cost for internal resources to manage and
support
•  Costs for internal developers and support
•  Costs for training
•  Unpredictable costs for downtime or slow
performance
•  Costs for creating and maintaining a
software development infrastructure
including testing and deployment
•  Costs to refactor forked version to any new
Postgres release version including security
and bug fixes
Cost

Pros
•  Flexibility to source vendors
on an as-needed basis
Cons
•  No commercial responsiveness or
incentives for mutual success
•  No direct access to Postgres
engineering resources
•  Potential difficulty in matching
vendor abilities to requirements
•  Inconsistent or unknown
availability of internal technical
resources
Relationships

Cons
•  Self-reliability to manage software
updates and security alerts
•  Uncoordinated and inconsistent
releases, documentation, support
and quality across tools or own
development leading to potential
incompatibility with community
tools
•  Potential public exposure of your
confidential and competitive
information via community
interactions
Software Control
Pros
•  Access to source code
•  Control over release schedule
•  No external lifecycle
limitations
•  Control over software
development and QA cycles
•  Liberal Postgres license
avoids software
contamination
•  Control over intellectual
property

Scenario:

User works with certified PostgreSQL binaries and with
EDB to enhance their interactions and input with the
community while getting all key mission critical tools from
EDB.
Scenario:
EDB Postgres Standard

Pros
•  Mature, capable RDBMS
•  SQL standards compliance
•  OLTP, READ, mixed
workloads
•  Unstructured data support
•  Integrated mission-critical tool
suites for monitoring,
management, tuning, high
availability, backup and
recovery, and Oracle
migration
Cons
•  Performance: Limited partitioning
capabilities, no workload
manager, limited performance
diagnostics
•  Security: No SQL injection attack
protection, no password policy
management, no enhanced
auditing
•  Limited developer usability and
features
Capabilities

Pros
•  Insight into community
database engineering
•  Some influence over the
database roadmap
•  Excellent insight into EDB
engineering activity
•  Influence on roadmap for
mission-critical tool suites
Cons
•  Insight into community activities
does not mean EDB controls
feature development of the
community database
•  Uncertainty about acceptance and
lead times of customer features
into community code
•  Limited influence over community
database release schedule
Roadmap

Cons
•  None
Tech Support
Pros
•  Service level agreements (SLAs)
•  Escalation support by EDB engineers
backed by Postgres community leaders
working at EDB
•  Hot fixes available “out of band” from
Postgres release schedule
•  Issue tracking portal
•  Technical Account Management
available
•  Community forums/mailing lists

Time to Market
Pros
•  EDB Consultants to assist with
general learning curve
•  Access to Postgres resources
for technical support, training,
and consulting including
assistance with set up and
configuration of database
•  Bundled with integrated tool
suites for management,
migration and integration
Cons
•  Procurement time required to
source vendor and implement
working relationship

Cost
Pros
•  No upfront license fees
•  No upfront maintenance/
support fees
•  Significant cost savings over
traditional vendors
Cons
•  Annual subscription fee
•  Unpredictable costs to
compensate for features only
available in EDB Postgres
Enterprise e.g. performance
improvements

Relationships
Pros
•  Access to the highest concentration of
Postgres resources and services worldwide
•  Full service provider for software, support,
maintenance, tools, training and
certification, and consulting
•  Commercial responsiveness and incentives
for mutual success
•  Expertise supporting a global brand 24x7
•  Most extensive network of business
partnerships
•  Gartner Magic Quadrant Leader
Cons
•  Some dependence
on EDB for mission-
critical tool suites

Pros
•  Access to database source code
•  Hot fixes
•  Influence over release
schedules for minor updates
•  Influence over roadmap for
mission-critical tool suites
•  Reliable and documented testing
of all database and tool suite
releases
•  Automated software updates,
alerting and management
•  Extended lifecycle support may
be available
Cons
•  Major database releases tied to
community schedule
•  No access to source code for tool
suites
Software Control

Scenario:

Comparison
EDB Postgres
Standard
Creating your own
PostgreSQL fork
PostgreSQL without
commercial support

•  Postgres solution choice depends on usage and
willingness to take risks
•  Mission-critical workloads require an enterprise
platform
•  EDB Postgres subscriptions reduce technical and
business risks
•  Save money and time with EDB Postgres
Summary

Whitepaper: Which Postgres is Right for Me
www.enterprisedb.com/Which-Postgres-Is-Right-For-Me
PostgreSQL Community Wish List
https://wiki.postgresql.org/wiki/Todo
Gartner: The State of Open-Source RDBMSs, 2015
info.enterprisedb.com/Gartner-MQ-2015.html
Download EDB Postgres Advanced Server
www.enterprisedb.com/downloads
To learn more contact us at sales@enterprisedb.com.
Resources

Resources:
Getting Started with EDB Postgres
Comprehensive bundle of a
Developer license, Training &
Consulting, helping to make
development projects successful.
•  EDB Postgres Developer Subscription
•  On-Demand Training (2 classes)
•  Consulting (2 days-remote)
EDB Developer Kick Start
Comprehensive package for
groups of 2-4 developers & DBAs
in support of mission-critical
production Postgres
implementations, along with
expert guidance for Year 1.
•  EDB Postgres Developer Subscription
•  On-Demand Training (4 classes)
•  Consulting (5 days, remote)
•  RemoteDBA (1 year, 8 instances)
EDB Postgres Group Success with RemoteDBA

World-class training that delivers
the education, experience, and
excellence needed to be
successful
•  Training that fits your learning needs:
Classroom, Online, and Onsite.
•  eSubscriptions - access to all on-demand
Training in an annual subscription
•  DBA and developer course tracks available
•  Courses cover administration, migration,
performance tuning and more
Resources:
Postgres Skills Development Assistance
EDB is the industry-recognized
global standard for Postgres
Certification
Develop and validate in-house
Postgres skill and expertise
•  DBMSs covered include:
−  PostgreSQL
−  EDB Postgres Advanced Server
•  Associate & Professional levels
•  Convenient online exams
EDB Training provides:
EDB Certification provides:

Which Postgres is Right for You? - Part 2

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Viewers also liked

Viewers also liked (14)

Similar to Which Postgres is Right for You? - Part 2

Similar to Which Postgres is Right for You? - Part 2 (20)

More from EDB

More from EDB (20)

Recently uploaded

Recently uploaded (20)

Which Postgres is Right for You? - Part 2