From: | John R Pierce <pierce(at)hogranch(dot)com> |
---|---|
To: | "Hu, William" <HuW(at)tri-met(dot)org> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Postgresql database for distributed transactions |
Date: | 2010-08-02 23:10:42 |
Message-ID: | 4C575072.7030702@hogranch.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 08/02/10 3:49 PM, Hu, William wrote:
>
> Each of the mobile POS when facing the consumer needs to process at
> most 500 transactions a day. I was hoping to use the intermittent
> network connection time to do system download to flag transactions,
> such as, stolen credit card number, etc. And, to use the stable
> midnight network connection time to do uploads of the mobile
> transactions to the central Postgresql database. The upload would
> require at most 600 mobile terminals times 500 transactions at most of
> 3,000,000 transactions a day in 30 minutes time frame.
>
fwiw, 600 * 500 is only 300,000, not 3,000,000. Thats only 10,000
transactions/minute, 166/second, which should be readily achievable with
a reasonable DB server with the appropriate disk system.
I'm not sure how you can ensure data consistency when your POS terminals
are disconnected from each other.
From | Date | Subject | |
---|---|---|---|
Next Message | Alban Hertroys | 2010-08-03 06:01:34 | Re: Application user name attribute on connection pool |
Previous Message | Hu, William | 2010-08-02 22:49:39 | Postgresql database for distributed transactions |