Download as PDF, PPTX
![$ cat limerick.txt | tr -cs "[:alpha:]" "n" | awk '{print
length(), $0}' | sort | uniq
1 a
2 as
2 of
2 on
3 And
3 Who
3 she
3 the
3 was
4 They
4 With
4 face
4 from
4 lady
4 ride
4 rode
5 Niger
5 There
5 smile
5 tiger
5 young
6 inside
6 smiled
8 returned](https://image.slidesharecdn.com/softwarearchitecture-principlespatternsandpractices-osidays-2017-171016075259/85/Software-Architecture-Principles-Patterns-and-Practices-OSI-Days-2017-25-320.jpg)
![Amazonâs rules for teams
âą All teams will henceforth expose their data and functionality
through service interfaces.
âą Teams must communicate with each other through these
interfaces.
âą There will be no other form of inter-service/team communication
allowed: no direct linking, no direct reads of another teamâs
datastore, no shared memory model, no backdoors whatsoever.
âą The only communication allowed is via service interface calls
over the network.
âą It doesnât matter what technology they [other services] use.
âą All service interfaces, without exception, must be designed from
the ground up to be externalizable.
âą That is to say, the team must plan and design to be able to
expose the interface to developers in the outside world.](https://image.slidesharecdn.com/softwarearchitecture-principlespatternsandpractices-osidays-2017-171016075259/85/Software-Architecture-Principles-Patterns-and-Practices-OSI-Days-2017-45-320.jpg)
![Example of a ïŹx (java.time)
You can use only date,
time, or even timezone,
and combine them as
needed (in java.time)!
LocalDate today = LocalDate.now();
System.out.println(today);
LocalTime now = LocalTime.now();
System.out.println(now);
LocalDateTime todayAndNow = LocalDateTime.now();
System.out.println(todayAndNow);
ZonedDateTime todayAndNowInTokyo =
ZonedDateTime.now(ZoneId.of("Asia/Tokyo"));
System.out.println(todayAndNowInTokyo);
2015-12-02
17:37:22.647
2015-12-02T17:37:22.648
2015-12-02T21:07:22.649+09:00[Asia/Tokyo]](https://image.slidesharecdn.com/softwarearchitecture-principlespatternsandpractices-osidays-2017-171016075259/85/Software-Architecture-Principles-Patterns-and-Practices-OSI-Days-2017-120-320.jpg)
Uploaded byCodeOps Technologies LLP
Software Architecture - Principles, Patterns and Practices - OSI Days - 2017
The document discusses software architecture, detailing fundamental principles, styles, and practices essential for architectural design. It covers various architectural styles such as microservices, event sourcing, and the pipe-and-filter model, while emphasizing the importance of design decisions that influence system qualities like availability, security, and performance. Additionally, it highlights tactics for achieving these qualities and includes references to open-source tools and case studies for practical application.
SoftwareâŠ
More Related Content
Similar to Software Architecture - Principles, Patterns and Practices - OSI Days - 2017
![[2016/2017] Introduction to Software Architecture](https://cdn.slidesharecdn.com/ss_thumbnails/ivano03softwarearchitecture-161220160406-thumbnail.jpg?width=640&height=640&fit=bounds)
More from CodeOps Technologies LLP
Software Architecture - Principles, Patterns and Practices - OSI Days - 2017
- 1. Ganesh Samarthyam ganesh@codeops.tech www.codeops.tech Software Architecture: Principles,Patterns, and Practices
- 2. Why do youwant to become an architect? What skills are required for an architect? Who is an architect? What essential knowledge is required for an architect?
- 3. What is software architecture? Howto evolve an architecture? What is the software architecture development process? What factors inïŹuences software architecture?
- 4. Generalist Specialist Source: Software Architecturefor Developers, Simon Brown, LeanPub, 2014
- 5.
- 6. âThe software architectureof a program or computing system is the structure or structures of the system, which comprise software elements, the externally visible properties of those elements, and the relationships among themâ Source: So)ware Architecture in Prac2ce (2nd edi2on), Bass, Clements, Kazman; Addison-Wesley 2003:
- 7. âArchitecture is aset of principal design decisions about a software systemâ Source: R. N. Taylor, N. Medvidovic, and E. M. Dashofy. 2009. Software Architecture: Foundations, Theory, and Practice. Wiley Publishing.
- 8. âThe architecture ofa deployed software is determined by those aspects that are hardest to changeâ Source: R. N. Taylor, N. Medvidovic, and E. M. Dashofy. 2009. Software Architecture: Foundations, Theory, and Practice. Wiley Publishing.
- 9. Architecture represents thesignificant design decisions that shape a system, where significant is measured by cost of change. - Grady Booch (2006)
- 10.
- 11. Cross-cutting concerns Error/Exception handling ConcurrencyPersistence Eventhandling Interaction and presentation Source: SWEBOK v3
- 13.
- 15. Source: Software Architecturefor Developers, Simon Brown, LeanPub, 2014
- 16. Architecture/design determines qualities Understandability ChangeabilityExtensibility Reusability Testability Reliability Arch/ Design impacts impacts impacts
- 17. Architecture principles andstyles Architectural principles: Axis, symmetry, rhythm, datum, hierarchy, transformation
- 18. Dravidian styleRenaissance style Mughalstyle Post-modern style
- 19. What architectural styleis this? Image source: http://ashokbasnet.com.np/wp-content/uploads/2011/03/wx_thumb-5B1-5D.jpg
- 20. Example: Abstracting for portabilityusing layering âąâŻ Helps'abstract'pla-orm0 speciïŹc'details'abstrac4ng' hardware'speciïŹc'aspects'' Hardware' Abstrac4on' Layer'(HAL)' âąâŻ Abstracts'OS'speciïŹc' func4onality'and'provides' a'generic'interface'to' underlying'OS' Opera4ng' System' Abstrac4on' Layer'(OSAL)' âąâŻ Hides'database'speciïŹc' aspects'by'providing'a' generic'interface'' Database' Abstrac4on' Layer'(DAL)'
- 21. Layering style: BeneïŹts +Reuse of layers + Support for standardization + Dependencies are kept local + Exchangeability Frank Buschmann, Regine Meunier, Hans Rohnert, Peter Sommerlad, and Michael Stal. 1996. Pattern-Oriented Software Architecture: A System of Patterns. John Wiley & Sons, Inc., NY, USA.
- 22. Layering style: Liabilities -Cascades of changing behavior - Lower efïŹciency - Unnecessary work - DifïŹculty in establishing the correct granularity of layers Frank Buschmann, Regine Meunier, Hans Rohnert, Peter Sommerlad, and Michael Stal. 1996. Pattern-Oriented Software Architecture: A System of Patterns. John Wiley & Sons, Inc., NY, USA.
- 23. What architectural styleis this?
- 24. $ cat limerick.txt Therewas a young lady of Niger Who smiled as she rode on a tiger. They returned from the ride With the lady inside And a smile on the face of the tiger.
- 25. $ cat limerick.txt| tr -cs "[:alpha:]" "n" | awk '{print length(), $0}' | sort | uniq 1 a 2 as 2 of 2 on 3 And 3 Who 3 she 3 the 3 was 4 They 4 With 4 face 4 from 4 lady 4 ride 4 rode 5 Niger 5 There 5 smile 5 tiger 5 young 6 inside 6 smiled 8 returned
- 26. List<String> lines = Files.readAllLines(Paths.get("./limerick.txt"),Charset.defaultCharset()); Map<Integer, List<String>> wordGroups = lines.stream() .map(line -> line.replaceAll("W", "n").split("n")) .flatMap(Arrays::stream) .sorted() .distinct() .collect(Collectors.groupingBy(String::length)); wordGroups.forEach( (count, words) -> { words.forEach(word -> System.out.printf("%d %s %n", count, word)); }); 1 a 2 as 2 of 2 on 3 And 3 Who 3 she 3 the 3 was 4 They 4 With 4 face 4 from 4 lady 4 ride 4 rode 5 Niger 5 There 5 smile 5 tiger 5 young 6 inside 6 smiled 8 returned
- 27.
- 28. Pipe-and-ïŹlter: BeneïŹts + Flexibilityby ïŹlter exchange + Flexibility by recombination + Reuse of ïŹlter components + Rapid prototyping of pipelines Frank Buschmann, Regine Meunier, Hans Rohnert, Peter Sommerlad, and Michael Stal. 1996. Pattern-Oriented Software Architecture: A System of Patterns. John Wiley & Sons, Inc., NY, USA.
- 29. Pipe-and-ïŹlter: Liabilities - Sharingstate information is expensive or inïŹexible - EfïŹciency gain by parallel processing is often an illusion - Data transformation overhead - DifïŹcult to handle errors Frank Buschmann, Regine Meunier, Hans Rohnert, Peter Sommerlad, and Michael Stal. 1996. Pattern-Oriented Software Architecture: A System of Patterns. John Wiley & Sons, Inc., NY, USA.
- 30. POSA - beforeand after
- 31.
- 32. What is the architecture stylefollowed by World Wide Web (WWW)?
- 35. SOA (Service Oriented Architecture) LambdaStyle Microservices REST (Representational State Transfer) Map-Reduce CQRS (Command-Query Responsibility Segregation ) Software Containers Event Sourcing
- 36. Command Query Responsibility Segregation(CQRS) pattern source: https://msdn.microsoft.com/en-us/library/jj591573.da82141c6f9950d64c1263fa4da825ec(l=en-us).png
- 37. Event Sourcing pattern source:https://msdn.microsoft.com/en-us/library/dn589792.aspx
- 38. Map-Reduce pattern Input Sara Booch Thayer Merlin Sara Ralph Merlin Tim Sara Christian Ralph Cormen ⊠Computer Cluster map map map Sara,1 Ralph, 1 Merlin, 1 Tim, 1 Sara, 1 Booch, 1 Thayer, 1 Merlin, 1 Sara, 1 Christian, 1 Ralph, 1 Cormen, 1 reduce reduce Sara, 3 Booch, 1 Thayer,1 Merlin, 2 Ralph, 2 Tim, 1 Christian, 1 Cormen, 1 ⊠OutputSara, 1 Sara, 1 Sara, 1 Booch, 1 Thayer, 1 Merlin, 1 Merlin, 1 Ralph, 1 Ralph, 1 Tim, 1 Christian, 1 Cormen, 1
- 39. What style isthis? Batch layer Serving layerSpeed layer
- 40.
- 41.
- 42. Complex application = composedof tiny services
- 43. Communicate over RESTAPI HTTPGET HTTPPUT HTTP POST HTTPDELETE
- 44. Underlying philosophy âdo onething and do it wellâ
- 45. Amazonâs rules forteams âą All teams will henceforth expose their data and functionality through service interfaces. âą Teams must communicate with each other through these interfaces. âą There will be no other form of inter-service/team communication allowed: no direct linking, no direct reads of another teamâs datastore, no shared memory model, no backdoors whatsoever. âą The only communication allowed is via service interface calls over the network. âą It doesnât matter what technology they [other services] use. âą All service interfaces, without exception, must be designed from the ground up to be externalizable. âą That is to say, the team must plan and design to be able to expose the interface to developers in the outside world.
- 46. Service = ateam can DURS (Deploy, Update, Replace, Scale) Microservices = Damn U R Sexy
- 47. Amazon case study 2-tier architecture SOAMicroservices
- 49. Triggering microservices Source: DevOps:A Software Architect's Perspective, Len Bass, Ingo Weber, Liming Zhu, Addison-Wesley Professional, 2015
- 50.
- 51. A process forarchitecting using scenarios Source: http://msdn.microsoft.com/en-us/library/ee658084.aspx
- 52. Strategies and tactics Atactic is a design decision that inïŹuences the control of a quality attribute response A collection of tactics is known as âstrategiesâ Source: Len Bass, Paul Clements, and Rick Kazman. 2003. Software Architecture in Practice (2 ed.). Addison-Wesley Longman Publishing Co., Inc., Boston, MA, USA.
- 53. Example: Security tactics Security Resisting Attacks Detecting Attacks Recovering Fromattack !⯠Authenticate users !⯠Authorize users !⯠Maintain data confidentiality !⯠Maintain integrity !⯠Limit exposure !⯠Limit access Restoration Identification Stimulus: Attack Response: System detects, resists, or recovers from attacks See âAvailabilityâ Audit Trail Intrusion Detection Source: Len Bass, Paul Clements, and Rick Kazman. 2003. Software Architecture in Practice (2 ed.). Addison-Wesley Longman Publishing Co., Inc., Boston, MA, USA.
- 54. Exercise: Tactics for achievingqualities Availability The property of software that it there and ready to carry out its task when you need it to be Testability The ease with which software can be made to demonstrate its faults through (typically execution-based) testing Security Measure of the systemâs ability to protect data and information from unauthorised access while still providing access to people and systems that are authorized Performance The softwareâs ability to meet timing requirements ModiïŹability The ease with which the software can be modiïŹed (with minimal risk and cost) Source: Len Bass, Paul Clements, and Rick Kazman. 2003. Software Architecture in Practice (2 ed.). Addison-Wesley Longman Publishing Co., Inc., Boston, MA, USA.
- 55. Tactics for availability Use$fault$detec,on$tac,cs$such$as$ ping/echo,$heartbeat,$,me$ stamping,$sanity$checking,$ condi,on$monitoring,$and$self:test$ Use$fault$recovery$tac,cs$such$as$ rollback$(to$a$previous$known$ good$state),$providing$âsparesâ$for$ redundancy,$retry$the$opera,on,$ ignoring$faulty$behavior,$and$ degrade$(gracefully$reduce$system$ func,onality)$ Use$fault$preven,on$tac,cs$such$ as$removal$from$service$ (temporarily$remove$the$faulty$ component),$use$transac,onal$ seman,cs$(ACID$proper,es),$ prevent$system$excep,ons$from$ occurring.$ Source:Len Bass, Paul Clements, and Rick Kazman. 2003. Software Architecture in Practice (2 ed.). Addison-Wesley Longman Publishing Co., Inc., Boston, MA, USA.
- 56. Tactics for modiïŹability Reduce&size&of&the&module,&for& example&by&spli7ng&module&(to& reduce&the&average&cost&of&future& changes)& Increase&seman>c&cohesion&of&the& module&(by&ensuring&that&the&a& responsibili>es&serving&the&same& purpose&are&placed&in&the&same& module)& Reduce&coupling&through& encapsula>on&(by&providing&explicit& interfaces&and&hiding&internal&details),& introducing&intermediate& dependencies&(e.g.,&introduce& dynamic&lookup&of&services&with&SOA& using&directory&as&an&intermediary)&&& Source:Len Bass, Paul Clements, and Rick Kazman. 2003. Software Architecture in Practice (2 ed.). Addison-Wesley Longman Publishing Co., Inc., Boston, MA, USA.
- 57. Tactics for performance Control'resource'demand'through'requiring' smaller'demand'on'resources'to'service'the' events;'for'instance,'reducing'the'sampling' frequency'(for'capturing'environmental'data),' limi;ng'event'response'(by'queuing'the'events),' priori;zing'events'(by'ranking'the'events' according'to'their'importance'and'processing' them),'reducing'overheads'(by'consuming'lesser' resources),'bound'execu;on';mes,'and'increase' resource'eïŹciency.' Manage'the'resources'more'eïŹec;vely'by' increasing'resources,'introducing'concurrency,' maintaining'mul;ple'copies'of'computa;on,' bounding'queue'sizes,'and'scheduling'resources.'' Source:Len Bass, Paul Clements, and Rick Kazman. 2003. Software Architecture in Practice (2 ed.). Addison-Wesley Longman Publishing Co., Inc., Boston, MA, USA.
- 58. Tactics for security Detect%a'acks%by%looking%for% known%pa'erns%of%intrusion,% detec8ng%service%denial,% verifying%message%integrity% before%using%them,%detec8ng% message%delay%(to%detect%man= in=the=middle%a'acks).% Resist%a'acks%by%iden8fying,% authen8ca8ng,%and%authorizing% actors%(note:%actors%are%sources% of%external%input%to%the%system),% limi8ng%access%to%resources,%and% limi8ng%exposure%of%the%system.% React%to%a'acks%when%an%a'ack% is%underway%by%revoking%access,% lock%computer,%or%inform% relevant%actors.%% Source:Len Bass, Paul Clements, and Rick Kazman. 2003. Software Architecture in Practice (2 ed.). Addison-Wesley Longman Publishing Co., Inc., Boston, MA, USA.
- 59. Tactics for testability Control'and'observe'system'state'by' providing'specializing'interfaces,'record/ playback'faults,'localize'state'storage' (instead'of'distribu;ng'the'state),' abstract'input'data'sources,'sandbox'(by' isola;ng'the'system'from'the'real'world),' and'introduce'executable'asser;ons'(to' check'if'the'program'is'in'a'faulty'state)' Limit'complexity'(by'reducing'cyclic' dependencies,'limi;ng'dependencies'to' external'components,'etc;'in'OO' systems,'limit'depth'of'inheritance'tree,' reduce'dynamic'calls;'and'having'high' cohesion,'low'coupling'and'separa;on'of' concerns);'also'limit'nonCdeterminism.' Source:Len Bass, Paul Clements, and Rick Kazman. 2003. Software Architecture in Practice (2 ed.). Addison-Wesley Longman Publishing Co., Inc., Boston, MA, USA.
- 60.
- 61.
- 62.
- 63.
- 64.
- 65.
- 66.
- 67.
- 68. Reference architectures Source: AlessandroBassi, Martin Bauer, Martin Fiedler, Thorsten Kramp, Rob Van Kranenburg, Sebastian Lange, and Stefan Meissner. 2013. Enabling Things to Talk: Designing IoT Solutions with the IoT Architectural Reference Model. Springer
- 69. Use reference architectures whenrelevant ones are available (donât reinvent the wheel)
- 70. Glasgow Haskell Compiler Source:http://aosabook.org/en/ghc.html
- 71. OpenSAR (Automotive OpenSoftware Architecture)
- 72.
- 73. It is hardto recognise architecture styles from block diagrams
- 74.
- 75.
- 76. Dynamic Language Runtime Source:http://aosabook.org/en/ironlang.html
- 77.
- 78. Both informal diagrams(e.g. block diagrams) and semi- formal diagrams (e.g., UML) are used in practice
- 79.
- 80.
- 81. Open MPI Image source:http://aosabook.org/en/openmpi.html
- 82. Layering continues to bethe most widely used architecture style
- 83. Image Hosting System Source:http://aosabook.org/en/distsys.html
- 84. Image Hosting System Source:http://aosabook.org/en/distsys.html Split reads and writes
- 85. Image Hosting System Source:http://aosabook.org/en/distsys.html with redundancy
- 86. Image Hosting System Source:http://aosabook.org/en/distsys.html with partitioning
- 87. Start with theâsimplest possible thing that worksâ and evolve the architecture
- 88.
- 89.
- 90. As-IS architecture isalmost always different than intended architecture Solution: architecture oversight
- 91.
- 92. Refactoring cycles Remove oneof the dependencies Change dependency direction Move one of the dependencies
- 93. Continual refactoring isthe best weapon to deal with architecture degradation
- 94. âCities grow, citiesevolve, cities have parts that simply die while other parts flourish; each city has to be renewed in order to meet the needs of its populace⊠Software-intensive systems are like that. They grow, they evolve, sometimes they wither away, and sometimes they flourishâŠâ Grady Booch in the foreword for âRefactoring for Software Design Smells: Managing Technical Debtâ, Girish Suryanarayana, Ganesh Samarthyam, Tushar Sharma, Morgan Kaufmann/Elsevier, 2014.
- 95.
- 97. Code Query Language(NDepend, Architect, âŠ)
- 98. Look at theworld differently for creative design solutions
- 99. Who coined the term âcodesmellâ? Hint: He also originated the terms TDD and XP
- 100.
- 101. Who coined the acronym âSOLIDâ? (asin SOLID principles) Hint: He is the author of the book âWorking effectively with legacy codeâ
- 102. Michael Feathers S Single Responsibility Principle Every objectshould have a single responsibility and that should be encapsulated by the class O Open Closed Principle Software should be open for extension, but closed for modification L Liskovâs Substitution Principle Any subclass should always be usable instead of its parent class I Interface Segregation Principle Many client specific interfaces are better than one general purpose interface D Dependency Inversion Principle Abstractions should not depend upon details. Details should depend upon abstractions
- 103. Who coined the term âtechnical debtâ? Hint:He is the creator of âwikiâ
- 104.
- 105.
- 106.
- 107.
- 108.
- 110.
- 113. "This is agood book about âDesign Smellsâ â actually a great book â nicely organized - clearly written with plenty of examples and a fair sprinkling of anecdotes." - Will Tracz (Principal Research Scientist & Fellow, Lockheed Martin) (review in ACM SIGSOFT Software Engineering Notes)
- 114. Believe in yourideas: how small or âinsigniïŹcantâ it may appear to be!
- 115. "The critical designtool for software development is a mind well educated in design principles" - Craig Larman
- 116. Interface Segregation Principle (ISP) Clientsshould not be forced to depend upon interfaces they do not use
- 117. Example of ISPviolation // using java.util.Date Date today = new Date(); System.out.println(today); $ java DateUse Wed Dec 02 17:17:08 IST 2015 Why should we get the time and timezone details if I only want a date (e.g., date of birth)? Can I get rid of these parts? No!
- 118. JSR 310: JavaDate and Time API Stephen Colebourne
- 119. Example of aïŹx (java.time) // using java.time.LocalDate LocalDate today = LocalDate.now();âš System.out.println(today); $ java DateUse 2015-12-02 I can use (and hence depend upon) only date related functionality (not time, zone, etc)
- 120. Example of aïŹx (java.time) You can use only date, time, or even timezone, and combine them as needed (in java.time)! LocalDate today = LocalDate.now(); System.out.println(today); LocalTime now = LocalTime.now(); System.out.println(now); LocalDateTime todayAndNow = LocalDateTime.now(); System.out.println(todayAndNow); ZonedDateTime todayAndNowInTokyo = ZonedDateTime.now(ZoneId.of("Asia/Tokyo")); System.out.println(todayAndNowInTokyo); 2015-12-02 17:37:22.647 2015-12-02T17:37:22.648 2015-12-02T21:07:22.649+09:00[Asia/Tokyo]
- 121. More types fromjava.time
- 122.
- 123. Know and applydesign principles
- 125. How to separate: a)code generation logic from node types? b) how to support different target types? class Plus extends Expr { private Expr left, right; public Plus(Expr arg1, Expr arg2) { left = arg1; right = arg2; } public void genCode() { left.genCode(); right.genCode(); if(t == Target.JVM) { System.out.println("iadd"); } else { // DOTNET System.out.println("add"); } } }
- 126. class Plus extendsExpr { private Expr left, right; public Plus(Expr arg1, Expr arg2) { left = arg1; right = arg2; } public Expr getLeft() { return left; } public Expr getRight() { return right; } public void accept(Visitor v) { v.visit(this); } } class DOTNETVisitor extends Visitor { public void visit(Constant arg) { System.out.println("ldarg " + arg.getVal()); } public void visit(Plus plus) { genCode(plus.getLeft()); genCode(plus.getRight()); System.out.println("add"); } public void visit(Sub sub) { genCode(sub.getLeft()); genCode(sub.getRight()); System.out.println("sub"); } public void genCode(Expr expr) { expr.accept(this); } }
- 127. Source: âDesign Patterns:Elements of Reusable Object-Oriented Softwareâ, Erich Gamma, Richard Helm, Ralph Johnson and John Vlissides, Addison-Wesley,1994
- 128. â Many distinctand unrelated operations need to be performed on objects in an object structure, and you want to avoid âpollutingâ their classes with these operations Represent an operation to be performed on the elements of an object structure. Visitor lets you deïŹne a new operation without changing the classes of the elements on which it operations â Create two class hierarchies: â One for the elements being operated on â One for the visitors that deïŹne operations on the elements
- 129. { mv = cw.visitMethod(ACC_PUBLIC+ ACC_STATIC, "printOne", "()V", null, null); mv.visitCode(); mv.visitFieldInsn(GETSTATIC, "java/lang/System", "err", "Ljava/io/PrintStream;"); mv.visitLdcInsn("CALL println"); mv.visitMethodInsn(INVOKEVIRTUAL, "java/io/PrintStream", "println", "(Ljava/lang/String;)V", false); mv.visitFieldInsn(GETSTATIC, "java/lang/System", "out", "Ljava/io/PrintStream;"); mv.visitLdcInsn("Hello World"); mv.visitMethodInsn(INVOKEVIRTUAL, "java/io/PrintStream", "println", "(Ljava/lang/String;)V", false); mv.visitFieldInsn(GETSTATIC, "java/lang/System", "err", "Ljava/io/PrintStream;"); mv.visitLdcInsn("RETURN println"); mv.visitMethodInsn(INVOKEVIRTUAL, "java/io/PrintStream", "println", "(Ljava/lang/String;)V", false); mv.visitInsn(RETURN); mv.visitMaxs(2, 0); mv.visitEnd(); } Use of visitor pattern in ASM tool (coding example of usage) source: http://web.cs.ucla.edu/~msb/cs239-tutorial/
- 130. Apply relevant designpatterns for creating high-quality designs
- 132.
- 134. Modularize JDK &JRE Hide platform internal details such as sun.misc Provide a module system for Java developers Reference: http://paulbakker.io/java/java-9-modularity/
- 136. Perform periodic refactoring (ïŹossor root canal)
- 137.
- 138.
- 139. Use technical debtapproach to get buy-in for refactoring
- 142. Desirable relationship between architectand manager: partnership
- 143. Steve Jobs isviewed as an excellent speaker, business person, and leader. But not much as an architect. He is an excellent architect. Why?
- 145. In the movieSteve Jobs, he gives an example of a music composer. The composer directs the people and focuses on the orchestra. That is the case with a software architect as well.
- 146.
- 147. Examples from Open Source architectures âąArchitecture descriptions from well-known open source software from key contributors âą You can get insights on the architecture from practical illustrations http://www.aosabook.org/en/index.html
- 148. Practical book onSA âą Useful to get an overview of software architecture âą Especially useful if you are a programmer âą Complete presentation available here.
- 149. Good ïŹrst book onSA âą Shares practical experiences in architecting enterprise IT systems âą If you want to learn about enterprise architecture, read this
- 150. SEIâs book on SA âąGood coverage of Attribute Driven Design, Architecture Trade-off Analysis Method, Quality Attributes, etc âą If you want an in-depth understanding, read this
- 151. In-depth treatment onSA âą Covers a wide range of topics in detail (stypes, modelling, visualisation, analysis, etc) âą Perhaps the most comprehensive/in-depth discussion on important SA topics âą Slides available online here
- 152. THE book ondesign patterns âą One of the earliest and best books on design patterns âą Presents a catalog of 23 design patterns âą ClassiïŹed as creational, structural, and behavioral patterns
- 153. THE book onarchitectural patterns âą One of the earliest and best books on architectural patterns âą Presents a catalog of architectural patterns with detailed discussion âą Referred to as POSA book âą First book in the series of books on patterns/ styles
- 154. Anti-patterns in development, architecture, ⊠âąA practical book that covers anti-patterns in software architectures as well as projects âą Important to know anti- patterns so that we can avoid them
- 155. Architectural refactoring is tough! âą Thefocus is on refactoring techniques, tools, and processes in the large- scale (i.e., architectural level) âą Covers architectural smells as well
- 156. Getting a systems perspective âą Emphasiseson working with stakeholders, and using viewpoints and perspectives âą Read this if you are looking for gaining an in-depth understanding of working with stakeholders and using viewpoints and perspectives
- 157. An early take onSA âą Provides a good overview of architectural patterns âą If you are interested in architectural styles, tools, languages and notations, etc, read this
- 158. Tips/ techniques perspective on SA âą Providesa collection of advices from working architects âą If you are already an architect and want to know best practices, read this
- 159. And donât forgetours! Forewords by Grady Booch and Dr. Stephane Ducasse
- 160. What were yourkey takeaways?
- 161. Image Credits âą http://it-ebooks.info/images/ebooks/3/restful_web_services_cookbook.jpg âąhttp://southïŹoridaclassicalreview.com/wp-content/uploads/ 2012/11/03THECLEVELANDORCHESTRA-CPJ.jpg âą http://www.ndepend.com/NS/images/CodeQuery.jpg âą https://www.toadworld.com/cfs-ïŹle/__key/communityserver-blogs-components- weblogïŹles/00-00-00-00-57/DN_2D00_4a.jpg âą http://d152tffy3gbaeg.cloudfront.net/2015/02/AIBA-World-Boxing- Championships.jpg âą http://www.lucidica.com/wp-content/uploads/2014/03/www.jpg âą http://restfulwebapis.org/images/rws-cover.jpg âą http://akamaicovers.oreilly.com/images/0636920021575/cat.gif âą http://it-ebooks.info/images/ebooks/6/pro_rest_api_development_with_node.js.jpg âą https://www.packtpub.com/sites/default/ïŹles/9781783285754.jpg âą https://www.packtpub.com/sites/default/ïŹles/ B04843_RESTful%20Web%20Services%20with%20Scala_.jpg âą http://i.ndtvimg.com/i/2015-02/sholay-still_640x480_61423213425.jpg
- 162. ganesh@codeops.tech @GSamarthyam www.codeops.tech slideshare.net/sgganesh +9198801 64463 bit.ly/sgganesh