Lock in $30 Savings on PRO—Offer Ends Soon! ⏳

Why Application Developers Love Postgres | Igni...

Why Application Developers Love Postgres | Ignite 2019 | Craig Kerstiens

Postgres is ranked as one of the “most-loved” databases by developers—and is the frequent choice for developers building new applications whether on-premises or in the cloud. We look at what makes the open source Postgres database unique among relational databases, from foreign data wrappers to rich indexes and datatypes to JSONB to Postgres extensions including PostGIS and Citus. And, we explore the types of modern frameworks Postgres is a good fit for, including Django and Rails. If you are looking to leverage Postgres and you don’t want to have to get a Ph.D. in database technologies, come learn why Postgres is leading the resurgence of relational databases among app developers.

Azure Database for PostgreSQL

November 06, 2019
Tweet

More Decks by Azure Database for PostgreSQL

Other Decks in Technology

Transcript

  1. Postgres OPEN SOURCE DATABASE SAME ROOTS AS MANY OTHERS NO

    SINGLE OWNER RELEASES YEARLY WITH NEW MAJOR RELEASE
  2. What’s in the box Feature rich Data types Advanced indexing

    Full text search Geospatial support JSON Extensions Vast ecosystem
  3. INSERT INTO products (name, attributes) VALUES ( 'Geek Love: A

    Novel’, 'author => "Katherine Dunn", pages => 368, category => fiction’ );
  4. INSERT INTO products (name, attributes) VALUES ( 'Geek Love: A

    Novel’, 'author => "Katherine Dunn", pages => 368, category => fiction’ ); SELECT name, attributes->'author' as author FROM products WHERE attributes->'category' = 'fiction'
  5. INSERT INTO products (name, attributes) VALUES ( 'Geek Love: A

    Novel’, 'author => "Katherine Dunn", pages => 368, category => fiction’ ); SELECT name, attributes->'author' as author FROM products WHERE attributes->'category' = 'fiction'
  6. INSERT INTO products (name, attributes) VALUES ( 'Geek Love: A

    Novel’, 'author => "Katherine Dunn", pages => 368, category => fiction’ ); SELECT name, attributes->'author' as author FROM products WHERE attributes->'category' = 'fiction’; CREATE INDEX idx_products ON products USING gin(attributes);
  7. Why People Azure Database for PostgreSQL Global reach Security Scale

    up & out Built-in HA Compliance Intelligent performance Easy ecosystem integration Extension support Extensions JSONB Full text search Geospatial support Rich indexing
  8. Skills you already have DBAs know how to administer Not

    another thing to learn, lower overhead to bring online Frameworks already work with it Again not a new thing to learn, already works with your tools Easy to hire for Hiring is hard enough, don’t make it harder
  9. Postgres for lower TCO Open source meaning no expensive licensing

    SQL that works well to replace existing SQL applications Not a new shiny type of data store, you already have the skills to support
  10. All these build on each other FOR DEVELOPERS: RICH FEATURE

    SET AND CONTINUAL INNOVATION FOR COMPANIES: ALREADY KNOWN TOOL WITH EXISTING SKILLS FOR ENTERPRISES: ABILITY TO REDUCE COST
  11. APPLICATION BEGIN; UPDATE SET WHERE COMMIT; campaigns start_date = '2018-03-17'

    company_id = 'Pat Co'; METADATA COORDINATOR NODE WORKER NODES W1 W2 W3 … Wn BEGIN; UPDATE Campaigns_2012 SET …; COMMIT; How Hyperscale (Citus) shards Postgres UPDATE
  12. How Hyperscale (Citus) scales out Postgres APPLICATION SELECT FROM GROUP

    BY company_id, avg(spend) AS avg_campaign_spend compaigns company_id; METADATA COORDINATOR NODE WORKER NODES W1 W2 W3 … Wn SELECT company_id sum(spend), count(spend) … FROM campaigns_2009 … SELECT company_id sum(spend), count(spend) … FROM campaigns_2001 … SELECT company_id sum(spend), count(spend) … FROM campaigns_2017 … DISTRIBUTED AGGREGATE
  13. Thanks! FOR DEVELOPERS: RICH FEATURE SET AND CONTINUAL INNOVATION FOR

    EVERYONE: ALREADY KNOWN TOOL WITH EXISTING SKILLS FOR ENTERPRISES: ABILITY TO REDUCE COST