Benny Rutten, Senior Database Administrator at Isabel Group, presented a case study at Postgres Vision 2018 about building a Service Hub on OpenStack with EDB Postgres that any Oracle DBA could manage with zero transition time.

1. Postgres at Isabel
June 5/6 2018

2. Agenda
• Introduction
• Purpose of this presentation
• Opting for Postgres
• EDB Postgres
• ‘People’ challenges
• DBA’s
• Developers
• EDB support
• Questions

3. Speaker Introduction
Experience: Air Defense controller (8 years), Emergency Supply Manager (5 years), Databases (18 years)
Achievements: Self-service Dev/Acc Oracle environments, implemented Postgres, RabbitMQ
Current Projects: DC migrations, Apache Cassandra, RabbitMQ
Name: Benny Rutten
Job: Database Administrator
Company: Isabel Group (Brussels, Belgium)

5. Agenda
• Introduction
• Purpose of this presentation
• Opting for Postgres
• EDB Postgres
• ‘People’ challenges
• DBA’s
• Developers
• EDB support
• Questions

6. Purpose of this presentation
• Explain why Isabel has chosen Postgres as its primary RDBMS
• Why EDB Postgres
• What kind of ‘people’ challenges faced
• Give a brief impression of EDB Support

7. Agenda
• Introduction
• Purpose of this presentation
• Opting for Postgres
• EDB Postgres
• ‘People’ challenges
• DBA’s
• Developers
• EDB support
• Questions

8. Which RDBMS can replace Oracle
• a robust relational database
• suitable for the applications now serviced by Oracle
• with a flexible licensing model, suited for VM
• and 24/7 support (with an experienced partner)

9. Required key features
Core Database Features Oracle Postgres
ACID transaction support Yes Yes
Crash recovery Yes Yes
Cost-based optimizer Yes Yes
Data partitioning Yes Yes
Data compression Yes Yes
User-defined datatypes Yes Yes
Multi-terabyte database capable Yes Yes
High-speed, parallel data loader Yes Yes
Memory/distributed caching option Yes Yes
Connection pooling Yes Yes
JSON support Yes Yes

10. Also…
• Do we need thi$$$
• If thi$ can do the same?

11. Agenda
• Introduction
• Purpose of this presentation
• Opting for Postgres
• EDB Postgres
• ‘People’ challenges
• DBA’s
• Developers
• EDB support
• Questions

12. We opted for EDB’s EPAS because:
• Oracle compatibility
• Covers all of Oracle’s functionality that we need
• < 10 % TCO compared to Oracle
• EDB’s licenses are ‘ALL IN’

13. EDB – added value
• Productivity tools:
• Postgres Enterprise Manager
• Backup tool
• Failover manager
• Replication server
• Migration toolkit

14. Agenda
• Introduction
• Purpose of this presentation
• Opting for Postgres
• EDB Postgres
• ‘People’ challenges
• DBA’s
• Developers
• EDB support
• Questions

15. DBA’s
• All Oracle specialists
• Hesitant to adapt to change (like most people)
• ‘Why should we change when everything is working?’

16. Steps taken to easy transition
• Provide an Oracle-like Postgres environment
• Software installation similar to Oracle
• Environment configuration similar to Oracle
• Connecting to the DB similar to Oracle

17. Software Installation - Oracle homes
17

18. Software installation - Postgres homes
18

19. Configuration - /etc/oratab (Oracle)
19

20. Cofiguration - /etc/pgtab (Postgres)
20

21. Setting the Oracle environment - . oraenv
21

22. Setting the Postgres environment - . pgenv
22

23. Agenda
• Introduction
• Purpose of this presentation
• Opting for Postgres
• EDB Postgres
• ‘People’ challenges
• DBA’s
• Developers
• EDB support
• Questions

24. Developers
• All are used to work with Oracle
• Willing to embrace new technology (we were surprised)

25. Self-service API (Oracle)

26. Self-service API (Postgres)

27. Agenda
• Introduction
• Purpose of this presentation
• Opting for Postgres
• EDB Postgres
• ‘People’ challenges
• DBA’s
• Developers
• EDB support
• Questions

28. EDB Support
• Average resolution time is on average less than one hour
• -> Based on 63 cases between December 2015 and June 2018
• You can simply mail and call the support team
• -> All ‘paperwork’ is filled out by EDB Support

29. Agenda
• Introduction
• Purpose of this presentation
• Opting for Postgres
• EDB Postgres
• ‘People’ challenges
• DBA’s
• Developers
• EDB support
• Questions

30. The end
• Thank you for your time
• Questions ?