This document discusses how PostgreSQL can enable digital transformation. It notes that digital transformation involves developing new types of products/services rather than just enhancing existing systems, moving to microservices architectures, and adopting data platforms. It then outlines how PostgreSQL supports these changes through its document store capabilities, foreign data wrappers for integration with other data sources, replication server for high availability, and containerized deployment options. Case studies are presented showing how enterprises have realized performance improvements, cost savings, and near real-time data exchange using PostgreSQL's unified relational and non-relational features.
3. Digital Transformation?
3
New Paradigms
• develop new types of products and services, rather than simply
enhancing and expanding existing systems
Monolithic to Micro
• Moving from traditional long cycle big monolithic software programs to
agile short cycle micro-services
Data Platforms
• Adopt data platforms for application development
Digital Assets
• Analytics for increased customer engagements
• Integrate with Big Data and IoT
• DevOps
• Fit with modern tools and languages (Node, Python, Docker, OpenShift,
Kubernetes, Kafka, Pivotal Cloud Foundry, Ansible etc.)
4. Postgres for Big Data
Postgres enables you to support a wider range of workloads with
your relational database:
• An Object-relational design and decades of proven reliability make Postgres the
most flexible, extensible and performant database available
• Document store capabilities: XML, JSON, PLV8; HStore (key-value store); non-
durable storage; full text indexing
• Foreign Data Wrappers enable read/write integration with other database
technologies
• Postgres sees the data source as a table that can be queried and written to
using SQL
• Support for Oracle, MongoDB, Hadoop and MySQL
4
5. Why Choose Between NoSQL and
Relational When You Can Have Both?
• Schema-less development – fast application development
• Document store with ACID and relational capabilities
• Decades-long track record of quality and stability
• TCO cost avoidance from new systems:
• Operational support
• Duplicated storage
• Software upgrades
• Monitoring & management
• Hardware
• Training
• Additional staffing
5
6. Why Choose Between NOSQL and
Relational When You Can Have Both?
No need for programmatic logic to combine SQL and NoSQL in the
application – Postgres does it all !!
SELECT DISTINCT
product_type,
data->>'brand' as Brand,
data->>'available' as Availability
FROM json_data
JOIN products
ON (products.product_type=json_data.data-
>>'name')
WHERE json_data.data->>'available'=true;
product_type | brand | availability
---------------------------+-----------+--------------
AC3 Phone | ACME | true
ANSI SQL
JSON
6
7. Integrate Web, Big Data and unstructured
information with your relational databases.
• Based on Foreign
Data Wrappers
and SQL/MED
7
R
R / W
R / W
File / CSVODBC/JDBC
MySQL
MongoDB
Twitter / FB
Hadoop
LDAP
Others…
8. EDB POSTGRES REPLICATION SERVER
• Replication from a master to multiple
replicas
• Integration with Oracle® and SQL Server®
for a holistic view of data
• Better performance by offloading read
workload
• Fine grained replication for customization
• Replication of subsets of data for testing
• Cross-version and legacy migration support
Master
Read/Write
Data Filtering
Scheduling
Replica
Read
Clients
Clients
9. Interoperability With Oracle:
9
ENHANCED COMPATIBILITY
• Autonomous transaction support in Advanced Server 11
SCHEMA MIGRATION
• Faster assessment: multiple schemas, better error recovery
• Seamless workflow via online Migration Portal
DATA MIGRATION
• More flexibility with Next Generation Replication Server
APPLICATION TRANSFORMATION
• Increased adoption of OCI, especially in ISV products
• Improved documentation on compatibility features
OPERATIONAL CHARACTERISTICS
• Minimal downtime for management and maintenance
• Facilitate migration and management in move to the cloud
Compatibility is no longer just about syntax − it’s every aspect
12. Simplified Deployment. Robust Capabilities.
• Packaged simply in only three containers
12
EDB Postgres Containers
EDB Postgres Advanced Server
+ EDB Failover Manager
Container
pgPool Container:
SQL Routing
and Load Balancing
EDB Postgres
Backup and Recovery Tool Container
FOR DATA MANAGEMENT
AND HIGH AVAILABILITY
FOR READ SCALABILITY FOR DISASTER RECOVERY
SUPPORTED VERSIONS |
EPAS 9.6,10; EFM 3.0; pgPool 3.5; BART 2.0; CentOS 6,7; RHEL 6,7;
Red Hat Open Shift 3.6; Kubernetes 1.6; Docker 12.1
14. Summary: Not just cost-effective but….
14
FLEXIBILITY TO DEPLOY
• Not just bare metal or Virtualized but DBaaS and PaaS
• Popular OS Platform Support: RHEL, SLES, Ubuntu, Debian, Windows, POWER Linux
• Cloud Platform Agnostic: Pubic or Private, AWS, Azure, OpenStack
EXTENSIBILITY
• MED through Foreign Data Wrappers
• Native GIS Extension, NoSQL- JSON/JSNON, Key Value Pair Support in the core
• Extensive PL Support: Pl/pgSQL, PL/SQL, PL/perl, PL/python,PL/TCL and more
CONTAINER READY
• Deploy with ease in Containers
• Work with Container Orchestrators & PaaS Environments
AN INTEGRATED DATABASE PLATFORM
• A database which is in the center of the data center
• Integrate with just not only the Homogenous but also with Heterogeneous data stores
• Integrate with Oracle, SQL Server, Postgres, Hadoop, MySQL, Mongo, Flat Files etc.
15. ENTERPRISE CLASS FEATURES FOR DIGITAL
TRANSFORMATION
“ EDB Postgres’ combination of unstructured and
relational database technologies provides us the
freedom, flexibility and performance for handling
unstructured and semi-structured data that we
needed to optimally run our system.”
-- DBA Team, Ericsson
Ashnik and the insurance company have been able to
realize significant performance improvements and
cost savings, while exchanging data in the near real-
time with the partner bank. Due to the Success of the
initial pilot Ashnik is now planning to roll out the
system, based on EDB Postgres, to the rest of the
insurance company’s operation in Southeast Asia.
-- Leading Singapore Insurance Company
“IAG is using EDB because of the
capabilities to do a number of
different things with a single
technology stack…because of its
various tools and different ways to
handle data…
-- Eddie Satterly, Director, Data &
Product Engineering & Data Ops.
IAG
Compatibility is no longer just about syntax − it’s every aspect
KEY TAKEAWAY: Postgres fills the ‘Utility Player role in your data infrastructure, with multiple capabilities not available in your current database.
Postgres’ DNA is as an Object-Relational DB.
Our Object-relational roots enable us to support many schema-less data types with exceptional extensibility that other relational DB’s may not.
Because of its extensibility, PostgreSQL easily integrates many core features that motivate organizations to use other NoSQL databases:
HSTORE for key-value storage
A MongoDB extension
Extensive JSON Support
XML Support
PL/V8 (a Java Script based database language)
KEY TAKEAWAY: Postgres NoSQL capabilities extend the value and investments you already have in Postgres.
Postgres can provide most of your database needs and where you’d like to use another database technology, Postgres’ additional features make it the perfect connection point for all of your data sources
JSONB-Example
Multi-Model Data Management
PostgreSQL supports relational, document oriented, and key-value pair based data models. The relational model is supported through a very high degree of ANSI SQL conformance; the document oriented data representation is supported through JSONB; key-value pair capabilities are provided through the HSTORE extension. Together with a rich range of other extensions, such as PostGIS, this creates a uniquely positioned platform to combine structured and unstructured data in one transactional, ACID-compliant context.
Query can return results in both JSON or non-JSON format based on how application want to use it.
Postgres is more of a “Not Only SQL” rather “NoSQL”.