1 / 8

Architecture Quality

Architecture Quality. extraordinarily large systems, services, strategic design, scalability and reliability, large datasets, latency, service-oriented systems, manage architectural change, scaling domain driven design. Richard Gabriel - Extraordinarly large systems.

tamera
Download Presentation

Architecture Quality

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Architecture Quality extraordinarily large systems, services, strategic design, scalability and reliability, large datasets, latency, service-oriented systems, manage architectural change, scaling domain driven design

  2. Richard Gabriel - Extraordinarly large systems • Can there be an architecture for extraordinarily large systems? • Does it matter? • Forgiving/unforgiving parts of a system • Path of correctness is wide • Digital evolution/genetic algorithms • Augment modules with; test, repair, clone, suicide.

  3. Nati Shalom - Scaling Tier-based systems • Traditional Tier-based systems suffer from over-communication • Scaling them is painful • 3 steps; • In-memory data grid • Consolidate the ESB and data together • Assemble business logic, data and messaging • Now it is scalable

  4. Eric Evans - Strategic Design • Not all of a large system will be well designed • Domain: A sphere of knowledge, influence , or activity • Model: A system of abstractions that describes selected aspects a domain and can be used to solve problems related to that domain. • Distill the core domain; • What makes your system worth writing? • Why not buy it off the shelf? • Why not outsource it? • Be recognized for what you do!

  5. Cameron Purdy - Scalability and Reliability • Scalability vs. Performance • How to avoid scalability and reliability. By overusing databases for things they are not useful for, and overusing abstraction, and introducing single points of failure, and single points of bottlenecks, and reinventing the wheel by building your own infrastructure • Use common sense (it is not as common as you might think)

  6. Jinesh Varia - Hadoop • Java based framework, that enables you to stop worrying about about details such as concurrency • Another layer of abstraction to enable the database to just be the database (which it is good at)

  7. The speakers of the track today • “Architect for Latency”Dan Pritchett • “Guerrilla SOA”Jim Webber • “How to Work With Business Leaders to Manage Architectural Change”Luke Hohmann • “Scaling Domain Driven Design”Greg Young

  8. Panel this afternoon Moderator: Ramano Rao Panelists: Luke Hohmann, Greg Young, Eric Evans, Nati Shalom, Dan Pritchett • A two-sentence summary of the most important part of their presentation • The most critical things to be thought about in the very early days of a new project or a new cycle.

More Related