KEMBAR78
Not all open source is the same | PPTX
Not all open source
is the same
Bruce Momjian; VP, Postgres Evangelist
Marc Linster; Chief Technology Officer
© Copyright EnterpriseDB Corporation, 2021. All rights reserved.
2
Slides and recording will be made available
Submit questions via Zoom – will be answering at end
Welcome – Housekeeping Items
Agenda
1. EDB Introduction
2. Why should you care about more than the license?
3. The multiple parties and their concerns
4. Innovation and long-term viability
5. What makes Postgres so different?
6. Updated guidance for open source selection
Bruce Momjian - VP, Postgres Evangelist Marc Linster - Chief Technology Officer
1. EDB Introduction
2019
Challengers Leaders
Niche Players Visionaries
Ability
to
execute
Completeness of
vision
1986
The design
of PostgreSQL
1996
Birth of
PostgreSQL
2004
EDB
is founded
2020
EDB acquires
2nd Quadrant
Materialized
Views
Parallel
Query
JIT
Compilation
Heap Only
Tuples (HOT)
Serializable
Parallel Query
We’re database fanatics who care deeply
about PostgreSQL
• Recognized by Gartner Magic Quadrant for 7 years
• Enterprise PostgreSQL innovations
• PostgreSQL community leadership
2007
2ndQuadrant
launched
Logical
Replication
Transaction
Control
Hot
Standby
Generated
Columns
2. Why you should care about more than
the license?
● Traditional concern:
○ is the open source software license virulent?
○ Is there GPL content?
● New concerns driven by the overwhelming success of open source
○ Can I rely on it in production?
○ Can I build my product strategy on this software and this open source project?
○ Will somebody support me in production?
○ Will it still be there tomorrow?
○ Will it be leading edge innovative, bleeding edge innovative?
○ Will it turn into a zombie?
○ Will they change their license model?
○ Can I influence the roadmap?
○ …
3. The multiple parties
and their interests
4. Innovation and long-term viability
Putting a new focus on how to choose open source
License Concerns: GPL/L-GPL
Innovation
Viability
Cost
Innovation
● Is there actually a ‘community’ or is it just an individual hacking away?
● A single-company does not make a open source community!
● Is there a community-driven roadmap that can be influenced?
Viability: Stability and Reliability
● Who will support me when I go into production?
● Is there a SLA for CVEs and bug fixes?
● 99.99% uptime requires response in 15 - 60 minutes!
Cost
● Can/will the ‘community’ change the license model?
● Examples: MongoDB (2018 change from GNU AGPL to Server Side Public
License SSPL) and CockroachDB (2019 change from Apache 2.0 to a
version of BSL for all new major releases).
5. What Makes Postgres Different?
● A great eco system: Not company owned or dominated
● Strong governance, meritocracy, and independence
● Large community (Microsoft, Google, NTT, Fujitsu, CrunchyData,
Credativ, …)
● Agile model fosters innovation
The Postgres Ecosystem
• PostgreSQL is the World’s Most Advanced Open
Source Database
• ...produced by the PostgreSQL Global Development Group (PGDG)
• A much wider industry has been created around these two things, which
we refer to as the Postgres Ecosystem
• Postgres 13 (2020) release had contributions from 40+ companies, such
as: Adjust, Afilias, Amazon, Appen, Basefarm AS, Brandwatch, conova communications GmbH, Credativ,
Crunchy Data, Cybertec, Dalibo, Deriv.com, EDB, Facebook, Freelancer, Fujitsu, Google, HeteroDB, Huawei,
ILande, iovation, Microsoft, Minsait, MongoDB, NTT, Ongres, Open Standards Promotion Center, Paragon,
PeopleDoc, Playtech, Postgres Experts, Postgres Pro, Rakuten, SRA OSS, Swarm64, True Software, University of
Cambridge, VMWare, Yandex
PostgreSQL
Community
Hackers
PostgreSQL
Community
Hackers are only
the most visible tip
of the iceberg
PostgreSQL Stability
• Regular Annual Release Cycle
• Consistent Quality
• Backwards Compatibility
• Long Term 5 year Support
• Full Documentation
• Active Security Team
• Regular Maintenance
Agility in the Postgres Ecosystem
EXTENSIONs
•PostGIS, BDR, AGE, Citus ...
Value Added Distros
•EDB Postgres Adv Server, Timescale ...
Forks
•Greenplum, Redshift, Aurora ...
6. Updated guidance for open source
selection
● Understand the license model
● Is there really a open source community?
● Are multiple commercial entities involved with the community?
● Is the license model subject to change?
● Do you have a choice of support vendors and integrators?
● Can the support vendors really support you with CVE patches and bug
fixes?
● Is the community vibrant and innovative?
○ Slashdot: https://news.slashdot.org/story/20/09/19/033203/wheres-the-yelp-for-open-
source-tools
○ Blackduck: https://www.openhub.net/explore/projects
Not all open source
is the same
Bruce Momjian; VP, Postgres Evangelist
Marc Linster; Chief Technology Officer

