Skip to main content
Microservice Integration Techniques
Handbook
121 docs tagged with "technique"
View all tags
Adhoc Over Formal Communication
Aggregate Logging and Monitoring Information in a Central Place
Align Architecture with Organizational Structure
Align Synchronicity to Business Flows
Align the Communication Style to the Business Process
API Facade
API Facade per Client Type
API Gateway Facade
API Versioning
Artifact Registry
Auto-Scale Instances Based on Metrics
Automate Anomaly Detection and Alerting
Avoid Default Configuration Values
Avoid Hardcoded Configurations
Avoid LOC Metric for Service Size
Avoid Transactions over Multiple Microservices
Backward Compatible APIs
Blue-Green Deployments
Bounded Retries
Bulkheads
Canary Releases
Centralized SSO
Choreography over Orchestration
CI/CD for Automated Deployment
Circuit Breaker and Fail Fast
Clear Responsibilities for Parts of the Data
Cluster Management by Container Orchestrator
Collabrate On Libraries
Communicate API Changes
Compensations in Workflows
Configuration as Code
Configuration Server
Consumer-Driven Contract Testing
Containers as Portable Deployment Artifacts
CQRS Proxy
Cross-Functional Teams
Data Replication
Data Replication Proxy
Database Clustering and Sharding
Dead Letter Queue
Decentralize Conceptual Models
Decentralize the Service Cut
Degradation of Functionality
Design for Failure
DNS for Routing
Document Microservice Metadata
Domain-Motivated Alternatives
Domain-Motivated Implementation Details
Edge Server Facade
Education Programs
Encrypt Service-to-Service Communication
Enterprise Service Wrapper
Enterprise-wide Standardization
Environment Variables for Configuration
ESB to Decouple From the Legacy System
Establish a Common Vocabulary
Establish Common Cultural Values
Evaluate the Microservice Cut With Prototypes
Experiments
FaaS/Serverless Platform to Abstract Infrastructure
Gradually Replace the Legacy System
Group Services Based on Domain Proximity
Hypermedia to Reduce Coupling
Immutable Deployments
Independent Choice of Communication Technology
Instance Discovery by Message Broker
Internal Integration Proxy
Load Balancing Between Instances
Load Balancing by Message Broker
Local Proximity of Team Members
Microfrontends
Microservice Managed by One Team
Monitor Metrics at Different Levels
No Domain Logic Into the Infrastructure
No Sharing of Domain-Specific Code
Offer Single-Node Deployment
Only Share Context Information Between UIs
Overarching Organizational Framework
Propagate Security Context via Headers
Propagate Security Context via Tokens
Provide Resources as a Service (Cloud)
Proximity to Domain-Knowledge Holders
Proxy Microservice
Push More Responsibility to Microservice Teams
Question Transactions on Domain Level
Reduce Deployment Coordination
Regular Cross-Team Discussions
Resilient Consumers
Responsibility Documentation
Rollbacks
Rolling Updates
Self-Contained Design
Service / API Registry
Service Cut by Data Entities and Consistency Needs
Service Cut by Dataflows
Service Cut by DDD
Service Cut by Functional Proximity
Service Cut by Non-Functional Requirements
Service Cut by Use-Case
Service Instance Discovery
Service Templates
Service-to-Service Authentication
Sidecars / Service Meshes
Standardization
Standardize API Documentation
Standardize Logging, Monitoring, and Tracing
Standardize the Location of Microservice Documentation
Stateless Design
Storage Area Isolation per Microservice
Support by Taskforce Team
Thematic Boards for Decision Making
Timeouts
Token-based Authentication
Treat the Legacy System as Microservice
UI as Part of Each Microservice
UI Suites
Use a Tracing Mechanism
Use APIs to Decouple From Implementation Details
Use Dashboards and Visualizations
Use of Established Patterns
Virtualize the Network