Path: csiph.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: Christian Barthel Newsgroups: comp.databases.postgresql Subject: Re: Application architecture for multi-site manufacturing Date: Sun, 15 Sep 2019 20:12:03 +0200 Lines: 35 Message-ID: <877e69h1jg.fsf@x230.onfire.org> References: Mime-Version: 1.0 Content-Type: text/plain X-Trace: individual.net IV5jzDQ2tbCQbJl0eYgpUwnvc2BP1V8t8Q2V3f4w3ggWvhdEmd Cancel-Lock: sha1:MNFymnL2vA5A4bNFNme3I77bjjo= sha1:RzL6np787T9fbS4tQhI6KBAtImU= User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.1 (berkeley-unix) Xref: csiph.com comp.databases.postgresql:873 Hello, Pankaj Jangid writes: > I am designing an application for a manufacturing company. And I have > decided to go with an open source implementation from top to bottom. And > obviously, PostgreSQL is one of the choices that I have made due to many > reasons. Most important being its ability to handle large amounts of > data, speed, and reliability. That is not such a bad decision, I guess. [..] > I want to get advice from the PostgreSQL community on this. I have not > done multi-site projects in the past. So before going ahead I want to > have advice on a reasonably futureproof architecture. Any help is > appreciated. I can not comment much on the above because I do not have a lot of experience with designing de-central, big systems(*). I would try to find a simple way of dealing with the existing demands and improve the existing solution incrementally. Is a Redis cache really necessary? If you have a local copy of the data on each site, the performance of PostgreSQL may be good enough? Can you add performance improvements later? Can you make it modular and extendable for future demands etc. Apart from that, more experienced people might be available on the mailinglist at https://lists.postgresql.org/. There is a lot more conversation going on. (*) It is more or less a reply to let you know that there is at least one person who still reads this group. -- Christian Barthel