Software Architecture

Portal and home for "loose" content related to software architecture.

• A software architect is a part-time Archeologist
• Above all, do no harm
• Aggregate
• Agile and Software Architecture
• Agile architecture - recommended reading
• Anti-agile architecture choices
• Architect categorization
• Architect qualities
• Architect roles and responsibilities
• Architect training guide
• Architectural drivers
• At-least once semantics
• Batch-oriented Architecture
• Bridging the gap between developers and architects
• CASE 1 - why do we might want to do this?
• CASE 2 - why do we might want to do this?
• Clear and consistent responsibility power all great architectures
• Clients of the domain model
• Cloud Home
• Communication channels in a learning organization
• Communication vs Technology focus
• Consistent and balanced decisions
• DDD friendly architectures
• Database categories explained
• Document the software architecture
• Domain Object Types
• Domain Service
• Domain objects having dependencies to services
• Domain-Driven Design (DDD)
• Domain-Driven Design (DDD) in practice
• Entity
• Erik's core dump
• Factory
• Helper code as separate projects
• High reads in the middleware
• Implementing Report functionality with Domain-Driven Design
• Laws for Organization Architects
• Laws for Project Architects
• Learning circle
• Learning organization
• Micro services
• Microservices
• Neo4j deployment alternatives
• NoSQL alternative to RDBMS - CRUD app
• Oracle-killer
• Organizational Architect
• Package structure and layers
• Persistence in the Web 2.0 - Enterprise 2.0 context
• Principles for clear and consistent architecture
• Principles for data collection in a sensor network
• Product Architect
• Project Architect
• Reporting
• Reporting on duplicated data
• Repository
• Resources
• Scalability - where, what and how to scale
• Scalability and HA requirements for distributed systems
• Scaling high computation load wrt. the middleware
• Security requirements for distributed systems
• Separating domain objects from persistence infrastructure
• Software Architecture Knowledge Management Home
• Software Orthogonality
• System architecture
• Tech lead
• The Cost of reuse versus duplication
• The right tools for the job
• Thou shall always revisit the architecture axiom - Clear and consistent responsibilities powers all great architectures
• Thou shalt always be ahead of the project and know the risks and challenges before they arrive
• Thou shalt always revisit the architecture axiom - Clear and consistent responsibilities powers all great architectures
• Thou shalt be hands on
• Thou shalt be kept accountable for all architectural decisions
• Thou shalt lead by example
• Thou shalt make consistent and balanced decisions throughout the project
• Thou shalt never default to silver bullets or magic
• Thou shalt never forget that your day is 80% communication and 20% technology
• Thou shalt never micromanage project decisions
• Thou shalt revisit and evaluate previous decisions
• Thou shalt sit and work together with the team - Thou art an integrated part of the team
• Thou shalt strive to build a learning organization and culture
• Thou shalt strive to create a learning culture
• Thou shalt strive to find and understand your limitations
• Thou shalt support and maintain functional and business data building blocks and communicate these to projects
• Tre-lags monolitiske web-applikasjoner
• Typical micro service technology stack (java)
• Ubiquitous Language
• Use levels to group components according to functionality
• Value Object
• What architects can do to help create a learning organization
• What is software architecture?
• client
• complex data
• high reads
• high writes
• lightweight architecture
• middleware
• scale complex data in the client
• scale complex data in the database layer
• scale complex data in the infrastructure layer
• scale complex data in the middleware layer
• scale complex data in the os & cloud layer
• scale complex data in the server code layer
• scale high processing or high computational in database layer
• scale high processing or high computational in the client
• scale high processing or high computational in the infrastructure layer
• scale high processing or high computational in the os & cloud layer
• scale high processing or high computational in the server code layer
• scale high read in the client
• scale high read in the database layer
• scale high read in the integration layer
• scale high read in the os & cloud layer
• scale high read in the server code layer
• scale high write in the client
• scale high write in the database layer
• scale high write in the infrastructure layer
• scale high write in the middleware layer
• scale high write in the os & cloud layer
• scale high write in the server code layer
• scale large data in the client
• scale large data in the database layer
• scale large data in the infrastructure layer
• scale large data in the middleware layer
• scale large data in the os & cloud layer
• scale large data in the server code layer