際際滷

際際滷Share a Scribd company logo
Software Architecture
using MQ




                  Pieter Hintjens
                #techmesh 2013
90% of software is already trash,
90% of the rest will be, soon
We basically don't know how to make
code that can survive ten, let alone
50 years
Software architecture should be
answering this question...
Can we build durable, perfect large-
scale systems?
The answer is all around us...
Future code has to talk to code, has
to be chatty, sociable, well-connected
The physics of software is the
physics of people
How we connect to each other
matters more than who we are
Writing distributed code is like a live
jam session, all about other people
A good contract is worth a thousand
assumptions
Distributed software lives or dies by
its protocols
Protocols define the rights and
obligations of each party
Extensibility and performance are
two separate targets
Simplicity always beats functionality
Design by removing problems, not
adding features
Problems are not all equal, and most
are illusions
When you know the real problem you
have done half the work
The problem landscape is real, and
discoverable over time
Do nothing that is not a minimal,
plausible answer to a clear problem
Make every commit shippable
Take small steps, it hurts less when
you fall
Solve one problem, and repeat until
you run out of time or money
Learn more:

The MQ Guide http://zero.mq/zg
Coming from O'Reilly in Feb 2013

MQ London http://zero.mq/lug
SkillsMatter eXchange, today 6.30pm

More Related Content

Software Architecture using ZeroMQ - techmesh 2012