canonical-ci-engineering team mailing list archive

[Vincent Ladeuil <vila+ci@xxxxxxxxxxxxx>]

>>>>> Evan Dandrea <evan.dandrea@xxxxxxxxxxxxx> writes:

    > A quick explanation of what microservices are and why there's a trend
    > to leverage them in cloud architectures:

    > http://www.thoughtworks.com/insights/blog/microservices-nutshell

Wow, such a great talk !

A bit long but worth the time.

* The town planning analogy with how software is built (as opposed to
  the house building one I've used for years) is so obvious in
  retrospect...

* The 'smart endpoints and dump pipes' also resonates: it captures what
  I've been trying to advocate about rabbit queues. We should keep them
  "dumb", rock solid but dumb. For example: I'm still against the idea
  that we should nack messages coming from queues because it means we
  try to make our pipes smarter. I'd rather make our endpoints (workers)
  smarter by creating a different message to express that the input
  message couldn't be processed and leave rabbit handle workers death
  (the only case where we want a message delivered to another worker),

* 'single responsibility' is worth engraving on the wall too,

* 'service choreography' vs 'service orchestration' may look blurry
  today but... seems to better capture what we want to achieve with a
  versatile CI engine,

* 'phoenix infrastructure': no more long-lived services, start new
  ones. (yeah, I know IS want to preserve licenses, but meh ;-D).

* Oh, he mentions 'Release it!' too.

      Vincent

P.S.: I couldn't find the slides but would really like to get my hands
on them, so if you do find them, send them my way. Thanks in advance !