IT:AD:Patterns:DualAccessToData

• (UP)

  • IT:AD:Patterns:ACID
  • IT:AD:Patterns:Chunky over Chatty Strategy
  • IT:AD:Patterns:CQRS
  • IT:AD:Patterns
  • IT:AD:Patterns:Adapter
  • IT:AD:Patterns:Adapter
  • IT:AD:Patterns:AntiPatterns
  • IT:AD:Patterns:AntiPatterns:HighCoupling
  • IT:AD:Patterns:AppHost Strategy
  • IT:AD:Patterns:App Settings != Host Settings != User Settings Strategy
  • IT:AD:Patterns:AppSettings Are Dead Strategy
  • IT:AD:Patterns:Builder
  • IT:AD:Patterns:Cache Is King Strategy
  • IT:AD:Patterns:Cache Like Crazy Strategy
  • IT:AD:Patterns:Command Pattern
  • IT:AD:Patterns:Complex is not Complicated Strategy
  • IT:AD:Patterns:Composite Application Strategy
  • IT:AD:Patterns:Contract First Development Strategy
  • IT:AD:Patterns:Controlled Admin Access Strategy
  • IT:AD:Patterns:Convention Over Configuration Strategy
  • IT:AD:Patterns:DDD
  • IT:AD:Patterns:Dependency Injection Strategy
  • IT:AD:Patterns:Dependency Wrapping Strategy
  • IT:AD:Patterns:Designing from the UI will kill your company
  • IT:AD:Patterns:Don't Drop your pants Strategy
  • IT:AD:Patterns:DRY Strategy
  • IT:AD:Patterns:DTO Strategy
  • IT:AD:Patterns:DualAccessToData
  • IT:AD:Patterns:Egg Yolk Strategy
  • IT:AD:Patterns:Enums Mapped to Code Tables Strategy
  • IT:AD:Patterns:Enums Start with Undefined Strategy
  • IT:AD:Patterns:Extension Methods Strategy
  • IT:AD:Patterns:GAWD Classes
  • IT:AD:Patterns:Gift Package Strategy
  • IT:AD:Patterns:Head Last Pattern
  • IT:AD:Patterns:Help is for Failures Strategy
  • IT:AD:Patterns:IdentityMap
  • IT:AD:Patterns:It's all Hierarchical After All
  • IT:AD:Patterns:KISS Strategy
  • IT:AD:Patterns:Less is More Strategy
  • IT:AD:Patterns:Localisable Data Strategy
  • IT:AD:Patterns:Lowest Framework Profile
  • IT:AD:Patterns:Many Assemblies Strategy
  • IT:AD:Patterns:Minimal Dependency Cardinality
  • IT:AD:Patterns:MS Is A Vendor Strategy
  • IT:AD:Patterns:MS Sells VS (not Good Practices) Strategy
  • IT:AD:Patterns:MVC
  • IT:AD:Patterns:MVP
  • IT:AD:Patterns:Namespace As Problem Boundary Strategy
  • IT:AD:Patterns:Naming Strategies
  • IT:AD:Patterns:Objects as Messages (using ExtensionMethods)
  • IT:AD:Patterns:Page Number Isn't A Search Criteria Strategy
  • IT:AD:Patterns:Prototype
  • IT:AD:Patterns:Reference Data Strategy
  • IT:AD:Patterns:Reference Downward Only
  • IT:AD:Patterns:Repository Pattern
  • IT:AD:Patterns:SASS
  • IT:AD:Patterns:Secure the Line Strategy
  • IT:AD:Patterns:Security is an Application concern
  • IT:AD:Patterns:Service Pattern
  • IT:AD:Patterns:Single Page WebSite Strategy
  • IT:AD:Patterns:Single Sign On Strategy
  • IT:AD:Patterns:SOC
  • IT:AD:Patterns:SOLID
  • IT:AD:Patterns:SOLID/DIP
  • IT:AD:Patterns:SOLID/LSP
  • IT:AD:Patterns:SOLID/OCP
  • IT:AD:Patterns:SOLID/SRP
  • IT:AD:Patterns:Specification Pattern
  • IT:AD:Patterns:Tier Strategy
  • IT:AD:Patterns:TripleA's Strategy
  • IT:AD:Patterns:UnitOfWork Pattern
  • IT:AD:Patterns:Vendors Suck Strategy
  • IT:AD:Patterns:Version Your Messages Strategy
  • IT:AD:Patterns:Views are not Screens Strategy
  • IT:AD:Patterns:WIMP
  • public_apis_ain_t_ui_apis_strategy

Most Apps do either:

• Visualize (Querying and Reporting)

  • Do not need up to the second information.
  • Have little to nothing to do with Business Rules.
    • Do have Authorisation, but that is Infrastructure.
  • Do not need to deal with Concurrency updates
    • Only Tracing/Auditing (which won't have this issue)
    • Therefore do not require:
      • Self-Tracking entities / ORM.
      • Transactional Support
  • Therefore other options are:
    • Lighter DAL
    • Potentially even allowing for a second DB: OLAP
      • Although Syncrhonization will have to be addressed.
  • See IT:AD:Patterns:CQRS which can be based on the above.