Pragmatic Architecture in .NET
Download as pptx, pdf4 likes2,492 views
The document discusses pragmatic architecture approaches in .NET. It outlines three levels of architecture - Level 1 using simple patterns like active record, Level 2 with some separation of concerns, and Level 3 using domain-driven design and other complex patterns. The key points are that the simplest approach that could work is best, context matters, and best practices have both benefits and costs to consider for the project.
1 of 48
Downloaded 58 times
Ad
Recommended
Pragmatic Architecture for Agile Teams - GeeCON 2014
Pragmatic Architecture for Agile Teams - GeeCON 2014Janne Sinivirta The document discusses the importance of pragmatic architecture in agile teams, emphasizing shared responsibility and collaboration among team members rather than relying solely on architects. Key concepts include balancing design methodologies, utilizing domain modeling for clearer communication, and maintaining effective documentation to enhance understanding and decision-making. It serves as a guide to improving architectural practices within agile frameworks, advocating for early prototyping and feedback loops.
Code Review Matters and Manners
Code Review Matters and MannersTrisha Gee The document discusses best practices for code reviews, focusing on key areas such as formatting, design, usability, and functionality. It emphasizes the importance of maintaining proper manners during reviews by providing constructive feedback and fostering a collaborative environment. The authors stress the need to automate checks where possible and to prioritize significant aspects without becoming overly critical of minor details.
Taming Big Balls of Mud with Diligence, Agile Practices, and Hard Work
Taming Big Balls of Mud with Diligence, Agile Practices, and Hard WorkJoseph Yoder The document discusses the challenges of maintaining clean software architecture, referring to poorly structured code as 'big balls of mud' (BBOM) that often arise despite intentions for quality systems. It emphasizes the necessity of agile practices, continuous improvements, and code refactoring to sustain architecture over time, while addressing common coding issues and design principles to enhance code quality. Additionally, it advocates for a shift in mindset towards professionalism and accountability in coding to prevent the build-up of technical debt and maintain a clean codebase.
Level Up Your Automated Tests
Level Up Your Automated TestsTrisha Gee The document discusses ways to improve automated testing practices, such as by making tests easier to write, more readable, and more meaningful. It suggests using mocking frameworks to reduce test complexity, following standards and examples, and adopting a testing framework like Spock that addresses common issues. While progress has been made, there is still work to be done to encourage writing tests, make tests easy to write and understand, and ensure tests are meaningful and focused on the purposes of testing.
Level Up Your Automated Tests
Level Up Your Automated TestsTrisha Gee Trisha Gee discusses the importance of automated testing, addressing common challenges and misconceptions about tests. She offers potential solutions and emphasizes the need for clear, readable, and meaningful tests while advocating for a supportive testing culture. The presentation also highlights resources and encourages participation in related events.
Clean Code and Common Engineering Practices
Clean Code and Common Engineering PracticesRuth Sperer The document focuses on clean code principles, emphasizing readability, error-free code, and meaningful naming conventions. It discusses the importance of code reviews, test-driven development, refactoring, software configuration management, static code analysis, and continuous integration practices. Additionally, it provides guidance on being a good programmer, including respect for predecessors and recommendations for further reading.
Six Steps to Conversation Driven Development
Six Steps to Conversation Driven DevelopmentRasa Technologies This document discusses Conversation-Driven Development (CDD) as a process for building conversational AI assistants. It describes CDD as involving six key actions: sharing prototypes with test users, reviewing user conversations, annotating conversations as training data, testing the assistant, tracking the success of conversations, and fixing issues found. CDD captures lessons learned from building conversational AI to help teams iteratively improve assistants based on user feedback. The document also promotes Rasa X as a tool that can help teams implement CDD through features like reviewing conversations, annotating data, and continuous integration testing.
Scrum + bdd + ddd
Scrum + bdd + dddHelder De Oliveira The document discusses the integration of Scrum, Behavior-Driven Development (BDD), and Domain-Driven Design (DDD) in software development, emphasizing the importance of collaboration, agile principles, and stakeholder involvement. It outlines key concepts and practices related to Scrum and DDD, such as domain models, ubiquitous language, and the use of stories for project management. Additionally, it presents examples of applying BDD to capture requirements and tests in software development processes.
Is your code SOLID enough?
Is your code SOLID enough?SARCCOM The document introduces the SOLID principles in software design, which consists of five key concepts aimed at improving code quality and maintainability. These principles encourage practices such as writing single-responsibility classes and implementing design patterns for better manageability. The aim is to help programmers create more robust, testable, and human-readable code, ultimately combating the common pitfalls of code complexity and redundancy.
Is Groovy better for testing than Java?
Is Groovy better for testing than Java?Trisha Gee The document discusses whether the Groovy programming language is better than Java for testing. It outlines some of the pros and cons of each approach. While Java and JUnit tests are performant and well-supported, Groovy and the Spock testing framework make tests more readable, easier to write, and help describe expected system behavior through features like mocking and hamcrest matchers. Migrating existing Java tests to Groovy would require learning a new language but allow exploring its testing advantages without impacting production code. In conclusion, both have tradeoffs and the best approach depends on the specific project needs and developer preferences.
Tips sukses berkarir sebagai developer dan programmer 2021
Tips sukses berkarir sebagai developer dan programmer 2021DicodingEvent The document outlines the experiences and advice of Andri Suranta Ginting, a mobile engineer at Gojek, focusing on public speaking, networking, and self-learning to enhance career opportunities. It emphasizes the importance of asking questions, sharing thoughts, reading and writing habits, and pair programming while highlighting the need for mentorship and receiving feedback. Additionally, it discusses the significance of both technical and soft skills in the tech industry, advocating persistence and adaptability in the learning process.
Software Development Essential Skills
Software Development Essential SkillsJohn Choi The document discusses essential skills that programmers need versus accidental skills. Essential skills are hard to acquire but long-lasting, including things like managing complexity, writing readable code, and limiting bugs. These skills separate good programmers from bad. Accidental skills like knowledge of a specific programming language are easier to obtain but have shorter usefulness. The document advocates spending time on design, planning, unit testing, discussing solutions with others, and considering alternative solutions rather than just focusing on writing code. Developing essential skills through these practices can help programmers continuously learn and improve over the course of their careers.
The five expertise of a software architect
The five expertise of a software architectLior Bar-On The document discusses the five areas of expertise of a software architect:
1. Technology - Having strong technical skills including writing code, understanding technologies, and solving difficult problems.
2. Technical communication - Effectively communicating technical concepts to both technical and non-technical audiences.
3. Human communication - Having strong empathy, influencing, and communication skills to work with various teams.
4. Domain knowledge - Understanding the business domain including customers, competitors, and market factors.
5. Architectural methods - Applying design principles, patterns, and processes to software architecture.
Test Driven Development
Test Driven DevelopmentSamnang Chhun The document discusses test-driven development (TDD) and design-driven development (DDD). It advocates for writing tests before code using short iterative development cycles. TDD helps produce clean code that fulfills requirements by making developers think about required behavior, providing documentation, and improving quality. Common objections to TDD are addressed, noting that it forces understanding of code and tests, creates reusable modular code, and drives simplicity. Guidelines for effective TDD include writing small focused tests with descriptive intentions that are independent and repeatable.
Deploy your Rasa Chatbots like a Boss with DevOps | Rasa Summit 2021
Deploy your Rasa Chatbots like a Boss with DevOps | Rasa Summit 2021Rasa Technologies The document discusses strategies for deploying Rasa chatbots more efficiently using DevOps practices. It emphasizes the importance of automating training data collection and deployment processes to enable quicker iterations and improvements. Additionally, it highlights the collaboration between developers and non-developers in enhancing chatbot performance through a structured workflow.
Software Craftsmanship VS Software Engineering
Software Craftsmanship VS Software EngineeringAndy Maleh Software craftsmanship and software engineering both aim to deliver high-quality, reliable software, but differ in their approaches. Software engineering focuses on macro goals and processes, while craftsmanship emphasizes mastering skills through experience. Both are used at Groupon, where engineering practices like architecture, testing and iteration are combined with craftsmanship techniques including apprenticeships and pair programming.
Design Smells
Design SmellsGiorgio Vespucci The document outlines seven 'design smells' that indicate poor software design: rigidity, fragility, immobility, viscosity, needless complexity, needless repetition, and opacity. Each smell represents a specific design flaw, highlighting difficulties in change, reuse, complexity, and understanding within the software. The text emphasizes that these smells are symptoms of violations of key design principles.
Mobile engineering at GOJEK Scale
Mobile engineering at GOJEK Scaleraditya gumay The document discusses mobile engineering at scale at Go-jek. It outlines Go-jek's mobile app milestones from 2010 to 2018. It then discusses challenges of engineering at scale, including that having many engineers does not necessarily mean faster feature delivery. It recommends centralizing engineers and sharing code between features to address these challenges. It also discusses problems like semantic versioning, slow builds, and onboarding. It provides solutions like monorepos and clean architecture to address these problems. It emphasizes the importance of testing, team collaboration, and referencing best practices.
Good Code / Bad Code
Good Code / Bad CodeKelly Harrop The document discusses the importance of a common framework for aligning designers and developers on quality coding standards. It emphasizes that bad code can hinder good design and innovation, while good code can mitigate design flaws. The S.P.A.D.E framework is introduced to assess code quality across various dimensions, including scalability, polish, accessibility, documentation, and efficiency.
How to sustain a tool building community-driven effort
How to sustain a tool building community-driven effortJordi Cabot This document discusses key dimensions for sustaining a tool building community-driven effort based on experiences developing modeling tools. It covers onboarding users and contributors, governance models, community health analysis using graph techniques, and optimization strategies. The document advocates an entrepreneurial path for tool development by releasing prototypes as open source software and improving them for real use cases to build a community and offer commercial services.
Low-code vs Model-Driven Engineering
Low-code vs Model-Driven EngineeringJordi Cabot This document discusses the relationship between low-code development and model-driven engineering (MDE). It notes that low-code is essentially a style of model-driven development focused on specific application types using a fixed language. While low-code tools have improved, the core concepts of modeling and code generation from models have existed in MDE research since the 1980s. The document argues low-code is worth studying from social and economic perspectives but does not present significant new technical challenges for MDE research. However, low-code popularity could help bring modeling expertise to new domains and communities. Researchers should monitor no-code tools which may evolve low-code further.
(A)TDD The what, why and how
(A)TDD The what, why and howAlexander van Trijffel This document discusses Acceptance Test Driven Development (ATDD), Behavior Driven Development (BDD), and Test Driven Development (TDD). ATDD uses automated acceptance tests defined early in development to ensure all stakeholders understand requirements. BDD uses a Given/When/Then framework to define automated acceptance tests that assert system functionality. SpecFlow is a tool that allows testers, analysts, and developers to collaborate on BDD feature files and step definitions. TDD involves writing automated tests before code to improve quality and support refactoring through the "Red-Green-Refactor" cycle. The document demonstrates SpecFlow with an example of a movie ticketing system.
Software quality
Software quality5minpause The document discusses the challenges of software quality in development projects, highlighting the importance of good coding practices and team communication. It emphasizes the concept of technical debt and mentions several well-known coding principles and rules from experts like Kent Beck and Sandi Metz that can help produce simpler and more maintainable code. Ultimately, it encourages developers to adapt and create their own rules while utilizing tools to measure and improve their coding practices.
Software development fundamentals
Software development fundamentalsAlfred Jett Grandeza The document provides an overview of software development fundamentals, covering topics such as programming languages, data types, object-oriented principles, and industry expectations. It emphasizes the need for understanding core programming concepts like variables, control structures, exception handling, and design principles such as S.O.L.I.D. The speaker encourages active participation and continuous learning, highlighting the importance of mastering programming languages and best practices.
A CQRS Journey
A CQRS JourneyChrysovalantis Koutsoumpos This document provides an introduction to CQRS (Command Query Responsibility Segregation), an architectural pattern that separates read and write operations into different models. It discusses the motivation for using CQRS including improved performance, scalability, and testability. Some potential downsides are increased complexity and the need to embrace eventual consistency. The document explains key CQRS concepts like commands, queries, and event sourcing. It also compares CQRS to other architectural patterns like hexagonal architecture, onion architecture, and MVC.
Using Rasa to Power an Immersive Multimedia Conversational Experience | Rasa ...
Using Rasa to Power an Immersive Multimedia Conversational Experience | Rasa ...Rasa Technologies Nathan Stratton, a five-time startup leader and founder of Vocinity, focuses on enhancing customer engagement through a voice and video platform. His innovations include pioneering VoIP technologies and addressing modern customer experience needs with personalized, interactive content. While promoting the advantages of video for brand engagement, the platform also aims to overcome challenges like real-time interaction complexities and the evolving capabilities of digital human avatars.
How to become a software developer
How to become a software developerEyob Lube This document provides information on how to become a software developer. It begins with an introduction that defines a software developer and notes they design, implement, and test software. It also provides the median salary range of $84,200 and high job growth of 24.6% expected through 2020. The document then outlines the roles and responsibilities of a software developer, and the requirements which do not necessarily include a computer science degree. It provides 10 steps to become a software developer including choosing a pet project, learning from books and online courses, implementing the pet project, asking questions online, and contributing to open source projects. It concludes with a list of free resources for learning C#.
Clean code and Coding Standards
Clean code and Coding StandardsMahesh Salaria The document discusses clean coding standards and best practices. It recommends following the Boy Scout Rule of leaving the code cleaner than you found it. It discusses using meaningful names for classes, methods, and variables without encodings. Functions should do one thing, use descriptive names, and avoid repeating code. Comments should explain intent, not make up for bad code. Error handling prefers exceptions over return codes. Formatting and style rules should be consistent within a team. Coding standards exist for many languages like Java, PHP, C#, Android and others.
Pragmatic Architecture
Pragmatic Architectureguestedb3ee The document outlines the expertise and credentials of Ted Neward, an independent consultant and architect, who discusses the role and significance of software architecture. It examines the principles of pragmatic architecture, the qualities of a good architect, and the distinctions between different types of architects. Additionally, it emphasizes the importance of defining architecture explicitly to avoid unintentional implications and ensure clarity in software design.
Pragmatic Architecture, Today (v2)
Pragmatic Architecture, Today (v2)Bart Blommaerts The document discusses pragmatic architecture, emphasizing the need for architectural viewpoints, stakeholder involvement, and iterative communication throughout the software development process. It highlights the importance of visualizations, decision logging, and just enough up-front design to build effective software systems that can evolve over time. Additionally, it addresses challenges related to politics and stakeholder engagement in architectural decision-making.
More Related Content
What's hot (20)
Is your code SOLID enough?
Is your code SOLID enough?SARCCOM The document introduces the SOLID principles in software design, which consists of five key concepts aimed at improving code quality and maintainability. These principles encourage practices such as writing single-responsibility classes and implementing design patterns for better manageability. The aim is to help programmers create more robust, testable, and human-readable code, ultimately combating the common pitfalls of code complexity and redundancy.
Is Groovy better for testing than Java?
Is Groovy better for testing than Java?Trisha Gee The document discusses whether the Groovy programming language is better than Java for testing. It outlines some of the pros and cons of each approach. While Java and JUnit tests are performant and well-supported, Groovy and the Spock testing framework make tests more readable, easier to write, and help describe expected system behavior through features like mocking and hamcrest matchers. Migrating existing Java tests to Groovy would require learning a new language but allow exploring its testing advantages without impacting production code. In conclusion, both have tradeoffs and the best approach depends on the specific project needs and developer preferences.
Tips sukses berkarir sebagai developer dan programmer 2021
Tips sukses berkarir sebagai developer dan programmer 2021DicodingEvent The document outlines the experiences and advice of Andri Suranta Ginting, a mobile engineer at Gojek, focusing on public speaking, networking, and self-learning to enhance career opportunities. It emphasizes the importance of asking questions, sharing thoughts, reading and writing habits, and pair programming while highlighting the need for mentorship and receiving feedback. Additionally, it discusses the significance of both technical and soft skills in the tech industry, advocating persistence and adaptability in the learning process.
Software Development Essential Skills
Software Development Essential SkillsJohn Choi The document discusses essential skills that programmers need versus accidental skills. Essential skills are hard to acquire but long-lasting, including things like managing complexity, writing readable code, and limiting bugs. These skills separate good programmers from bad. Accidental skills like knowledge of a specific programming language are easier to obtain but have shorter usefulness. The document advocates spending time on design, planning, unit testing, discussing solutions with others, and considering alternative solutions rather than just focusing on writing code. Developing essential skills through these practices can help programmers continuously learn and improve over the course of their careers.
The five expertise of a software architect
The five expertise of a software architectLior Bar-On The document discusses the five areas of expertise of a software architect:
1. Technology - Having strong technical skills including writing code, understanding technologies, and solving difficult problems.
2. Technical communication - Effectively communicating technical concepts to both technical and non-technical audiences.
3. Human communication - Having strong empathy, influencing, and communication skills to work with various teams.
4. Domain knowledge - Understanding the business domain including customers, competitors, and market factors.
5. Architectural methods - Applying design principles, patterns, and processes to software architecture.
Test Driven Development
Test Driven DevelopmentSamnang Chhun The document discusses test-driven development (TDD) and design-driven development (DDD). It advocates for writing tests before code using short iterative development cycles. TDD helps produce clean code that fulfills requirements by making developers think about required behavior, providing documentation, and improving quality. Common objections to TDD are addressed, noting that it forces understanding of code and tests, creates reusable modular code, and drives simplicity. Guidelines for effective TDD include writing small focused tests with descriptive intentions that are independent and repeatable.
Deploy your Rasa Chatbots like a Boss with DevOps | Rasa Summit 2021
Deploy your Rasa Chatbots like a Boss with DevOps | Rasa Summit 2021Rasa Technologies The document discusses strategies for deploying Rasa chatbots more efficiently using DevOps practices. It emphasizes the importance of automating training data collection and deployment processes to enable quicker iterations and improvements. Additionally, it highlights the collaboration between developers and non-developers in enhancing chatbot performance through a structured workflow.
Software Craftsmanship VS Software Engineering
Software Craftsmanship VS Software EngineeringAndy Maleh Software craftsmanship and software engineering both aim to deliver high-quality, reliable software, but differ in their approaches. Software engineering focuses on macro goals and processes, while craftsmanship emphasizes mastering skills through experience. Both are used at Groupon, where engineering practices like architecture, testing and iteration are combined with craftsmanship techniques including apprenticeships and pair programming.
Design Smells
Design SmellsGiorgio Vespucci The document outlines seven 'design smells' that indicate poor software design: rigidity, fragility, immobility, viscosity, needless complexity, needless repetition, and opacity. Each smell represents a specific design flaw, highlighting difficulties in change, reuse, complexity, and understanding within the software. The text emphasizes that these smells are symptoms of violations of key design principles.
Mobile engineering at GOJEK Scale
Mobile engineering at GOJEK Scaleraditya gumay The document discusses mobile engineering at scale at Go-jek. It outlines Go-jek's mobile app milestones from 2010 to 2018. It then discusses challenges of engineering at scale, including that having many engineers does not necessarily mean faster feature delivery. It recommends centralizing engineers and sharing code between features to address these challenges. It also discusses problems like semantic versioning, slow builds, and onboarding. It provides solutions like monorepos and clean architecture to address these problems. It emphasizes the importance of testing, team collaboration, and referencing best practices.
Good Code / Bad Code
Good Code / Bad CodeKelly Harrop The document discusses the importance of a common framework for aligning designers and developers on quality coding standards. It emphasizes that bad code can hinder good design and innovation, while good code can mitigate design flaws. The S.P.A.D.E framework is introduced to assess code quality across various dimensions, including scalability, polish, accessibility, documentation, and efficiency.
How to sustain a tool building community-driven effort
How to sustain a tool building community-driven effortJordi Cabot This document discusses key dimensions for sustaining a tool building community-driven effort based on experiences developing modeling tools. It covers onboarding users and contributors, governance models, community health analysis using graph techniques, and optimization strategies. The document advocates an entrepreneurial path for tool development by releasing prototypes as open source software and improving them for real use cases to build a community and offer commercial services.
Low-code vs Model-Driven Engineering
Low-code vs Model-Driven EngineeringJordi Cabot This document discusses the relationship between low-code development and model-driven engineering (MDE). It notes that low-code is essentially a style of model-driven development focused on specific application types using a fixed language. While low-code tools have improved, the core concepts of modeling and code generation from models have existed in MDE research since the 1980s. The document argues low-code is worth studying from social and economic perspectives but does not present significant new technical challenges for MDE research. However, low-code popularity could help bring modeling expertise to new domains and communities. Researchers should monitor no-code tools which may evolve low-code further.
(A)TDD The what, why and how
(A)TDD The what, why and howAlexander van Trijffel This document discusses Acceptance Test Driven Development (ATDD), Behavior Driven Development (BDD), and Test Driven Development (TDD). ATDD uses automated acceptance tests defined early in development to ensure all stakeholders understand requirements. BDD uses a Given/When/Then framework to define automated acceptance tests that assert system functionality. SpecFlow is a tool that allows testers, analysts, and developers to collaborate on BDD feature files and step definitions. TDD involves writing automated tests before code to improve quality and support refactoring through the "Red-Green-Refactor" cycle. The document demonstrates SpecFlow with an example of a movie ticketing system.
Software quality
Software quality5minpause The document discusses the challenges of software quality in development projects, highlighting the importance of good coding practices and team communication. It emphasizes the concept of technical debt and mentions several well-known coding principles and rules from experts like Kent Beck and Sandi Metz that can help produce simpler and more maintainable code. Ultimately, it encourages developers to adapt and create their own rules while utilizing tools to measure and improve their coding practices.
Software development fundamentals
Software development fundamentalsAlfred Jett Grandeza The document provides an overview of software development fundamentals, covering topics such as programming languages, data types, object-oriented principles, and industry expectations. It emphasizes the need for understanding core programming concepts like variables, control structures, exception handling, and design principles such as S.O.L.I.D. The speaker encourages active participation and continuous learning, highlighting the importance of mastering programming languages and best practices.
A CQRS Journey
A CQRS JourneyChrysovalantis Koutsoumpos This document provides an introduction to CQRS (Command Query Responsibility Segregation), an architectural pattern that separates read and write operations into different models. It discusses the motivation for using CQRS including improved performance, scalability, and testability. Some potential downsides are increased complexity and the need to embrace eventual consistency. The document explains key CQRS concepts like commands, queries, and event sourcing. It also compares CQRS to other architectural patterns like hexagonal architecture, onion architecture, and MVC.
Using Rasa to Power an Immersive Multimedia Conversational Experience | Rasa ...
Using Rasa to Power an Immersive Multimedia Conversational Experience | Rasa ...Rasa Technologies Nathan Stratton, a five-time startup leader and founder of Vocinity, focuses on enhancing customer engagement through a voice and video platform. His innovations include pioneering VoIP technologies and addressing modern customer experience needs with personalized, interactive content. While promoting the advantages of video for brand engagement, the platform also aims to overcome challenges like real-time interaction complexities and the evolving capabilities of digital human avatars.
How to become a software developer
How to become a software developerEyob Lube This document provides information on how to become a software developer. It begins with an introduction that defines a software developer and notes they design, implement, and test software. It also provides the median salary range of $84,200 and high job growth of 24.6% expected through 2020. The document then outlines the roles and responsibilities of a software developer, and the requirements which do not necessarily include a computer science degree. It provides 10 steps to become a software developer including choosing a pet project, learning from books and online courses, implementing the pet project, asking questions online, and contributing to open source projects. It concludes with a list of free resources for learning C#.
Clean code and Coding Standards
Clean code and Coding StandardsMahesh Salaria The document discusses clean coding standards and best practices. It recommends following the Boy Scout Rule of leaving the code cleaner than you found it. It discusses using meaningful names for classes, methods, and variables without encodings. Functions should do one thing, use descriptive names, and avoid repeating code. Comments should explain intent, not make up for bad code. Error handling prefers exceptions over return codes. Formatting and style rules should be consistent within a team. Coding standards exist for many languages like Java, PHP, C#, Android and others.
Viewers also liked (7)
Pragmatic Architecture
Pragmatic Architectureguestedb3ee The document outlines the expertise and credentials of Ted Neward, an independent consultant and architect, who discusses the role and significance of software architecture. It examines the principles of pragmatic architecture, the qualities of a good architect, and the distinctions between different types of architects. Additionally, it emphasizes the importance of defining architecture explicitly to avoid unintentional implications and ensure clarity in software design.
Pragmatic Architecture, Today (v2)
Pragmatic Architecture, Today (v2)Bart Blommaerts The document discusses pragmatic architecture, emphasizing the need for architectural viewpoints, stakeholder involvement, and iterative communication throughout the software development process. It highlights the importance of visualizations, decision logging, and just enough up-front design to build effective software systems that can evolve over time. Additionally, it addresses challenges related to politics and stakeholder engagement in architectural decision-making.
Modelo de expediente para arquitectura
Modelo de expediente para arquitecturaDanny Guevara Este documento describe la construcción de un cerco perimétrico para un lote ubicado en la urbanización Praderas del Golf en Trujillo, Perú. El cerco tendrá una altura de 2.60 metros y se construirá con ladrillos sin quemar sobre una cimentación corrida. El presupuesto total para la construcción es de S/6,831.88 y se financiará con fondos propios, con un plazo de ejecución de 3 días.
ea2009 Enterprise Architecture keynote Final
ea2009 Enterprise Architecture keynote FinalMarc Caltabiano The document discusses pragmatic enterprise architecture, emphasizing its importance in aligning business strategy with IT initiatives to enhance efficiency and innovation. It outlines guiding principles, the roles of various architects, and various frameworks applicable to enterprise architecture. The text advocates for a simplified and flexible approach to enterprise architecture, with a focus on just-in-time solutions and iterative improvements to accommodate changing business needs and technologies.
Teoria funcional
Teoria funcionalenrique miranda El documento presenta los conceptos fundamentales de la arquitectura, incluyendo su definición tripartita según Vitrubio como utilidad, solidez y belleza. Explica que la función es la utilidad pragmática de un edificio y describe sus variantes (función pragmática, de circulación, simbólica y psicológica). También describe los elementos, cualidades y criterios que componen los sistemas de ordenamiento funcional para el proyecto de un edificio, como las actividades, relaciones y métodos para ordenarlas como diagramas de burbujas
Metodos de diseño arquitectonico
Metodos de diseño arquitectonicoVianey Isabel Mujica Campos El documento explica que el método de diseño involucra producir dibujos para clientes y fabricantes. Define los factores naturales y culturales, el programa, y la tecnología como componentes clave del proceso de diseño. Además, introduce cinco tipos de diseño: pragmático, analógico, icónico, canónico y tipológico.
Proceso metodológico del diseño arquitectónico
Proceso metodológico del diseño arquitectónicoJorge Granados Valencia El documento presenta la metodología de un curso de diseño arquitectónico. El objetivo general es que los estudiantes evalúen el espacio arquitectónico y el proceso de diseño para desarrollar proyectos que enfatizan la funcionalidad, forma y aspectos contextuales y constructivos. Se describen los objetivos de conocimiento, habilidad y actitud, así como las etapas de investigación, análisis, metodología de diseño, conceptualización y diseño que conforman el proceso de desarrollo de un proyecto arquitect
Ad
Similar to Pragmatic Architecture in .NET (20)
Elements of DDD with ASP.NET MVC & Entity Framework Code First
Elements of DDD with ASP.NET MVC & Entity Framework Code FirstEnea Gabriel The document discusses elements of Domain-Driven Design (DDD) when building applications with ASP.NET MVC and Entity Framework Code First. It emphasizes modeling the application around the business domain, using tools like EF Code First and dependency injection frameworks to decouple layers and enable unit testing. The presentation provides an overview of DDD concepts and techniques for applying them with ASP.NET MVC and EF Code First to build loosely coupled, testable architectures focused on the business domain.
Day1
Day1madamewoolf The document summarizes a lecture on enterprise web application architecture and design. It discusses key topics like architectural patterns, object-oriented design principles, UML diagrams, and the .NET framework. Students will work in groups of 3 on a semester-long project to build a web application prototype. They are given examples of possible projects and an overview of the topics that will be covered each lecture day.
2010-07-19_rails_tdd_week1
2010-07-19_rails_tdd_week1Wolfram Arnold This document outlines a curriculum for a course on efficient test-driven development (TDD) in Rails, detailing weekly topics such as testing strategies, TDD culture, API testing, and integration testing. The course emphasizes the economics of testing, the importance of testing for maintaining code quality, and includes structured exercises for practical application. It promotes active participation and collaboration among participants to foster a productive learning environment.
J2EE Performance And Scalability Bp
J2EE Performance And Scalability BpChris Adkin This document outlines best practices for performance and scalability in J2EE applications, primarily based on the author's experience with IBM WebSphere. It covers key areas including requirements capture, architectural design, and implementation, with specific attention to avoid distributed architectures, the importance of caching, and leveraging design patterns for efficiency. The document also emphasizes the need for a balanced approach between maintaining code elegance and achieving performance, alongside recommendations for practical implementation strategies.
SPCA2013 - Test-driven Development with SharePoint 2013 and Visual Studio
SPCA2013 - Test-driven Development with SharePoint 2013 and Visual StudioNCCOMMS This document discusses test-driven development (TDD) approaches for SharePoint projects using Visual Studio. It begins with an introduction to TDD and the benefits it provides. It then covers different types of tests like unit, integration, and acceptance tests. It demonstrates how to write server-side and client-side tests for SharePoint. Finally, it discusses test automation tools and concludes that while SharePoint presents challenges for testing, TDD is still very valuable when developing for the platform.
Usemon; Building The Big Brother Of The Java Virtual Machinve
Usemon; Building The Big Brother Of The Java Virtual MachinvePaul René Jørgensen This document discusses Usemon, a tool for monitoring Java applications. Usemon works by inserting itself into the Java virtual machine as an agent and modifying bytecode during class loading. It collects data on method invocations, dependencies, and heap usage and multicasts the observations to a collector. The collector caches, reorganizes, and stores the data, which can then be analyzed using OLAP tools to identify performance bottlenecks and exceptions in enterprise Java applications. A proof of concept real-time visualization of class dependencies is also presented.
Application Architecture April 2014
Application Architecture April 2014Lars-Erik Kindblad This document discusses best practices for application architecture, including:
- Using inversion of control and dependency injection to create loosely coupled and testable code
- Applying the single responsibility principle to have focused classes that are easier to maintain
- Employing patterns like extract method and execute around method to reduce code duplication
- Structuring applications using architectures like onion architecture or n-tier to organize code clearly
- Logging executed use cases/events for replay testing before releases to check for bugs
Asp.Net_ Developer Resume Remotely
Asp.Net_ Developer Resume RemotelySumitKumar2504 Sumit Kumar is a highly organized software engineer with over 8 years of experience in programming and database management, skilled in languages like C# and frameworks such as .NET. He has worked on various projects across multiple domains, demonstrating proficiency in API integration, data access, and application performance optimization. His certifications include Microsoft Certified Professional and Microsoft Certified Solution Developer, with a strong track record in mentoring and leading software development teams.
Latest trends in information technology
Latest trends in information technologyEldos Kuriakose The document discusses recent trends in the IT industry including cloud computing, mobile applications, Agile methodology (Scrum), N-tier architecture, and Java vs .NET. It covers topics such as cloud computing fundamentals and features, social networking sites, mobile app development and monetization, the shift from waterfall to Agile development, Scrum processes, Agile principles, N-tier architecture, advantages of both Java and .NET, and the continued relevance of object-oriented design.
MongoDB Evenings Toronto - Monolithic to Microservices with MongoDB
MongoDB Evenings Toronto - Monolithic to Microservices with MongoDBMongoDB The document discusses the transition from monolithic applications to microservices, outlining the pros and cons of both architectures. It highlights the importance of using MongoDB for developing scalable, flexible services with rich data structures. The document also emphasizes the challenges faced in monitoring, operational overhead, and organizational shifts involved in adopting microservices.
Linq To The Enterprise
Linq To The EnterpriseDaniel Egan The document provides a biography and background information on Daniel N. Egan, including his roles as a Microsoft Regional Director, Microsoft MVP for ASP.Net, author, and speaker. It then outlines the topics to be covered in the presentation, including object relational mappers, language enhancements in C# and VB.Net, LINQ goals, fundamentals and usage.
IT Modernization For Process Modernization
IT Modernization For Process ModernizationDheeraj Remella The document discusses strategies for modernizing legacy IT systems, emphasizing the importance of understanding organizational people, processes, and risk management. It outlines a methodology for transformation that includes assessing business processes, reducing risks, and calculating return on investment. Nexaweb Technologies offers cloud transformation services with a repeatable approach, aiming to convert outdated applications into modern solutions quickly and efficiently.
Whats New In 2010 (Msdn & Visual Studio)
Whats New In 2010 (Msdn & Visual Studio)Steve Lange This document provides an overview and summary of new features in Visual Studio 2010 and Team Foundation Server 2010. It begins with introducing the product lineup and changes to MSDN subscriptions. Major sections then summarize new capabilities in project management, reporting, version control, architecture/modeling tools, development aids like profiling and testing tools like lab management and coded UI tests. The document aims to outline the key updates and highlights for developers across the application lifecycle with Visual Studio 2010 and TFS.
CV_SwapnilGupta
CV_SwapnilGuptaSwapnil Gupta Swapnil Gupta is seeking a challenging position in the software industry that allows for innovation, creativity, dedication, and continuous learning. He has over 9 years of experience developing web and Windows applications using Microsoft technologies like C#, .NET, MVC, ASP.NET, SQL Server, and more. He has experience in the full software development lifecycle and a proven record of delivering business value through information technology.
RailswayCon 2010 - Command Your Domain
RailswayCon 2010 - Command Your DomainLourens Naudé The document discusses domain-driven design and moving away from monolithic applications. It recommends modeling the domain first before coding, focusing on behaviors and responsibilities over data. Events and commands should be used to drive changes rather than CRUD operations. An event-driven and message-based architecture is advocated to improve performance, testing and relaxed consistency. Domain events should be used instead of directly saving to the database.
The Magic Of Application Lifecycle Management In Vs Public
The Magic Of Application Lifecycle Management In Vs PublicDavid Solivan The document discusses challenges with software development projects and how tools from Microsoft can help address these challenges. It notes that most projects fail or are over budget and challenges include poor requirements gathering and testing. However, tools like Visual Studio and Team Foundation Server that integrate requirements, work tracking, source control, testing and other functions can help make successful projects more possible by facilitating team collaboration. The document outlines features of these tools and how they aim to make application lifecycle management a routine part of development.
Syllabus for Technical courses
Syllabus for Technical coursesMontek1Learning This document outlines the syllabus for various technical courses including PHP basics, HTML, CSS, JavaScript, PHP advance training, Java, Oracle 10G, Android, cloud computing, and web & graphics designing. It provides details on topics that will be covered in each course such as PHP scripting, control structures, strings, functions, arrays, cookies, sessions, AJAX, frameworks, servlets, JSP, SQL, activities, UI design, telephony, SMS, storage, publishing, and more. It also lists software that will be used like Eclipse, JUnit, Google App Engine, and outlines key takeaways for participants.
Shaloo Verma
Shaloo VermaShaloo Verma Shaloo Verma has over 3 years of experience in software development and testing using languages like Python, C, C++, C#, ASP.Net, and databases like MySQL and Oracle. She has worked on projects involving requirements analysis, design, testing, maintenance and cloud deployment. Currently she is an Associate Software Development in Test at Quick Heal Technologies where she has developed automation frameworks for testing and implemented features like generic registry cleaning and malware detection.
Kasi Resume
Kasi Resumekasi reddy K. Chinna Kasi has over 6 years of experience as a Senior Testing Engineer working on automation testing projects using Selenium and manual testing. He has extensive experience with C#, ASP.NET, MVC, Java, SQL, Visual Studio, TFS, and Quality Center. Some of his project experience includes working on the Dell.com responsive learning site and an ASTTRA finance application. He is proficient in test case design, defect tracking, and Agile methodologies like Scrum.
Onion Architecture with S#arp
Onion Architecture with S#arpGary Pedretti The document discusses implementing the Onion Architecture using the s#arp framework, focusing on its benefits for developing maintainable web applications. Key principles include a separation of concerns, a domain-driven design, and the ability to run core application code independently of infrastructure. It highlights various domain logic patterns and outlines how s#arp contributes to setting up robust application architecture with additional templates and configurations.
Ad
Recently uploaded (20)
FIDO Seminar: Authentication for a Billion Consumers - Amazon.pptx
FIDO Seminar: Authentication for a Billion Consumers - Amazon.pptxFIDO Alliance FIDO Seminar: Authentication for a Billion Consumers - Amazon
OpenPOWER Foundation & Open-Source Core Innovations
OpenPOWER Foundation & Open-Source Core InnovationsIBM penPOWER offers a fully open, royalty-free CPU architecture for custom chip design.
It enables both lightweight FPGA cores (like Microwatt) and high-performance processors (like POWER10).
Developers have full access to source code, specs, and tools for end-to-end chip creation.
It supports AI, HPC, cloud, and embedded workloads with proven performance.
Backed by a global community, it fosters innovation, education, and collaboration.
Creating Inclusive Digital Learning with AI: A Smarter, Fairer Future
Creating Inclusive Digital Learning with AI: A Smarter, Fairer FutureImpelsys Inc. Have you ever struggled to read a tiny label on a medicine box or tried to navigate a confusing website? Now imagine if every learning experience felt that way—every single day.
For millions of people living with disabilities, poorly designed content isn’t just frustrating. It’s a barrier to growth. Inclusive learning is about fixing that. And today, AI is helping us build digital learning that’s smarter, kinder, and accessible to everyone.
Accessible learning increases engagement, retention, performance, and inclusivity for everyone. Inclusive design is simply better design.
Improving Data Integrity: Synchronization between EAM and ArcGIS Utility Netw...
Improving Data Integrity: Synchronization between EAM and ArcGIS Utility Netw...Safe Software Utilities and water companies play a key role in the creation of clean drinking water. The creation and maintenance of clean drinking water is becoming a critical problem due to pollution and pressure on the environment. A lot of data is necessary to create clean drinking water. For fieldworkers, two types of data are key: Asset data in an asset management system (EAM for example) and Geographic data in a GIS (ArcGIS Utility Network ). Keeping this type of data up to date and in sync is a challenge for many organizations, leading to duplicating data and creating a bulk of extra attributes and data to keep everything in sync. Using FME, it is possible to synchronize Enterprise Asset Management (EAM) data with the ArcGIS Utility Network in real time. Changes (creation, modification, deletion) in ArcGIS Pro are relayed to EAM via FME, and vice versa. This ensures continuous synchronization of both systems without daily bulk updates, minimizes risks, and seamlessly integrates with ArcGIS Utility Network services. This presentation focuses on the use of FME at a Dutch water company, to create a sync between the asset management and GIS.
Raman Bhaumik - Passionate Tech Enthusiast
Raman Bhaumik - Passionate Tech EnthusiastRaman Bhaumik A Junior Software Developer with a flair for innovation, Raman Bhaumik excels in delivering scalable web solutions. With three years of experience and a solid foundation in Java, Python, JavaScript, and SQL, she has streamlined task tracking by 20% and improved application stability.
AI vs Human Writing: Can You Tell the Difference?
AI vs Human Writing: Can You Tell the Difference?Shashi Sathyanarayana, Ph.D This slide illustrates a side-by-side comparison between human-written, AI-written, and ambiguous content. It highlights subtle cues that help readers assess authenticity, raising essential questions about the future of communication, trust, and thought leadership in the age of generative AI.
AI VIDEO MAGAZINE - June 2025 - r/aivideo
AI VIDEO MAGAZINE - June 2025 - r/aivideo1pcity Studios, Inc AI VIDEO MAGAZINE - r/aivideo community newsletter – Exclusive Tutorials: How to make an AI VIDEO from scratch, PLUS: How to make AI MUSIC, Hottest ai videos of 2025, Exclusive Interviews, New Tools, Previews, and MORE - JUNE 2025 ISSUE -
9-1-1 Addressing: End-to-End Automation Using FME
9-1-1 Addressing: End-to-End Automation Using FMESafe Software This session will cover a common use case for local and state/provincial governments who create and/or maintain their 9-1-1 addressing data, particularly address points and road centerlines. In this session, you'll learn how FME has helped Shelby County 9-1-1 (TN) automate the 9-1-1 addressing process; including automatically assigning attributes from disparate sources, on-the-fly QAQC of said data, and reporting. The FME logic that this presentation will cover includes: Table joins using attributes and geometry, Looping in custom transformers, Working with lists and Change detection.
The Future of Technology: 2025-2125 by Saikat Basu.pdf
The Future of Technology: 2025-2125 by Saikat Basu.pdfSaikat Basu A peek into the next 100 years of technology. From Generative AI to Global AI networks to Martian Colonisation to Interstellar exploration to Industrial Nanotechnology to Artificial Consciousness, this is a journey you don't want to miss. Which ones excite you the most? Which ones are you apprehensive about? Feel free to comment! Let the conversation begin!
From Manual to Auto Searching- FME in the Driver's Seat
From Manual to Auto Searching- FME in the Driver's SeatSafe Software Finding a specific car online can be a time-consuming task, especially when checking multiple dealer websites. A few years ago, I faced this exact problem while searching for a particular vehicle in New Zealand. The local classified platform, Trade Me (similar to eBay), wasn’t yielding any results, so I expanded my search to second-hand dealer sites—only to realise that periodically checking each one was going to be tedious. That’s when I noticed something interesting: many of these websites used the same platform to manage their inventories. Recognising this, I reverse-engineered the platform’s structure and built an FME workspace that automated the search process for me. By integrating API calls and setting up periodic checks, I received real-time email alerts when matching cars were listed. In this presentation, I’ll walk through how I used FME to save hours of manual searching by creating a custom car-finding automation system. While FME can’t buy a car for you—yet—it can certainly help you find the one you’re after!
Security Tips for Enterprise Azure Solutions
Security Tips for Enterprise Azure SolutionsMichele Leroux Bustamante Delivering solutions to Azure may involve a variety of architecture patterns involving your applications, APIs data and associated Azure resources that comprise the solution. This session will use reference architectures to illustrate the security considerations to protect your Azure resources and data, how to achieve Zero Trust, and why it matters. Topics covered will include specific security recommendations for types Azure resources and related network security practices. The goal is to give you a breadth of understanding as to typical security requirements to meet compliance and security controls in an enterprise solution.
Tech-ASan: Two-stage check for Address Sanitizer - Yixuan Cao.pdf
Tech-ASan: Two-stage check for Address Sanitizer - Yixuan Cao.pdfcaoyixuan2019 A presentation at Internetware 2025.
FIDO Seminar: Perspectives on Passkeys & Consumer Adoption.pptx
FIDO Seminar: Perspectives on Passkeys & Consumer Adoption.pptxFIDO Alliance FIDO Seminar: Perspectives on Passkeys & Consumer Adoption
OWASP Barcelona 2025 Threat Model Library
OWASP Barcelona 2025 Threat Model LibraryPetraVukmirovic Threat Model Library Launch at OWASP Barcelona 2025
https://owasp.org/www-project-threat-model-library/
Coordinated Disclosure for ML - What's Different and What's the Same.pdf
Coordinated Disclosure for ML - What's Different and What's the Same.pdfPriyanka Aash Coordinated Disclosure for ML - What's Different and What's the Same
Curietech AI in action - Accelerate MuleSoft development
Curietech AI in action - Accelerate MuleSoft developmentshyamraj55 CurieTech AI in Action – Accelerate MuleSoft Development
Overview:
This presentation demonstrates how CurieTech AI’s purpose-built agents empower MuleSoft developers to create integration workflows faster, more accurately, and with less manual effort
linkedin.com
+12
curietech.ai
+12
meetups.mulesoft.com
+12
.
Key Highlights:
Dedicated AI agents for every stage: Coding, Testing (MUnit), Documentation, Code Review, and Migration
curietech.ai
+7
curietech.ai
+7
medium.com
+7
DataWeave automation: Generate mappings from tables or samples—95%+ complete within minutes
linkedin.com
+7
curietech.ai
+7
medium.com
+7
Integration flow generation: Auto-create Mule flows based on specifications—speeds up boilerplate development
curietech.ai
+1
medium.com
+1
Efficient code reviews: Gain intelligent feedback on flows, patterns, and error handling
youtube.com
+8
curietech.ai
+8
curietech.ai
+8
Test & documentation automation: Auto-generate MUnit test cases, sample data, and detailed docs from code
curietech.ai
+5
curietech.ai
+5
medium.com
+5
Why Now?
Achieve 10× productivity gains, slashing development time from hours to minutes
curietech.ai
+3
curietech.ai
+3
medium.com
+3
Maintain high accuracy with code quality matching or exceeding manual efforts
curietech.ai
+2
curietech.ai
+2
curietech.ai
+2
Ideal for developers, architects, and teams wanting to scale MuleSoft projects with AI efficiency
Conclusion:
CurieTech AI transforms MuleSoft development into an AI-accelerated workflow—letting you focus on innovation, not repetition.
MuleSoft for AgentForce : Topic Center and API Catalog
MuleSoft for AgentForce : Topic Center and API Catalogshyamraj55 This presentation dives into how MuleSoft empowers AgentForce with organized API discovery and streamlined integration using Topic Center and the API Catalog. Learn how these tools help structure APIs around business needs, improve reusability, and simplify collaboration across teams. Ideal for developers, architects, and business stakeholders looking to build a connected and scalable API ecosystem within AgentForce.
Securing Account Lifecycles in the Age of Deepfakes.pptx
Securing Account Lifecycles in the Age of Deepfakes.pptxFIDO Alliance Securing Account Lifecycles in the Age of Deepfakes
OpenACC and Open Hackathons Monthly Highlights June 2025
OpenACC and Open Hackathons Monthly Highlights June 2025OpenACC The OpenACC organization focuses on enhancing parallel computing skills and advancing interoperability in scientific applications through hackathons and training. The upcoming 2025 Open Accelerated Computing Summit (OACS) aims to explore the convergence of AI and HPC in scientific computing and foster knowledge sharing. This year's OACS welcomes talk submissions from a variety of topics, from Using Standard Language Parallelism to Computer Vision Applications. The document also highlights several open hackathons, a call to apply for NVIDIA Academic Grant Program and resources for optimizing scientific applications using OpenACC directives.
Pragmatic Architecture in .NET
- 1. Pragmatic Architecture in .NET Cory House @housecor | bitnative.com
- 2. The problem.
- 3. X is good It Depends
- 4. Three Simple Goals: 1. Cost vs benefit 2. Contrast extremes 3. Review our options in .NET
- 5. Why? Save money. Save effort. Save time.
- 6. Why Not? To improve my resume’. To challenge myself. To experiment.
- 7. Assumptions 1. Web based 2. RDBMS 3. Enterprise line of business app
- 8. Astronaut Assessment We must use <shiny new technology> for this! Reinvent the wheel 100% test coverage Never ORM Always code to an interface Use all the patterns Resume Driven Development
- 9. Consider Simplicity 1. Do simplest thing that could possibly work 2. Lean / Agile principles 3. YAGNI 4. 80/20 Rule
- 10. Consider Complexity • Unit Testing • Coding to an interface • SOA • Rich Domain Model • Layered N-teir architecture
- 11. Which is better? Tightly Coupled No Tests No Layers No API Coded to Interfaces 100% Test coverage Rich Domain Model Service Oriented
- 12. It depends.
- 13. What if I said… • $250k over budget • Customers hated it, or worse, ignored it • Idea didn’t pan out • Project funding dried up • 1 month late = worthless
- 14. Work expands to fill available time. Parkinson’s Law
- 15. Agile Estimation: Flex one. Quality Date Cost Features* Architecture Reuse Performance Security Testing Scalability Documentation * Fat chance
- 16. Quality is reduced to meet deadlines. Software quality is directly related to deadline sanity. Deadline and manpower are often a constant. Thus, software quality is directly related to deadline sanity. Quality software requires realistic deadlines.
- 17. Q: Is debt bad? Later Now A: Is the deadline hard?
- 18. Hard vs Soft Deadlines Trade show Published advertising X-team dependencies 1st to market or dead Network effects Single loud customer WAG Salesman misspoke MS Project said so
- 19. Perfect architecture? Who cares. Facebook Twitter StackOverflow The problem is getting people to care.
- 20. We’re paid for solutions, not code. Unit Testing – Insurance – Investment in the future (ease of maint) – Potential long-term cost in complexity/manpower
- 21. Enough Theory… Let’s get geeky.
- 22. Presentation Service Domain Data Web Forms vs MVC JavaScript, CSS, jQuery, Knockout, Angular, IoC Web API, WCF, ASMX, ServiceStack or POCOs C#, VB.Net Entity Framework, nHibernate, LLBLGen, Dapper, ADO.Net
- 24. Layers vs Tiers Logical Physical
- 25. Tiers Scalability Security Abstract complexity Minimize dependences Reusable Performance cost Increased complexity
- 26. Layers Separate concerns Aid understanding Abstract complexity Support testing Minimize dependences Standardize Enable reuse Leak More code
- 27. Small app? methods = layers.
- 28. ORM honors DRY 1. Database 2. Class property 3. Select statements 4. Insert statements 5. Update statements 6. Delete statements 7. SQL marshalling code 1. Database 2. Class property 3. .hbm.xml file
- 29. When ORM? Go for it: • DRY = faster development • Speedier changes • RDBMS agnostic • Type safe interface • Avoid writing SQL • SQL Injection protection • Security, performance, ca ching, mapping OOTB Pass: • Lose control over SQL • DBAs lose control • Security concerns • Performance penalty
- 30. SOA Heterogeneous systems Autonomous Reusable Formal Performance hit Risky changes Both sides must test
- 31. Architectural LevelsL1 Simplest thing L2 Somewhere in between L3 Every tool in the shed
- 32. Level 1 Presentation Domain & Persistence Web Forms Active Record Pattern Linq-2-SQL, Subsonic, Castle ActiveRecord
- 34. Active Record Customer Address Purchase Customer Address Purchase DB Tables Classes One instance = One row
- 35. Active Record Simple & obvious Speedy dev and changes Compliments CRUD apps Good for simple domain No OR mismatch Honors YAGNI Rigid: Domain model = DB Leads to God object Low cohesion: Breaks SRP Hard to test Tricky transactions Repository pattern = pain
- 36. Level 3 Presentation Service Domain Persistence ASP.Net MVC, Knockout/Angular Repository Pattern nHibernate, EF POCOs, Dapper DDD with POCOs WCF, ServiceStack
- 37. Domain Model It’s all about the objects.
- 38. Domain Model Customer Address Purchase Customer with list of addresses Purchase DB Tables Classes Note OR Mismatch
- 39. Business Layer Patterns: Domain Model Complex business domain Leverage design patterns Speak business language Abstracts ugly DB schema Large team Reusable Learning curve Time-consuming design Long-term commitment DB mapping overhead
- 40. Level 3 Summary Testable Manage object lifecycle AOP via dynamic proxies Swappable UI or DAL Speaks in business language Leverage design patterns Slower initial dev Larger initial dev cost Learning curve More places to change Senior developers
- 41. Bottom Line: L1 vs L3
- 42. Points to Add a Feature Level 1 1. UI 2. DB 3. Implement BL (in AR class) 4. Regen DAL Level 3 1. UI 2. DB 3. Implement BL in POCO 4. Update/create interface 5. Update IoC bootstrap 6. Update DB mapping 7. Update/Add service call 8. Add/update tests
- 43. Choice by Complexity Level 3 Level 2Level 1 Effort to enhance Application Complexity
- 44. Architectural Levels Level 1 Level 2 Level 3 Centralized Data Access ? Mockable Data Access ? Central Lifetime Management ? Separation of Concerns ? Domain Driven Design ? Unit Testing Friendly ? Concurrent Development ? Service Oriented ? SOLID ? SPA friendly ? Simplest thing/YAGNI
- 45. Architecture Selection MVP Junior team Small team Simple Domain Tight timeline Throwaway No security concerns Little chance for reuse Flagship product Senior Team Large Team Complex domain Flexible timeline Long-term Security matters Other apps could reuse
- 46. Reading
- 47. Bottom Line 1. Consider the simplest thing that could possibly work. 2. Context matters. X isn’t good or bad. 3. Best practices have a benefit and cost.
Editor's Notes
- #4: Unit testingDomain Driven DesignSOAEvery abstraction has a cost. Know what you're getting and giving.
- #8: not games, embedded software)
- #10: http://www.xprogramming.com/Practices/PracSimplest.htmlGet 80 of the benefit from 20% of the features.
- #14: 6 months: Annual trade show, Ad campaign,
- #16: Quality: Features, Scope, Architecture, Reuse, Performance, Security
- #17: Note: Rarely is scope decreased, deadlines moved, or manpower added.
- #18: Often deadlines are arbitrary – you estimate so executives know about when something will be released. Real deadline
- #20: Facebook uses PHPTwitterStackOverflow - used Linq-2-SQL (Active record pattern). Now #85 globallyThe problem is getting people to care
- #26: Peformance Cost: Translation. Often offset by performance tuning, via encapsulation (e.g. caching queries)
- #27: Reusable: HTTP, Telnet, SSH use TCP/IPLeaky: Update all layers to add UI fieldPerformance Cost: Translation. Often offset by performance tuning, via encapsulation (e.g. caching queries)
- #28: Escalate to separate classes and modules as complexity justifies
- #29: On the other hand, you know how it works. You can debug it. It's all right there in your own persistence layer, not buried in the bowels of a 3rd party tool.
- #30: Note under pass - Sprocs can be used to please DBAs, but lose are required by DBAs (mitigates benefits)
- #36: http://www.martinfowler.com/eaaCatalog/activeRecord.htmlhttp://www.mehdi-khalili.com/orm-anti-patterns-part-1-active-record
- #38: Each object owns the logic that is relevant to its piece.
- #40: UseDataMapper pattern to resolve variant relational object schemas
- #44: Insert chart from pg 29Note: Not mutually exclusive. Can use each as needed in diff contexts.
- #47: .Net architecturePOEAADDD