Playframework Hamburg Meetup #1 - Reactive persistence with Play 2 & postgresql-async
1 like1,694 views
The document discusses a presentation by Martin Grotzke on reactive persistence using PostgreSQL-async within the Play framework. It highlights the benefits of evented servers for handling real-time web applications without thread blocking, emphasizing the need for asynchronous I/O to improve efficiency. A sample project demonstrates non-blocking database access using the PostgreSQL-async driver.
Playframework Hamburg Meetup #1 - Reactive persistence with Play 2 & postgresql-async
- 1. Playframework Hamburg Meetup #1 Martin Grotzke - inoio gmbh @martin_grotzke - http://inoio.de reactive persistence showcase with postgresql-async
- 2. @martin_grotzke Motivation ● Realtime webapps ● Long running connections ● Thread based model: limited by # threads ● One thread per request, bound until the request is complete ● Thread blocked by I/O, idle ● CPU switching context ● Servlets, Ruby on Rails, Django, PHP
- 3. @martin_grotzke Solution – evented servers ● Evented servers: single thread per CPU core The Idea: threads are never blocked ● All I/O is asynchronous ● Instead of waiting, the thread can process other requests ● Come back when the response from the I/O call is ready ● Play, Node.js, Twisted
- 4. @martin_grotzke Challenge – backends ● Mostly synchronous, blocking drivers ● Most prominent: JDBC (synchronous API), on top connection pools, query DSL libs, ORMs ...
- 5. @martin_grotzke Solution example: postgresql-async https://github.com/mauricio/postgresql-async ● postgresql-async & mysql-async ● Netty based drivers for MySQL and PostgreSQL written in Scala - 2.10
- 6. @martin_grotzke Sample project https://github.com/magro/play-coda-reactive Play 2 sample (based on the standard computer database sample) to demonstrate async, non-blocking database access using the postgresql-async driver