How nullstone-io/deployment-sdk works
Main Components
a. Core SDK Layer:
• Main provider interface and contract components
• Core action interfaces (publish, deploy, monitor, log streaming)
b. Cloud Provider Implementations:
• Create two main branches for AWS and GCP services
• Implementations by service type (Container, Serverless, Static Site, Server)
c. Supporting Services:
• Docker integration layer
• Artifact management
• Logging subsystem
• Metrics/Monitoring system
Relationship Structure
Core SDK Layer
• Provider Interface
• AWS Implementations
• Container Services (ECS, Batch)
• Serverless (Lambda)
• Static Sites (S3)
• Server (Elastic Beanstalk)
• GCP Implementations
• Container Services (GKE)
• Static Sites (GCS)
Component Details
• Interfaces (hexagons)
• Implementations (rectangles)
• Supporting services (rounded rectangles)
• AWS services (orange)
• GCP services (blue)
• Core SDK components (green)
• Supporting services (gray)
Data Flow Representation
Following flows:
• Artifact publication path
• Deployment execution flow
• Log streaming pathway
• Monitoring data flow
Additional Elements
Supporting components:
• Authentication/Credentials management
• Environment variables handling
• Metrics collection and reporting
• Error handling and retry logic
Specific Details
For each implementation, show:
• Input/Output interfaces
• Service-specific components (e.g., ECS Task Definitions, Lambda Functions)
• Monitoring and logging integrations
• Resource management capabilities
Notes
Annotations for:
• Cross-cutting concerns
• Authentication flows
• Error handling strategies
• Retry mechanisms
Remember to emphasize the extensibility points where new providers can be added, as this appears to be a key design consideration based on the file structure.