skills.rest
tadokoro-ryusuke
tadokoro-ryusukeCOMMUNITY
Explore all skills by this author →
GitHub

backend-patterns

Detail backend architecture patterns for API design, repository, service layer, caching with sample TypeScript code.

Updated Dec 1, 2025
Search Tags:#typescript#caching#backend#api-design#service-layer#repository-pattern
One-click install
npx skills add https://github.com/tadokoro-ryusuke/cc-plugins --skill backend-patterns-tadokoro-ryusuke
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: backend-patterns
Source: https://github.com/tadokoro-ryusuke/cc-plugins/tree/main/dev-core/skills/backend-patterns
Command: npx skills add https://github.com/tadokoro-ryusuke/cc-plugins --skill backend-patterns-tadokoro-ryusuke

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Designers and engineers often struggle to design and implement robust backend architectures, facing uncertainty about which patterns to apply in API design, repository usage, service orchestration, and caching.

Core Features & Use Cases

  • API design guidance: RESTful endpoint design, response formats, and error handling.
  • Repository pattern: interface contracts and practical implementations.
  • Service layer orchestration: use-case examples and business logic structuring.
  • Caching strategies: cache-aside and invalidation patterns to optimize performance.
  • End-to-end patterns with sample TypeScript code illustrating typical backend workflows.

Quick Start

Outline common backend patterns for API design, repository, service layer, and caching.

Frequently Asked Questions about backend-patterns

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

FAQPage Schema
What is the repository pattern for backend API design?▼

The repository pattern defines interface contracts and practical implementations to abstract data access, decoupling the service layer from underlying database operations. It establishes a clear boundary for querying and persisting domain entities within a backend architecture.

How do I structure a service layer for RESTful API endpoints?▼

Structure a RESTful service layer by orchestrating use cases and encapsulating business logic separately from API routes. This pattern coordinates domain operations, applies validation rules, and invokes repository interfaces to manage data transactions cleanly.

What's the best way to implement caching strategies in a backend service?▼

The best way to implement backend caching involves applying the cache-aside pattern to optimize performance and establishing strict cache invalidation rules. This strategy ensures data consistency by loading data on demand and proactively updating stale cache entries.

Can I use these backend patterns for TypeScript microservices?▼

Yes, these backend patterns apply directly to TypeScript microservices. The provided sample TypeScript code illustrates typical backend workflows, covering API design conventions, repository interfaces, and service orchestration tailored for scalable RESTful services.

When do I need a service layer in my backend architecture?▼

You need a service layer in your backend architecture when separating business logic from data access and API routing becomes essential. This pattern is crucial for structuring complex use cases, ensuring maintainability, and orchestrating multiple repository interactions effectively.

Related Skills

Explore More Software Engineering Skills→
msichtermanmsichterman

expo-api-routes

Create Expo Router API routes hosted on EAS Hosting with TypeScript and HTTP methods.

Community
Advanced
sameer-thakkarsameer-thakkar

cache-ops

Generate bottom-up cache invalidation commands across five cache layers.

Community
Advanced
ChurchCRMChurchCRM
933

churchcrm

Plan and implement ChurchCRM development using Slim 4, Perpl ORM, and Bootstrap 5/Tabler patterns.

Official
Advanced
fsollafsolla

domain-driven-design

Models software systems using bounded contexts, aggregates, and ubiquitous language to align code with business domains.

Community
Advanced