Software Design and Development

Deployment Infrastructure

Deployment infrastructure is everything that must exist for a build to become a running service: compute, network, identity, data stores,

Azure Pipelines is Microsoft’s CI/CD: YAML (or classic UI) that builds, tests, and deploys. Treat the YAML as code in

Deployment principles are the rules that keep a release boring. Tools change; these do not: same artifact, small steps, observable,

Software deployment is moving a specific build into an environment and making it the thing that serves traffic. If you

Architecture improvement is a change to the shape of the system — boundaries, data ownership, runtime topology — not a

A performance issue is a missed latency, throughput, or cost budget — not “the server feels slow.” Start from a

Software metrics are numbers that change how you act. If a dashboard cannot change a decision this week, it is

End-to-end tests drive the system as a user or client would: browser, or real HTTP against a composed environment. They

A code smell is a surface hint that a design may be rotting. It is not a compiler error and

Quality assurance is the system that makes “we meant to” into “we would have caught that.” Testing is a subset.

An ORM maps objects to tables so you can persist a graph without hand-writing every INSERT. EF Core, Hibernate, Django

Brokers have size limits (SQS 256 KiB; Kafka often about 1 MiB via message.max.bytes; RabbitMQ 4 and later defaults to