enterprise-application-architecture-patterns

Guide enterprise application architecture pattern selection across layered systems.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/kotarosan-dev/02_rd --skill enterprise-application-architecture-patterns
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: enterprise-application-architecture-patterns
Source: https://github.com/kotarosan-dev/02_rd/tree/main/Books/2026/02/20260221_%E3%82%A8%E3%83%B3%E3%82%BF%E3%83%BC%E3%83%97%E3%83%A9%E3%82%A4%E3%82%BA%E3%82%A2%E3%83%97%E3%83%AA%E3%82%B1%E3%83%BC%E3%82%B7%E3%83%A7%E3%83%B3%20%E3%82%A2%E3%83%BC%E3%82%AD%E3%83%86%E3%82%AF%E3%83%81%E3%83%A3%E3%83%91%E3%82%BF%E3%83%BC%E3%83%B3%20%E9%A0%91%E5%BC%B7%E3%81%AA%E3%82%B7%E3%82%B9%E3%83%86%E3%83%A0%E3%82%92%E5%AE%9F%E7%8F%BE%E3%81%99%E3%82%8B%E3%81%9F%E3%82%81%E3%81%AE%E3%83%AC%E3%82%A4%E3%83%A4%E5%8C%96%E3%82%A2%E3%83%97%E3%83%AD%E3%83%BC%E3%83%81
Command: npx skills add https://github.com/kotarosan-dev/02_rd --skill enterprise-application-architecture-patterns

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a concise, actionable catalog of architecture patterns to reduce design ambiguity and repeated mistakes when building or refactoring enterprise applications that handle complex business logic, persistence mapping, and distributed concerns.

Core Features & Use Cases

  • Pattern Catalog: Summarizes key PoEAA patterns such as Transaction Script, Domain Model, Table Module, Active Record, Data Mapper, Unit of Work, Repository, and presentation and distributed patterns.
  • Decision Guidance: Gives practical heuristics for choosing patterns based on domain complexity, mapping divergence, concurrency needs, and scalability requirements.
  • Practical Scenarios: Helps architects decide between Active Record vs Data Mapper for OR mapping, set boundaries for Service Layer, design Unit of Work strategies, and select session and locking approaches for web and distributed systems.

Quick Start

Ask: "Recommend a set of PoEAA patterns and a data-mapping strategy for a complex domain-driven enterprise system that must integrate legacy RDBMS and support high-concurrency web clients."

Frequently Asked Questions about enterprise-application-architecture-patterns

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
When should I use Active Record vs Data Mapper for O/R mapping in enterprise applications?

Choose Active Record vs Data Mapper based on mapping divergence and domain complexity. Active Record suits simpler domain logic with direct database mapping, while Data Mapper separates persistence from domain logic, handling complex O/R structural mapping and high-concurrency scenarios better.

How do I decide between Transaction Script and Domain Model patterns for my business logic?

Decide between Transaction Script and Domain Model based on domain complexity. Transaction Script handles simple procedural business logic efficiently, whereas Domain Model manages complex domain-driven-design rules and behaviors, requiring robust service layer boundaries and Unit of Work strategies.

What is the best way to implement Unit of Work and Identity Map for high-concurrency web clients?

Implement Unit of Work and Identity Map by tracking object state changes and ensuring consistent object retrieval within a session. Select appropriate session state strategies and locking approaches to maintain concurrency and transactional integrity for distributed web clients.

Does this enterprise application architecture guidance help with integrating legacy RDBMS?

Yes, this enterprise application architecture guidance supports legacy RDBMS integration. It provides O/R structural mapping heuristics and data-source mapping patterns to refactor and bridge complex domain logic with existing relational database schemas effectively.

Can I use these PoEAA patterns for setting Service Layer boundaries in a distributed system?

Yes, you can use these PoEAA patterns to set Service Layer boundaries in distributed systems. The guidance covers establishing service interfaces, managing session state, and selecting distributed patterns to handle concurrency and scalability requirements.