tapps-agents 3.6.0__py3-none-any.whl → 3.6.1__py3-none-any.whl

tapps_agents/experts/knowledge/cloud-infrastructure/containerization.md

@@ -1,222 +1,222 @@
-# Containerization Best Practices
-
-## Overview
-
-Containerization packages applications with dependencies into portable, isolated units. This guide covers Docker best practices, multi-stage builds, container patterns, and production considerations.
-
-## Docker Best Practices
-
-### Image Optimization
-
-**Multi-Stage Builds:**
-```dockerfile
-# Stage 1: Build
-FROM node:18-alpine AS builder
-WORKDIR /app
-COPY package*.json ./
-RUN npm ci
-COPY . .
-RUN npm run build
-
-# Stage 2: Production
-FROM node:18-alpine
-WORKDIR /app
-COPY package*.json ./
-RUN npm ci --only=production
-COPY --from=builder /app/dist ./dist
-USER node
-EXPOSE 3000
-CMD ["node", "dist/server.js"]
-```
-
-**Benefits:**
-- Smaller final images
-- No build tools in production
-- Better security (fewer layers)
-
-### Layer Caching
-
-**Order Layers by Change Frequency:**
-```dockerfile
-# Dependencies (change less frequently)
-COPY package.json package-lock.json ./
-RUN npm ci
-
-# Source code (changes frequently)
-COPY . .
-```
-
-**Use .dockerignore:**
-```
-node_modules
-.git
-.env
-*.log
-dist
-```
-
-### Security Best Practices
-
-**Non-Root User:**
-```dockerfile
-FROM node:18-alpine
-RUN addgroup -g 1001 -S nodejs && \
-    adduser -S nodejs -u 1001
-USER nodejs
-```
-
-**Minimal Base Images:**
-- Use `-alpine` variants
-- Avoid unnecessary packages
-- Keep images small
-
-**Scan for Vulnerabilities:**
-```bash
-docker scan myimage:latest
-```
-
-## Container Patterns
-
-### Sidecar Pattern
-
-**Separate Concerns:**
-```yaml
-apiVersion: v1
-kind: Pod
-spec:
-  containers:
-    - name: app
-      image: myapp:latest
-    - name: proxy
-      image: nginx:alpine
-      # Sidecar handles logging, monitoring, etc.
-```
-
-### Init Containers
-
-**Setup Before Main Container:**
-```yaml
-spec:
-  initContainers:
-    - name: init-db
-      image: busybox
-      command: ['sh', '-c', 'until nc -z db 5432; do sleep 1; done']
-  containers:
-    - name: app
-      image: myapp:latest
-```
-
-### Ambassador Pattern
-
-**Proxy Service Calls:**
-- Container proxies requests to external services
-- Handles retries, circuit breaking
-- Simplifies application code
-
-## Production Considerations
-
-### Resource Limits
-
-```yaml
-resources:
-  requests:
-    memory: "256Mi"
-    cpu: "250m"
-  limits:
-    memory: "512Mi"
-    cpu: "500m"
-```
-
-### Health Checks
-
-**Liveness Probe:**
-```yaml
-livenessProbe:
-  httpGet:
-    path: /health/live
-    port: 8080
-  initialDelaySeconds: 30
-  periodSeconds: 10
-```
-
-**Readiness Probe:**
-```yaml
-readinessProbe:
-  httpGet:
-    path: /health/ready
-    port: 8080
-  initialDelaySeconds: 5
-  periodSeconds: 5
-```
-
-### Logging Strategy
-
-**Write to stdout/stderr:**
-- Applications log to stdout
-- Container runtime captures
-- Aggregated by logging infrastructure
-
-### Secret Management
-
-**Use Secrets:**
-```yaml
-env:
-  - name: DB_PASSWORD
-    valueFrom:
-      secretKeyRef:
-        name: db-secret
-        key: password
-```
-
-## Dockerfile-Specific Patterns
-
-### Multi-Stage Build Optimization
-
-**Separate Build and Runtime:**
-```dockerfile
-# Stage 1: Build
-FROM python:3.12-slim AS builder
-WORKDIR /app
-COPY requirements.txt .
-RUN pip install --user --no-cache-dir -r requirements.txt
-
-# Stage 2: Runtime
-FROM python:3.12-slim
-WORKDIR /app
-COPY --from=builder /root/.local /root/.local
-COPY . .
-ENV PATH=/root/.local/bin:$PATH
-CMD ["python", "main.py"]
-```
-
-### Docker Health Check Patterns
-
-**Basic Health Check:**
-```dockerfile
-HEALTHCHECK --interval=30s --timeout=10s --start-period=40s --retries=3 \
-    CMD curl -f http://localhost:8000/health || exit 1
-```
-
-**Python Service Health Check:**
-```dockerfile
-HEALTHCHECK --interval=30s --timeout=10s --start-period=40s --retries=3 \
-    CMD python -c "import requests; requests.get('http://localhost:8000/health')" || exit 1
-```
-
-**See Also:**
-- `dockerfile-patterns.md` - Comprehensive Dockerfile patterns
-- `container-health-checks.md` - Detailed health check patterns
-
-## Best Practices Summary
-
-1. **Use multi-stage builds** for smaller images
-2. **Order layers** by change frequency
-3. **Run as non-root** user
-4. **Set resource limits** to prevent resource exhaustion
-5. **Implement health checks** for reliability
-6. **Use .dockerignore** to reduce build context
-7. **Scan images** for vulnerabilities
-8. **Keep images small** with minimal base images
-9. **Log to stdout** for aggregation
-10. **Use secrets** for sensitive data
-
+# Containerization Best Practices
+
+## Overview
+
+Containerization packages applications with dependencies into portable, isolated units. This guide covers Docker best practices, multi-stage builds, container patterns, and production considerations.
+
+## Docker Best Practices
+
+### Image Optimization
+
+**Multi-Stage Builds:**
+```dockerfile
+# Stage 1: Build
+FROM node:18-alpine AS builder
+WORKDIR /app
+COPY package*.json ./
+RUN npm ci
+COPY . .
+RUN npm run build
+
+# Stage 2: Production
+FROM node:18-alpine
+WORKDIR /app
+COPY package*.json ./
+RUN npm ci --only=production
+COPY --from=builder /app/dist ./dist
+USER node
+EXPOSE 3000
+CMD ["node", "dist/server.js"]
+```
+
+**Benefits:**
+- Smaller final images
+- No build tools in production
+- Better security (fewer layers)
+
+### Layer Caching
+
+**Order Layers by Change Frequency:**
+```dockerfile
+# Dependencies (change less frequently)
+COPY package.json package-lock.json ./
+RUN npm ci
+
+# Source code (changes frequently)
+COPY . .
+```
+
+**Use .dockerignore:**
+```
+node_modules
+.git
+.env
+*.log
+dist
+```
+
+### Security Best Practices
+
+**Non-Root User:**
+```dockerfile
+FROM node:18-alpine
+RUN addgroup -g 1001 -S nodejs && \
+    adduser -S nodejs -u 1001
+USER nodejs
+```
+
+**Minimal Base Images:**
+- Use `-alpine` variants
+- Avoid unnecessary packages
+- Keep images small
+
+**Scan for Vulnerabilities:**
+```bash
+docker scan myimage:latest
+```
+
+## Container Patterns
+
+### Sidecar Pattern
+
+**Separate Concerns:**
+```yaml
+apiVersion: v1
+kind: Pod
+spec:
+  containers:
+    - name: app
+      image: myapp:latest
+    - name: proxy
+      image: nginx:alpine
+      # Sidecar handles logging, monitoring, etc.
+```
+
+### Init Containers
+
+**Setup Before Main Container:**
+```yaml
+spec:
+  initContainers:
+    - name: init-db
+      image: busybox
+      command: ['sh', '-c', 'until nc -z db 5432; do sleep 1; done']
+  containers:
+    - name: app
+      image: myapp:latest
+```
+
+### Ambassador Pattern
+
+**Proxy Service Calls:**
+- Container proxies requests to external services
+- Handles retries, circuit breaking
+- Simplifies application code
+
+## Production Considerations
+
+### Resource Limits
+
+```yaml
+resources:
+  requests:
+    memory: "256Mi"
+    cpu: "250m"
+  limits:
+    memory: "512Mi"
+    cpu: "500m"
+```
+
+### Health Checks
+
+**Liveness Probe:**
+```yaml
+livenessProbe:
+  httpGet:
+    path: /health/live
+    port: 8080
+  initialDelaySeconds: 30
+  periodSeconds: 10
+```
+
+**Readiness Probe:**
+```yaml
+readinessProbe:
+  httpGet:
+    path: /health/ready
+    port: 8080
+  initialDelaySeconds: 5
+  periodSeconds: 5
+```
+
+### Logging Strategy
+
+**Write to stdout/stderr:**
+- Applications log to stdout
+- Container runtime captures
+- Aggregated by logging infrastructure
+
+### Secret Management
+
+**Use Secrets:**
+```yaml
+env:
+  - name: DB_PASSWORD
+    valueFrom:
+      secretKeyRef:
+        name: db-secret
+        key: password
+```
+
+## Dockerfile-Specific Patterns
+
+### Multi-Stage Build Optimization
+
+**Separate Build and Runtime:**
+```dockerfile
+# Stage 1: Build
+FROM python:3.12-slim AS builder
+WORKDIR /app
+COPY requirements.txt .
+RUN pip install --user --no-cache-dir -r requirements.txt
+
+# Stage 2: Runtime
+FROM python:3.12-slim
+WORKDIR /app
+COPY --from=builder /root/.local /root/.local
+COPY . .
+ENV PATH=/root/.local/bin:$PATH
+CMD ["python", "main.py"]
+```
+
+### Docker Health Check Patterns
+
+**Basic Health Check:**
+```dockerfile
+HEALTHCHECK --interval=30s --timeout=10s --start-period=40s --retries=3 \
+    CMD curl -f http://localhost:8000/health || exit 1
+```
+
+**Python Service Health Check:**
+```dockerfile
+HEALTHCHECK --interval=30s --timeout=10s --start-period=40s --retries=3 \
+    CMD python -c "import requests; requests.get('http://localhost:8000/health')" || exit 1
+```
+
+**See Also:**
+- `dockerfile-patterns.md` - Comprehensive Dockerfile patterns
+- `container-health-checks.md` - Detailed health check patterns
+
+## Best Practices Summary
+
+1. **Use multi-stage builds** for smaller images
+2. **Order layers** by change frequency
+3. **Run as non-root** user
+4. **Set resource limits** to prevent resource exhaustion
+5. **Implement health checks** for reliability
+6. **Use .dockerignore** to reduce build context
+7. **Scan images** for vulnerabilities
+8. **Keep images small** with minimal base images
+9. **Log to stdout** for aggregation
+10. **Use secrets** for sensitive data
+

