Re: Async IO HTTP server frontend for PostgreSQL

From: Dmitriy Igrishin <dmitigr(at)gmail(dot)com>
To: David Boreham <david_list(at)boreham(dot)org>
Cc: "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: Async IO HTTP server frontend for PostgreSQL
Date: 2014-09-10 07:16:30
Message-ID: CAAfz9KPm-n=_CuB47ozy5D8XVQzRKaD7jva2g-Ly6EJcOMXiOQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hello, David

2014-09-10 4:31 GMT+04:00 David Boreham <david_list(at)boreham(dot)org>:

> Hi Dmitriy, are you able to say a little about what's driving your quest
> for async http-to-pg ?
> I'm curious as to the motivations, and whether they match up with some of
> my own reasons for wanting to use low-thread-count solutions.
>
For many web projects I consider Postgres as a development platform. Thus,
I prefer to keep the business logic (data integrity trigger functions and
API functions) in the database. Because of nature of the Web, many
concurrent
clients can request a site and I want to serve maximum possible of them with
minimal overhead. Also I want to avoid a complex solutions. So, I believe
that
with asynchronous solution it's possible to *stream* the data from the
database
to the maximum number of clients (which possible can request my site over a
slow connection).

--
// Dmitriy.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Herouth Maoz 2014-09-10 08:26:08 Re: Decreasing performance in table partitioning
Previous Message Tom Lane 2014-09-10 03:07:08 Re: Crash in 9.4 Beta when partially collapsing left outer joins