A Albumi

Roles / Solution Architect

Solution Architect

Core Scenario

Designing New Integrations

Need to integrate CRM with ERP? Check existing patterns, find the right middleware, and document your design — all in one place.

  • Find existing integrations with similar systems for pattern reuse
  • Check which system is the System of Record for data objects
  • Select middleware based on existing usage and team expertise
  • Document the new integration with full technical details
Result: "Event-driven integration via Kafka documented. Data objects: Customer, Order. SLA requirements defined. Ready for implementation."
Integration Detail
Technology Choice

Middleware Selection

Event-driven architecture needed? See which middleware is already standard, how many teams use it, and avoid introducing unnecessary complexity.

  • Browse IT components by category (middleware, databases, etc.)
  • See usage count — how many integrations use each option
  • Check status: standard, emerging, or deprecated
  • Find teams with existing expertise
Recommendation: "Use Kafka (23 integrations, 'standard' status, 3 teams with expertise) instead of RabbitMQ (deprecated)."
IT Components
Efficiency

Reusing Existing Integrations

Before building from scratch, check if someone already solved the same problem. Subscribe to existing data streams instead of creating duplicates.

  • Find all outbound integrations from source system
  • Check data objects being transferred
  • Contact integration owner for access
  • Subscribe to existing Kafka topic instead of new integration
Discovery: "Found SAP→DWH integration with needed data. Solution: subscribe to existing Kafka topic. Saved 2 weeks of development."
Integrations
Architecture Design

Data Flow Design

New microservice needs master data and must emit events. Design the complete data flow based on existing data landscape.

  • Identify required data objects and their Systems of Record
  • Find existing integrations from SoR systems
  • Identify consumers for your service's events
  • Create complete data flow diagram
Data Flow: "Customer from CRM (API), Product from PIM (event), Order events → Kafka → [Billing, Warehouse, Analytics]"
Data Lineage
Governance

Technology Stack Compliance

Before ARB review, validate that your technology choices align with corporate standards. No surprises at the architecture committee.

  • Check each planned technology against the corporate radar
  • Verify status: standard, emerging (needs approval), or deprecated
  • Find recommended alternatives for deprecated technologies
  • Generate compliance report for ARB
Compliance Check: "8/10 technologies compliant, 1 emerging (requires approval), 1 deprecated (alternative suggested)."
Applications

Works Closely With

EA

Enterprise Architect

  • Standards compliance
  • Pattern governance
  • Impact analysis
Learn more
ID

Integration Developer

  • Implementation handoff
  • Technical specs
  • Troubleshooting
Learn more
AO

Application Owner

  • System roadmap
  • API contracts
  • Dependencies
Learn more

See Albumi in Action for Solution Architects

Get a demo showing how to design solutions faster with full visibility into existing patterns and integrations.

Get Early Access