tapps_agents/experts/knowledge/cloud-infrastructure/cost-optimization.md

@@ -1,122 +1,122 @@
-# Cloud Cost Optimization
-
-## Overview
-
-Cloud cost optimization reduces spending while maintaining performance and functionality. This guide covers strategies for rightsizing, reservations, monitoring, and cost allocation.
-
-## Cost Optimization Strategies
-
-### Rightsizing
-
-**Match Resources to Workloads:**
-- Analyze actual usage
-- Downsize over-provisioned resources
-- Upsize under-provisioned resources
-- Use auto-scaling
-
-**Tools:**
-- AWS Cost Explorer
-- Google Cloud Recommender
-- Azure Cost Management
-
-### Reserved Instances
-
-**Commitment Discounts:**
-- 1-3 year commitments
-- Significant discounts (up to 75%)
-- Predictable workloads
-- All Upfront, Partial Upfront, No Upfront
-
-### Spot Instances
-
-**Interruptible Resources:**
-- Up to 90% discount
-- For fault-tolerant workloads
-- Batch processing
-- Auto-scaling groups
-
-### Auto-Scaling
-
-**Match Demand:**
-- Scale up during peaks
-- Scale down during valleys
-- Reduce idle resources
-- Cost-effective scaling
-
-### Serverless
-
-**Pay Per Use:**
-- Only pay for execution time
-- No idle costs
-- Auto-scaling included
-- Event-driven workloads
-
-## Monitoring and Tagging
-
-### Resource Tagging
-
-**Cost Allocation:**
-```json
-{
-  "Environment": "production",
-  "Team": "backend",
-  "Project": "user-service",
-  "CostCenter": "engineering"
-}
-```
-
-### Cost Monitoring
-
-**Track Spending:**
-- Daily, weekly, monthly reports
-- Budget alerts
-- Anomaly detection
-- Department allocation
-
-### Cost Dashboards
-
-**Visualize Spending:**
-- By service
-- By team
-- By environment
-- Trends over time
-
-## Optimization Patterns
-
-### Storage Optimization
-
-**Choose Right Storage:**
-- Hot data: Premium storage
-- Warm data: Standard storage
-- Cold data: Archive storage
-- Delete unused data
-
-### Network Optimization
-
-**Reduce Data Transfer:**
-- Use CDN for static content
-- Minimize cross-region transfer
-- Compress data
-- Cache responses
-
-### Compute Optimization
-
-**Efficient Resource Usage:**
-- Use appropriate instance types
-- Containerize for efficiency
-- Optimize application code
-- Use spot instances for batch
-
-## Best Practices
-
-1. **Tag Resources:** For cost allocation
-2. **Monitor Regularly:** Track spending trends
-3. **Set Budgets:** Alert on overspending
-4. **Review Monthly:** Identify optimization opportunities
-5. **Use Reserved Instances:** For predictable workloads
-6. **Right-size Resources:** Match to actual usage
-7. **Delete Unused:** Clean up orphaned resources
-8. **Use Auto-scaling:** Match demand
-9. **Choose Appropriate Storage:** Tier by access pattern
-10. **Review Pricing Models:** Optimize per workload
-
+# Cloud Cost Optimization
+
+## Overview
+
+Cloud cost optimization reduces spending while maintaining performance and functionality. This guide covers strategies for rightsizing, reservations, monitoring, and cost allocation.
+
+## Cost Optimization Strategies
+
+### Rightsizing
+
+**Match Resources to Workloads:**
+- Analyze actual usage
+- Downsize over-provisioned resources
+- Upsize under-provisioned resources
+- Use auto-scaling
+
+**Tools:**
+- AWS Cost Explorer
+- Google Cloud Recommender
+- Azure Cost Management
+
+### Reserved Instances
+
+**Commitment Discounts:**
+- 1-3 year commitments
+- Significant discounts (up to 75%)
+- Predictable workloads
+- All Upfront, Partial Upfront, No Upfront
+
+### Spot Instances
+
+**Interruptible Resources:**
+- Up to 90% discount
+- For fault-tolerant workloads
+- Batch processing
+- Auto-scaling groups
+
+### Auto-Scaling
+
+**Match Demand:**
+- Scale up during peaks
+- Scale down during valleys
+- Reduce idle resources
+- Cost-effective scaling
+
+### Serverless
+
+**Pay Per Use:**
+- Only pay for execution time
+- No idle costs
+- Auto-scaling included
+- Event-driven workloads
+
+## Monitoring and Tagging
+
+### Resource Tagging
+
+**Cost Allocation:**
+```json
+{
+  "Environment": "production",
+  "Team": "backend",
+  "Project": "user-service",
+  "CostCenter": "engineering"
+}
+```
+
+### Cost Monitoring
+
+**Track Spending:**
+- Daily, weekly, monthly reports
+- Budget alerts
+- Anomaly detection
+- Department allocation
+
+### Cost Dashboards
+
+**Visualize Spending:**
+- By service
+- By team
+- By environment
+- Trends over time
+
+## Optimization Patterns
+
+### Storage Optimization
+
+**Choose Right Storage:**
+- Hot data: Premium storage
+- Warm data: Standard storage
+- Cold data: Archive storage
+- Delete unused data
+
+### Network Optimization
+
+**Reduce Data Transfer:**
+- Use CDN for static content
+- Minimize cross-region transfer
+- Compress data
+- Cache responses
+
+### Compute Optimization
+
+**Efficient Resource Usage:**
+- Use appropriate instance types
+- Containerize for efficiency
+- Optimize application code
+- Use spot instances for batch
+
+## Best Practices
+
+1. **Tag Resources:** For cost allocation
+2. **Monitor Regularly:** Track spending trends
+3. **Set Budgets:** Alert on overspending
+4. **Review Monthly:** Identify optimization opportunities
+5. **Use Reserved Instances:** For predictable workloads
+6. **Right-size Resources:** Match to actual usage
+7. **Delete Unused:** Clean up orphaned resources
+8. **Use Auto-scaling:** Match demand
+9. **Choose Appropriate Storage:** Tier by access pattern
+10. **Review Pricing Models:** Optimize per workload
+