Software Architectureusing ØMQ                  Pieter Hintjens                #techmesh 2013
90% of software is already trash,90% of the rest will be, soon
We basically dont know how to makecode that can survive ten, let alone50 years
Software architecture should beanswering this question...
Can we build durable, perfect large-scale systems?
The answer is all around us...
Future code has to talk to code, hasto be chatty, sociable, well-connected
The physics of software is thephysics of people
How we connect to each othermatters more than who we are
Writing distributed code is like a livejam session, all about other people
A good contract is worth a thousandassumptions
Distributed software lives or dies byits protocols
Protocols define the rights andobligations of each party
Extensibility and performance aretwo separate targets
Simplicity always beats functionality
Design by removing problems, notadding features
Problems are not all equal, and mostare illusions
When you know the real problem youhave done half the work
The problem landscape is real, anddiscoverable 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 whenyou fall
Solve one problem, and repeat untilyou run out of time or money
Learn more:The ØMQ Guide http://zero.mq/zgComing from OReilly in Feb 2013ØMQ London http://zero.mq/lugSkillsMatter eXchang...
Upcoming SlideShare
Loading in …5
×

Software Architecture using ZeroMQ - techmesh 2012

2,089 views

Published on

Pretty pictures and empty phrases

Published in: Technology
1 Comment
2 Likes
Statistics
Notes
  • All photos by Pieter Hintjens and licensed under cc-nc-by-sa.
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
No Downloads
Views
Total views
2,089
On SlideShare
0
From Embeds
0
Number of Embeds
12
Actions
Shares
0
Downloads
43
Comments
1
Likes
2
Embeds 0
No embeds

No notes for slide

Software Architecture using ZeroMQ - techmesh 2012

  1. 1. Software Architectureusing ØMQ Pieter Hintjens #techmesh 2013
  2. 2. 90% of software is already trash,90% of the rest will be, soon
  3. 3. We basically dont know how to makecode that can survive ten, let alone50 years
  4. 4. Software architecture should beanswering this question...
  5. 5. Can we build durable, perfect large-scale systems?
  6. 6. The answer is all around us...
  7. 7. Future code has to talk to code, hasto be chatty, sociable, well-connected
  8. 8. The physics of software is thephysics of people
  9. 9. How we connect to each othermatters more than who we are
  10. 10. Writing distributed code is like a livejam session, all about other people
  11. 11. A good contract is worth a thousandassumptions
  12. 12. Distributed software lives or dies byits protocols
  13. 13. Protocols define the rights andobligations of each party
  14. 14. Extensibility and performance aretwo separate targets
  15. 15. Simplicity always beats functionality
  16. 16. Design by removing problems, notadding features
  17. 17. Problems are not all equal, and mostare illusions
  18. 18. When you know the real problem youhave done half the work
  19. 19. The problem landscape is real, anddiscoverable over time
  20. 20. Do nothing that is not a minimal,plausible answer to a clear problem
  21. 21. Make every commit shippable
  22. 22. Take small steps, it hurts less whenyou fall
  23. 23. Solve one problem, and repeat untilyou run out of time or money
  24. 24. Learn more:The ØMQ Guide http://zero.mq/zgComing from OReilly in Feb 2013ØMQ London http://zero.mq/lugSkillsMatter eXchange, today 6.30pm

×