Not all open source is the same

  • 1.
    Not all opensource is the same Bruce Momjian; VP, Postgres Evangelist Marc Linster; Chief Technology Officer
  • 2.
    © Copyright EnterpriseDBCorporation, 2021. All rights reserved. 2 Slides and recording will be made available Submit questions via Zoom – will be answering at end Welcome – Housekeeping Items
  • 3.
    Agenda 1. EDB Introduction 2.Why should you care about more than the license? 3. The multiple parties and their concerns 4. Innovation and long-term viability 5. What makes Postgres so different? 6. Updated guidance for open source selection
  • 4.
    Bruce Momjian -VP, Postgres Evangelist Marc Linster - Chief Technology Officer
  • 5.
    1. EDB Introduction 2019 ChallengersLeaders Niche Players Visionaries Ability to execute Completeness of vision 1986 The design of PostgreSQL 1996 Birth of PostgreSQL 2004 EDB is founded 2020 EDB acquires 2nd Quadrant Materialized Views Parallel Query JIT Compilation Heap Only Tuples (HOT) Serializable Parallel Query We’re database fanatics who care deeply about PostgreSQL • Recognized by Gartner Magic Quadrant for 7 years • Enterprise PostgreSQL innovations • PostgreSQL community leadership 2007 2ndQuadrant launched Logical Replication Transaction Control Hot Standby Generated Columns
  • 6.
    2. Why youshould care about more than the license? ● Traditional concern: ○ is the open source software license virulent? ○ Is there GPL content? ● New concerns driven by the overwhelming success of open source ○ Can I rely on it in production? ○ Can I build my product strategy on this software and this open source project? ○ Will somebody support me in production? ○ Will it still be there tomorrow? ○ Will it be leading edge innovative, bleeding edge innovative? ○ Will it turn into a zombie? ○ Will they change their license model? ○ Can I influence the roadmap? ○ …
  • 7.
    3. The multipleparties and their interests
  • 8.
    4. Innovation andlong-term viability Putting a new focus on how to choose open source License Concerns: GPL/L-GPL Innovation Viability Cost
  • 9.
    Innovation ● Is thereactually a ‘community’ or is it just an individual hacking away? ● A single-company does not make a open source community! ● Is there a community-driven roadmap that can be influenced?
  • 10.
    Viability: Stability andReliability ● Who will support me when I go into production? ● Is there a SLA for CVEs and bug fixes? ● 99.99% uptime requires response in 15 - 60 minutes!
  • 11.
    Cost ● Can/will the‘community’ change the license model? ● Examples: MongoDB (2018 change from GNU AGPL to Server Side Public License SSPL) and CockroachDB (2019 change from Apache 2.0 to a version of BSL for all new major releases).
  • 12.
    5. What MakesPostgres Different? ● A great eco system: Not company owned or dominated ● Strong governance, meritocracy, and independence ● Large community (Microsoft, Google, NTT, Fujitsu, CrunchyData, Credativ, …) ● Agile model fosters innovation
  • 13.
    The Postgres Ecosystem •PostgreSQL is the World’s Most Advanced Open Source Database • ...produced by the PostgreSQL Global Development Group (PGDG) • A much wider industry has been created around these two things, which we refer to as the Postgres Ecosystem • Postgres 13 (2020) release had contributions from 40+ companies, such as: Adjust, Afilias, Amazon, Appen, Basefarm AS, Brandwatch, conova communications GmbH, Credativ, Crunchy Data, Cybertec, Dalibo, Deriv.com, EDB, Facebook, Freelancer, Fujitsu, Google, HeteroDB, Huawei, ILande, iovation, Microsoft, Minsait, MongoDB, NTT, Ongres, Open Standards Promotion Center, Paragon, PeopleDoc, Playtech, Postgres Experts, Postgres Pro, Rakuten, SRA OSS, Swarm64, True Software, University of Cambridge, VMWare, Yandex
  • 14.
  • 15.
    PostgreSQL Community Hackers are only themost visible tip of the iceberg
  • 16.
    PostgreSQL Stability • RegularAnnual Release Cycle • Consistent Quality • Backwards Compatibility • Long Term 5 year Support • Full Documentation • Active Security Team • Regular Maintenance
  • 17.
    Agility in thePostgres Ecosystem EXTENSIONs •PostGIS, BDR, AGE, Citus ... Value Added Distros •EDB Postgres Adv Server, Timescale ... Forks •Greenplum, Redshift, Aurora ...
  • 18.
    6. Updated guidancefor open source selection ● Understand the license model ● Is there really a open source community? ● Are multiple commercial entities involved with the community? ● Is the license model subject to change? ● Do you have a choice of support vendors and integrators? ● Can the support vendors really support you with CVE patches and bug fixes? ● Is the community vibrant and innovative? ○ Slashdot: https://news.slashdot.org/story/20/09/19/033203/wheres-the-yelp-for-open- source-tools ○ Blackduck: https://www.openhub.net/explore/projects
  • 19.
    Not all opensource is the same Bruce Momjian; VP, Postgres Evangelist Marc Linster; Chief Technology Officer