'microservices' 검색 결과

Build and debug Java applications with Spring Boot 3.x. This skill guides application design, API implementation, database query tuning, authentication, and testing, including WebFlux applications that process requests without blocking.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Build APIs with Spring Boot
• Improve slow JPA queries
• Configure OAuth2/JWT authentication

Build web application features across the interface, API, and database, with authentication, input checks, and safe data handling. The skill guides technical design, implementation, error handling, and component testing in one workflow.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Building data entry and editing forms with matching APIs
• Adding authenticated profile pages
• Designing data flows from database to interface

Build .NET 8 APIs and backend services using C# 12, with clear separation of application responsibilities. The skill covers database access, authentication, API documentation, compilation checks, and integration tests that verify components working together.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Building endpoints with minimal APIs
• Adding database access with Entity Framework Core
• Separating application responsibilities with MediatR

Build Node.js, Express, and TypeScript APIs with consistent structure. Separate request handling, business logic, and database access, while following guidance for input validation, error tracking, configuration, and tests when adding features or refactoring existing services.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Adding an API endpoint
• Separating business logic from database access
• Standardizing input validation and error handling

Create an evidence-based plan for modernizing an existing system. Analyze code and dependencies, research technology choices, and produce domain-specific migration plans with testing, rollback steps, and a consolidated roadmap for developers to execute.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Planning a gradual replacement of a legacy system
• Comparing service separation and consolidation strategies
• Preparing a language or framework migration

Design and implement a NestJS backend organized into business modules within one deployable application. The skill defines module boundaries, separates data ownership, builds layered code and event communication, and validates isolation through checks and tests.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Designing a new modular NestJS backend
• Implementing business modules with layered responsibilities
• Connecting modules through events

Design a modular monolith, a single application with clear business boundaries. Plan module structure, external service integration, failure handling, and future separation, then produce an HTML architecture document with SVG diagrams.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Design business boundaries for a new backend
• Plan integration that limits dependence on an external vendor
• Define retries and failure handling for external calls

Create a phased roadmap for splitting a monolithic application into separate services. Assess current progress, prioritize work by risk, value, and dependencies, and produce milestones, estimated effort, acceptance criteria, and progress reports.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Planning a migration from a monolith to separate services
• Prioritizing components for extraction
• Defining phase milestones and completion criteria

Turn a large codebase spanning multiple repositories or services into a structured knowledge base. It documents architecture, business rules, and dependencies, links conclusions to source lines, labels confidence in relationships, and supports incremental updates.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Documenting architecture across multiple repositories
• Tracing service dependencies and business rules
• Updating a knowledge base after code changes

Set up one mirrord-up.yaml file to debug several related services locally at the same time. Define each application’s command, Kubernetes target, environment settings, and traffic mode, then manage the sessions together with mirrord up.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Debug an authentication service and dashboard together
• Create an initial multi-service configuration
• Route personal requests using a shared session key

Provides gRPC usage guidelines, protobuf organization, and production-ready patterns for Golang microservices. Use when implementing, reviewing, or debugging gRPC servers/clients, writing proto files, setting up interceptors, handling gRPC errors with status codes, configuring TLS/mTLS, testing with bufconn, or working with streaming RPCs.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Build production-ready systems with stability patterns: circuit breakers, bulkheads, timeouts, and retry logic. Use when the user mentions "production outage", "circuit breaker", "deployment pipeline", "chaos engineering", "retry storm", "health checks", "my service keeps crashing", "prevent cascading failures", or "make it resilient". Also trigger when designing resilient microservices, planning zero-downtime deployments, or capacity-planning for peak load. Covers stability patterns, capacity planning, deploy/release decoupling, and observability. For data systems, see ddia-systems. For system architecture, see system-design.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Design scalable distributed systems using structured approaches for load balancing, caching, database scaling, and message queues. Use when the user mentions "system design", "scale this", "high availability", "rate limiter", "design a URL shortener", "design Twitter", "design Uber", "design a news feed", "system design interview", "capacity planning", or "distributed architecture". Also trigger when estimating infrastructure requirements, choosing between microservices and monoliths, or designing for millions of concurrent users. Covers common system designs (TinyURL, feeds, chat) and back-of-the-envelope estimation. For data fundamentals, see ddia-systems. For resilience, see release-it.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Guided journey from an app idea to a deliberate architecture: boundaries, domain model, data decisions, and resilience, making only the expensive-to-reverse decisions and deferring the rest. Orchestrates eight skills phase by phase - clean-architecture, domain-driven-design, system-design, ddia-systems, software-design-philosophy, release-it, pragmatic-programmer, 37signals-way - asking the user questions at every decision point and recording results in the project docs/ folder (ARCHITECTURE.md, DESIGN-CODE-ARCHITECTURE-PLAN.md) so the journey resumes across sessions. Use when the user wants to design a new app's architecture, choose boundaries and a domain model, decide monolith versus microservices, or says 'how should I structure this app'. If a codebase already exists, use remove-technical-debt (aged), improve-code-quality (fresh prototype), or architecture-optimization (slow but working); if unvalidated, run create-business or create-app first. For one framework in isolation, invoke that skill directly.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Master Java 21+ with modern features like virtual threads, pattern matching, and Spring Boot 3.x. Expert in the latest Java ecosystem including GraalVM, Project Loom, and cloud-native patterns. Use PROACTIVELY for Java development, microservices architecture, or performance optimization.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Build production-ready Node.js backend services with Express/Fastify, implementing middleware patterns, error handling, authentication, database integration, and API design best practices. Use when creating Node.js servers, REST APIs, GraphQL backends, or microservices architectures.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Build high-performance async APIs with FastAPI, SQLAlchemy 2.0, and Pydantic V2. Master microservices, WebSockets, and modern Python async patterns. Use PROACTIVELY for FastAPI development, async optimization, or API architecture.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Master Go 1.21+ with modern patterns, advanced concurrency, performance optimization, and production-ready microservices. Expert in the latest Go ecosystem including generics, workspaces, and cutting-edge frameworks. Use PROACTIVELY for Go development, architecture design, or performance optimization.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Expert backend architect specializing in scalable API design, microservices architecture, and distributed systems. Masters REST/GraphQL/gRPC APIs, event-driven architectures, service mesh patterns, and modern backend frameworks. Handles service boundary definition, inter-service communication, resilience patterns, and observability. Use PROACTIVELY when creating new backend services or APIs.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Master software architect specializing in modern architecture patterns, clean architecture, microservices, event-driven systems, and DDD. Reviews system designs and code changes for architectural integrity, scalability, and maintainability. Use PROACTIVELY for architectural decisions.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Expert cloud architect specializing in AWS/Azure/GCP multi-cloud infrastructure design, advanced IaC (Terraform/OpenTofu/CDK), FinOps cost optimization, and modern architectural patterns. Masters serverless, microservices, security, compliance, and disaster recovery. Use PROACTIVELY for cloud architecture, cost optimization, migration planning, or multi-cloud strategies.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Designs software architecture and selects appropriate patterns for projects. Use when designing systems, choosing architecture patterns, structuring projects, making technical decisions, or when asked about microservices, monoliths, or architectural approaches.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Implement Istio and Linkerd service meshes. Configure mTLS, traffic management, and observability. Use when managing microservices communication.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Backend API design, database architecture, microservices patterns, and test-driven development. Use for designing APIs, database schemas, or backend system architecture.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.