TODO: Add comparison matrix (or other visual representation) describing what types of strategies are relevant for a given problem context. E.g. something like this presentation from JavaZone 2009: Kan vi skape mye mere verdi i softwareprosjekter?
Choose a topic Strategies
Techniqueues
|
Training and communication |
Labels:
None
Page:
Database categories explained
Page:
Persistence in the Web 2.0 - Enterprise 2.0 context
Page:
Resources
Page:
Learning circle
Page:
Laws for Project Architects
Page:
NoSQL alternative to RDBMS - CRUD app
Page:
Scalability - where, what and how to scale
Page:
Domain-Driven Design (DDD)
Page:
Agile and Software Architecture
Page:
Architect roles and responsibilities
Page:
Laws for Organization Architects
Page:
Batch-oriented Architecture
Page:
Architect training guide
Page:
Reporting on duplicated data
Page:
Architectural drivers
Page:
Tre-lags monolitiske web-applikasjoner
Page:
Principles for data collection in a sensor network
Page:
At-least once semantics
Page:
Micro services
1 Comment
comments.show.hideJun 06, 2012
Erik Drolshammer
Really, really good article on CAP/BASE/ACID: http://www.infoq.com/articles/cap-twelve-years-later-how-the-rules-have-changed