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: Tue, 17 Sep 2019 20:32:56 +0200 Lines: 31 Message-ID: <87h85ag4dj.fsf@x230.onfire.org> References: <877e69h1jg.fsf@x230.onfire.org> Mime-Version: 1.0 Content-Type: text/plain X-Trace: individual.net 7HOLm8ZjvqTiuzrn/ArULAm2cwfxyBRnK7chintu69hIzaUUgV Cancel-Lock: sha1:DWYsCTRO7F0WWQtFZdftdS9edP8= sha1:gcBJY9ecAzR9Ky2bPj4uwhqb6OY= User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.1 (berkeley-unix) Xref: csiph.com comp.databases.postgresql:875 Pankaj Jangid writes: > This is a really practicle advice. Thanks. Given the timeline of this > project I wanted some suggestion to deal with the complexity. And this > is really a breather. I can certainly apply incremental improvement. One further thing I noticed during the last few months on a personal project: if you have time left, you may also think about how and where to add debugging and logging code. Making state transition explicit and visible can help tremendously when something does not operate "as intended". I develop some code in PL/pgSQL (triggers and database functions) and added small if/else branches with RAISE NOTICE messages. I can turn on and off such messages with a configuration table in the database and see how various functions operate along the way. >> (*) It is more or less a reply to let you know that there is >> at least one person who still reads this group. > > I really appreciate your reply. Felt so lonely after posting my > query. Your reply is a hope. Sure! If you are further interested in reporting about the progress, your decisions or tools, please feel free to report it here. Your project sounds interesting and maybe, others have some further hints or tips when reading more about your project. -- Christian Barthel