Downloaded 52 times
Uploaded byEberhard Wolff
Software Architecture for Innovation
The document discusses the relationship between software architecture and innovation, emphasizing that effective software architecture enables changeability and supports continuous delivery. It details the importance of microservices in achieving quick and reliable deployments while fostering team autonomy and reducing coordination challenges. The author argues that by implementing microservices and continuous delivery, organizations can adapt to market needs effectively and innovate more rapidly.
More Related Content
Similar to Software Architecture for Innovation
Software Architecture for Innovation
- 1. Software Architecture for Innovation EberhardWolff Fellow innoQ @ewolff
- 2. What is Innovation? >New products and services on the market > New sources of revenue
- 3.
- 4. How does innovation relateto software architecture?
- 5.
- 6. Software architecture: set of structures neededto reason about a system, comprise software elements, relations among them, and properties of both.
- 7. Software architecture ofa system: set of structures needed to reason about a system, comprise software elements, relations among them, and properties of both.
- 8. Software architecture implements desired qualityattributes with technological means
- 9. Enable innovation… > Easyto change software > Measuring success (i.e. revenue)
- 10. Changeable software > Holygrail ever of software development > Through clean architecture > Good code quality
- 11.
- 12.
- 13.
- 14. Build Pipeline Commit Stage Automated Acceptance Testing Automated Capacity Testing Manual Explorative Testing Release Many teststo minimize risk Infrastructure automation Fast Feedback
- 15. Jenkins + Build PipelinePlug In
- 16. Commit Stage > Compile >Unit Tests > Static Code Analysis > Result: binary or installer
- 17.
- 18. UI Tests: Selenium >Easy to start > Natural for testers > Fragile > Loose semantics
- 19. Behavior-driven Scenario: User registerssuccessfully Context Event Expected outcome Given a new user with email eberhard.wolff@gmail.com firstname Eberhard name Wolff When the user registers Then a customer with email eberhard.wolff@gmail.com should exist And no error should be reported
- 20.
- 21. Capacity Tests > Automated >Realistic scenario and data > (Scaled-down) production- like system
- 22.
- 23. Explorative Tests > Nostrict test plan > Focus on new features > …unforeseen behavior > Automation frees resources for manual testing
- 24.
- 25. Release > Automated! > Nomanual change to any system > Mitigate risk e.g. with Blue-green > Two environments > Install system on second in the background
- 26.
- 27. Production > Gather feedback >…by monitoring > ...and logging > Does the software perform as expected?
- 28.
- 29. CD & Innovation >Make software easy to change > …by putting it into production quickly > ...and reliably > Less risk > Monitor success > ...by logging and monitoring
- 30. Continuous Delivery is onemore tool to achieve desired quality attributes.
- 31. CD Quality Attributes >Architecture must enable Continuous Delivery > Easy to deploy & test > Independent deployment > Easy & fast Continuous Delivery Pipeline
- 32. Trading Quality Software Architecture Continuous Delivery Provide easy todeployment Provide changeability
- 33.
- 34.
- 35.
- 36.
- 37. Server Server Microservice Definition >Independent deployment units > E.g. process, VMs, Docker containers > Any technology Micro Service Micro Service
- 38.
- 39.
- 40.
- 41.
- 42.
- 43.
- 44. Microservice Pipeline > Independentdeployment > Build pipeline per Microservice > Small > Easier to set up > Simpler (3rd party systems) > Faster Feedback: Less tests
- 45.
- 46. Agility > Put softwareout quickly > …by implementing stories > Measure success > Provide feedback for next iteration > Hard to do for large applications
- 47. Deployment Monolith Deployment Monolith Stories CoordinatingReleases Technical coordination
- 48. Add people untilteam too large – what now?
- 49. Conway‘s Law Architecture copies communication structures ofthe organization
- 50. Microservices > Team foreach Microservice > Team responsible for business features > Ideal: Independent features
- 51. Microservices Microservice Stories Microservice Stories Microservice Stories Order Billing Search ReleaseRelease Release Technical coordination Technical coordination Technical coordination
- 52. Team can deploywithout integration Changes can be deployed independently & quickly One or many Microservices per Team Synergy Microservices / Conway’s Law Order SearchBilling Order Billing Search Technology decisions per team
- 53. Microservices enable innovation by self-organization
- 54. Self Organization > Teamcan decide when to deploy into production > Team can decide on technologies > Total freedom?
- 55. Microservices enable innovation by delegatingtechnical decision to teams
- 56.
- 57. There are otherways to make software easily changeable.
- 58. Continuous Delivery > ContinuousDelivery allows to put out new features quickly > ...and measure success > Microservices support Continuous Delivery
- 59. Microservices > Microservices alloweach team to create new products > …put them in production > ...and see the effect on revenue > …with little coordination
- 60. Microservices > Microservices allowto do experiments > ...and remove failed experiments > Even with new or different technologies!
- 61. Not new! > Amazon2006 > Teams > …build business services > …operate them > ...foundation: Amazon Cloud > ...(i.e. virtual machines) > Microservices + DevOps + Continuous Delivery
- 62. Not radical! > DeveloperAnarchy is the radical approach. > No management > Programmers driven by business KPIs (Key Performance Indicators) > http://www.se-radio.net/2016/03/se-radio- episode-253-fred-george-on-developer- anarchy/
- 63.