Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1XP2Cs-0005E3-B3 for pgsql-pkg-docker@arkaria.postgresql.org; Wed, 03 Sep 2014 04:30:06 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1XP2Cr-0006Kj-0h for pgsql-pkg-docker@arkaria.postgresql.org; Wed, 03 Sep 2014 04:30:05 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1XP2Cq-0006Kb-2W for pgsql-pkg-docker@postgresql.org; Wed, 03 Sep 2014 04:30:04 +0000 Received: from out1-smtp.messagingengine.com ([66.111.4.25]) by magus.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1XP2Ce-0007hZ-5g for pgsql-pkg-docker@postgresql.org; Wed, 03 Sep 2014 04:30:02 +0000 Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by gateway2.nyi.internal (Postfix) with ESMTP id 501C02090C for ; Wed, 3 Sep 2014 00:29:49 -0400 (EDT) Received: from web6 ([10.202.2.216]) by compute6.internal (MEProxy); Wed, 03 Sep 2014 00:29:49 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=fastmail.net; h= message-id:from:to:mime-version:content-transfer-encoding :content-type:subject:date; s=mesmtp; bh=KCZw/duRegnpBK5VcRpbzD1 OUJY=; b=GYvPgRdxy/eO0/uL4kJTF4+SY25SGAXkRo5XvL4MXXRoSUyM0pZNb3x B/SaQz/d10GUC/nFG4oRp+Y8Q3zC4yXAH4h3TBGu+tEyZ1HnOE6IOrSkK04LYbPZ aE2YK28UJBVxm6LnDlt/wQD5l1gNPePJz6wY5d1GtM1DNpucZ1uA= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:from:to:mime-version :content-transfer-encoding:content-type:subject:date; s=smtpout; bh=KCZw/duRegnpBK5VcRpbzD1OUJY=; b=uKeDxSuCiTklppba1Mx18IN1uG3E G70+Faq5T4BnQZF30hAlBQcbe6b/s3nhj5xXlTaPG0CwoLO/XrwXT7jAuPSLbtMt 9w0K1Dzt3gEqSeUyfGG/XVvwnVjJsTC730bDUmIEy5NjcSGTiMQ4b928xsZAyrLN WXrretECrfNqCj0= Received: by web6.nyi.internal (Postfix, from userid 99) id 20963981BFE; Wed, 3 Sep 2014 00:29:49 -0400 (EDT) Message-Id: <1409718589.1136366.162988969.1D08CE01@webmail.messagingengine.com> X-Sasl-Enc: bvK18To1AD43YrQ3FjeOJyP1IgQ6I9Bi1XiltUBrsiyr 1409718589 From: sprin@fastmail.net To: pgsql-pkg-docker@postgresql.org MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain X-Mailer: MessagingEngine.com Webmail Interface - ajax-d99f3b31 Subject: Introduction Date: Tue, 02 Sep 2014 21:29:49 -0700 X-Pg-Spam-Score: -2.7 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-pkg-docker Precedence: bulk Sender: pgsql-pkg-docker-owner@postgresql.org Hi! I am really excited to see some good discussion and involvement from the Postgres community on the Postgres Docker image. My team is in the process of "Dockerizing all the things" at $WORK, and most of "the things" have Postgres at their core. Some of our backends are little more than some Python HTTP/auth glue on top of Postgres. We make heavy use of views, a little PLPGSQL here and there, and other Postgres niceties such as JSON types. I have been developing with Postgres for a few years now, but after a minor upheaval, I am leading the overhaul of our platform and taking on more of an "ops" role. This brings with it DBA responsibilities, so I am quickly learning about replication, backups, and high availability mechanisms. Coincident with our containerization effort, we are moving towards a more "microservices" platform to alleviate the pain of long-lived, monolithic applications, lower ramp-up time for devs, and generally make the development process simpler. The downside is increased operational complexity of tying together all these services across disparate hosts and making them highly available. Docker is what we use to isolate services from each other on hosts and is a pretty complete tool for this task. To construct our "routing mesh", we found some great complements to Docker: HAProxy[1] and Consul[2]. With some glue provided by Registrator[3] and Consul-HAProxy[4], we were able to build a general purpose, zero-conf TCP routing mesh for Docker services with no new code. I see this routing layer as essential to Postgres replication and failover when dealing with arbitrary numbers of containerized clusters. So I am highly motivated to see Postgres images that are satisfactory for production use in a microservices environment *and* are very approachable to the casual Postgres user. I began some work on Postgres images for our use at $WORK, but Josh pointed me to this list when I asked for feedback. I've just finished reading through the the mailing list archives here and reviewing the commit history/issues at docker-library/postgres, and I think this list is a great place to drive further development of images and guide the use of Dockerized Postgres. I want to ask some pretty high-level questions on the overall approach since I think that will guide the direction of the images we build - tomorrow. -- Steffen Prince [1] http://www.haproxy.org/ [2] http://www.consul.io/ [3] https://github.com/progrium/registrator [4] https://github.com/hashicorp/consul-haproxy -- Sent via pgsql-pkg-docker mailing list (pgsql-pkg-docker@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-pkg-docker