Presented by:


Jim Mlodgenski

Amazon Web Services

Jim has more than 20 years of experience developing data intensive applications and infrastructure. Prior to joining AWS, Jim was CTO at OpenSCG and CEO at StormDB, a Postgres-XC scalable public cloud solution. While at StormDB, Jim envisioned the offering and was responsible for all product development. Prior to StormDB, Jim was chief architect at EnterpriseDB, leading the firm’s technology direction, including its early cloud offerings and other product lines. Jim also very active in the PostgreSQL community, co-founding both the New York and Philadelphia PostgreSQL Meetup groups, co-organizing the largest PostgreSQL conferences, and serving on the Board of the PostgreSQL Foundation. Jim also speaks regularly at PostgreSQL and other open sources conferences.

No video of the event yet, sorry!

Regardless of the type of application you are writing, PostgreSQL needs a data model to hold your data. Some people think that your data model needs to conform to perfect 5th normal form, while others think the ideal model is just putting everything in a JSON document. For most business applications, the answer is likely somewhere in the middle. Whether you are designing a new application or migrating an existing one to PostgreSQL, the single biggest factor contributing to your overall performance is the data model. Spending time up front and laying a quality foundation is the key to success.

In this talk, we will discuss how to think about your data model in PostgreSQL. We will cover how best to lay out your tables based on how your application behaves and how it affect PostgreSQL. We will talk about the different types of constraints in PostgreSQL and when you should consider using other ways of ensuring data integrity instead of a foreign key. Throughout the talk, we will be discussing the wide range of data types and how to choose the correct type.

2019 September 19 16:20
50 min
Winchester (1)
Silicon Valley 2019