Picking a specific database technology is not done overnight. It is not a decision that is taken lightly. You will most probably select a database technology for a long time, as the dogma of database agnostic has proven not to exist. Switching database technology is even more challenging. To even consider switching the workhorse under you prized, mission critical applications, the switch would have to bring serious advantages. Many years, if not decades, have been invested in building and testing everything, why change? I have invested nearly a quarter of a century working with Oracle technology, yet I made a switch. In this talk I want to take you through some of the considerations of this change and perhaps show that picking Postgres over Oracle makes sense…

2. THANK YOU DEVRIM

3. @POSTGRES
#PGDAYAMS
@PGDAYAMSTERDAM

6. WHY I PICKED POSTGRES OVER ORACLE

7. WHY

8. ▸This presentation
▸Open source
▸Change glasses
WHY

9. WHY
THIS PRESENTATION
▸It’s a journey
▸To boldly go
▸Why not?

10. WHY
OPEN SOURCE
▸2nd wave
▸Traditional business model
▸Passion

11. WHY - SIDE STEP
CLOSE VERSUS OPEN
▸ Develop solutions to sell
▸ Primary goal is to do business
▸ Develop solutions to solve a problem
▸ Primary goal is to solve a problem

12. WHY - SIDE STEP
CLOSE VERSUS OPEN
▸ Open software shows the math, not just the answer
▸ Not reverse engineering, just a good read
▸ Allows for tailoring of solutions

13. WHY
CHANGE GLASSES
▸The same, yet different
▸(Re) focus on the core
▸Challenges change

14. I

15. ▸Jan Karremans
▸My history & databases
▸Community centric
I

16. I
JAN KARREMANS
▸IT since 1991
▸Oracle v6 / Postgres v9.6
▸101 roles
▸Supporter of #DBADev & #SmartDB

17. I
MY HISTORY & DATABASES
▸Operator
▸Administrator
▸Consultant
▸Manager
▸Director
▸Sales
▸Pre-sales

18. I
MY HISTORY & DATABASES
▸Datapoint RMS 1991
▸Oracle on VAX / VMS 1993
▸Oracle on HP-UX 1997
▸Oracle on Linux 2010
▸Postgres on Linux 2016

19. I
COMMUNITY CENTRIC
▸Late to the game
▸Sharing is multiplying
▸Different vibes

20. PICKED

21. ▸Traditionally
▸Doing nothing
▸Changing business
PICKED

22. PICKED
TRADITIONALLY
▸Just an easy pick
▸Economy
▸The obvious

23. PICKED
DOING NOTHING
▸Don’t fix it, if…
▸IT is cool
▸Core infrastructure
▸Mortgage

24. PICKED - SIDE STEP
CORE INFRASTRUCTURE
▸ High availability
▸ RAC or ADG vs. streaming replication & load balancing
▸ Disaster recovery
▸ RMAN vs. BART
▸ Integration
▸ Golden Gate vs. logical replication or FDW

25. PICKED
CHANGING BUSINESS
▸Agility
▸Cost
▸Development
▸Deployment

26. PICKED - SIDE STEP
CHANGING BUSINESS
▸ DevOps
▸ Consolidation
▸ Containerisation
▸ This is “my computer”

27. PICKED
CHANGING BUSINESS
▸Confusion
▸Competition
▸Inside
▸Outside

28. POSTGRES

29. ▸Best hidden secret
▸Community open source
▸EnterpriseDB
▸Integration
▸Data centric application development
POSTGRES

30. POSTGRES
BEST HIDDEN SECRET
▸It’s changing
▸No marketing
▸Apply more strength

31. POSTGRES
COMMUNITY OPEN SOURCE
▸Built to sell / built to solve
▸Indepence
▸Super technology

32. POSTGRES - SIDE STEP
COMMUNITY OPEN SOURCE
▸ Closing presentation by Bruce Momjian - “Will Postgres Live Forever?”
Proprietary Software Life Cycle
versus
Open Source Software Life Cycle

33. POSTGRES
ENTERPRISEDB
▸Vehicle of choice
▸Massive Postgres
▸Oracle on Postgres

34. POSTGRES
ENTERPRISEDB
▸Global player
▸Focus on the Enterprise
▸Making a difference

35. POSTGRES
INTEGRATION
▸Extensions
▸Foreign Data Wrappers
▸Multi Model

36. POSTGRES
DATA CENTRIC APPLICATION DEVELOPMENT
▸Procedural Languages
▸Faster than Java
▸Mindset
▸#SmartDB

37. OVER

38. ▸Open or closed
▸Focus
▸Red or blue
OVER

39. OVER
OPEN OR CLOSED
▸Black box suffices
▸Code access is crucial
▸Paradigm shift

40. OVER - SIDE STEP
OPEN OR CLOSED
▸ “Black Box” approach can also be really tricky
▸ Not just with traditional vendors
▸ Amazon RDS vs. regular PostgreSQL

41. OVER
FOCUS
▸Automation, “DevOps” or don’t care
▸Think different
▸Lean

42. OVER
RED OR BLUE
▸Tradition
▸Religion

43. ORACLE

44. ▸Large
▸Economy of scale
▸May I join
▸Direction
ORACLE

45. ORACLE
LARGE
▸Big company
▸For big clients
▸On big projects

46. ORACLE
ECONOMY OF SCALE
▸Makes sense (at scale)
▸Large enterprise focus

47. ORACLE
DIRECTION
▸Diversification
▸At your service
▸Abstraction

48. LESSONS LEARNED

49. ▸Weigh your needs
▸Don’t be afraid
▸Small to big
▸There are more ways
LESSONS LEARNED

50. LESSONS LEARNED
WEIGH YOUR NEEDS
▸What do I need
▸What does my project need
▸What should be our focus

51. LESSONS LEARNED
DON’T BE AFRAID
▸You are not alone
▸Technically it’s never an issue
▸Not much fresh wine

52. LESSONS LEARNED
SMALL TO BIG
▸They all state it
▸Video recorder to conglomerate bank
▸We don’t need promises

53. LESSONS LEARNED
THERE ARE MORE WAYS
▸But when it comes to databases
▸That truly need to do something
▸Postgres could just be
▸Your best bet for the future!

54. THAT’S IT
SPECIAL THANKS TO BRUCE MOMJIAN FOR HIS INSPIRATION…

55. #BLAMEMAGNUS

56. STAY IN TOUCH
USE ANY OF THESE
▸jan.karremans@enterprisedb.com
▸@johnnq72
▸+31 6 1638 9607
▸jankarremansnl
Thank you!!