Components

A Component is the basic building block of a Biztraak project.
Each component represents a service in your application, whether it’s a frontend, backend, database, or integration, and comes with its own Git repo, pipeline, and lifecycle.

What is a Component?

A component in Biztraak includes:

• Source: linked Git repo or pre-built image
• Infrastructure: provisioned through infrastructure workflows (compute, storage, networking)
• Lifecycle: build reviews, deployments, logs, scaling rules
• Governance context: supported activity can be associated with audit records, secrets, IAM, monitoring, and governance workflows

Every component lives inside a project, but has enough isolation to be developed, tested, and deployed independently.

Types of Components

• Frontend: Angular, React, Vue, static sites
• Backend / API: .NET, Node.js, Python, Go, Java
• Virtual Machines: full-machine runtimes with provider-backed VM operations
• VM-hosted Workloads: application components that run inside a selected virtual machine
• Database: Postgres, MySQL, MariaDB, MongoDB
• Cache & Queue: Redis, RabbitMQ, Kafka
• Storage: S3-compatible buckets, object stores
• Federated Apps: packaged extensions like CMS, auth, analytics

Component Lifecycle

1. Create Component

   • From a template
   • From an imported repo
   • From a Marketplace app

2. Develop

   • Use Cloud Dev (VS Code/JetBrains in browser)
   • Push changes to the linked Git repo

3. Build Reviews

   • Configured commits or branches can use a live preview environment
   • Available logs, checks, and governance events are recorded

4. Deploy

   • Promote builds through staging or production deployment flows
   • Assign domains, scale services, monitor health

5. Maintain

   • Adjust scaling rules
   • Update secrets/KMS
   • Track compliance reports and audit logs

Features

• Isolated: each component has its own repo, CI/CD, and infra
• Composable: combine multiple components into one project
• Reviewable: supported security and audit context can stay near the component workflow
• Extensible: link federated apps, databases, or third-party APIs
• Customizable: modify infra, repos, or deployment settings

Example

A SaaS project might include:

• Frontend Component: React UI
• Backend Component: Node.js API
• Database Component: Postgres DB
• Federated App: Auth service from the Marketplace

Each has its own repo, pipeline, and deployments, but together, they form one cohesive Biztraak project.

Next steps

• Deployments → see how components are deployed
• Build Reviews → preview changes per branch
• Virtual Machines → understand VM components and VM-hosted workloads
• Federated Apps → extend with integrations

Components are the foundation of your projects, modular, isolated, and ready to be reviewed and deployed through the project’s configured delivery workflows.