korya

This is my response to an email asking about Domain-Driven Design in golang project.

Thank you for getting in touch. Below you will find my thoughts on how golang works with DDD, changing it. This is merely a perception of how things worked out for us in a single project.

That project has a relatively well-known domain. My colleagues on this project are very knowledgeable, thoughtful and invested in quality design. The story spelled out below is a result of countless hours spent discussing and refining the approach.

Conclusions could be very different, if there was a different project, team or a story-teller.

Short story

korya

var child_process = require('child_process');

exports.handler = function(event, context) {
  var proc = spawn('./test', [ JSON.stringify(event) ], { stdio: 'inherit' });

  proc.on('close', function(code){
    if(code !== 0) {
      return context.done(new Error("Process exited with non-zero status code"));
    }

korya

Share Counts

I have always struggled with getting all the various share buttons from Facebook, Twitter, Google Plus, Pinterest, etc to align correctly and to not look like a tacky explosion of buttons. Seeing a number of sites rolling their own share buttons with counts, for example The Next Web I decided to look into the various APIs on how to simply return the share count.

If you want to roll up all of these into a single jQuery plugin check out Sharrre

Many of these API calls and methods are undocumented, so anticipate that they will change in the future. Also, if you are planning on rolling these out across a site I would recommend creating a simple endpoint that periodically caches results from all of the APIs so that you are not overloading the services will requests.

Twitter

korya

[{
    "Note": "The first two digits (ranging from 10–43) correspond to the province, while the last two digits correspond either to the city/delivery zone (range 01–50) or to the district/delivery zone (range 51–99). Afghanistan Postal code lookup",
    "Country": "Afghanistan",
    "ISO": "AF",
    "Format": "NNNN",
    "Regex": "^\\d{4}$"
}, {
    "Note": "With Finland, first two numbers are 22.",
    "Country": "Åland Islands",
    "ISO": "AX",
    "Format": "NNNNN",
    "Regex": "^\\d{5}$"
}, {
    "Note": "Introduced in 2006, gradually implemented throughout 2007.",
    "Country": "Albania",
    "ISO": "AL",
    "Format": "NNNN",
    "Regex": "^\\d{4}$"
}, {
    "Note": "First two as in ISO 3166-2:DZ",
    "Country": "Algeria",
    "ISO": "DZ",
    "Format": "NNNNN",
    "Regex": "^\\d{5}$"
}, {
    "Note": "U.S. ZIP codes (range 96799)",
    "Country": "American Samoa",
    "ISO": "AS",
    "Format": "NNNNN (optionally NNNNN-NNNN or NNNNN-NNNNNN)",
    "Regex": "^\\d{5}(-{1}\\d{4,6})$"
}, {
    "Note":

korya

WAL-E needs to be installed on all machines, masters and slaves.

How to install WAL-E

Only one machine, the master, writes WAL segments via continuous archiving. The configuration for the master postgresql.conf is:

archive_mode = on
archive_command = 'envdir /etc/wal-e.d/env wal-e wal-push %p'
archive_timeout = 60