Software & Development Glossary

Application Programming Interface - a way for different software applications to communicate with each other. Like a waiter who takes your order and brings food from the kitchen.

Building applications as small, independent services that work together. Like a restaurant where different stations handle appetizers, main courses, and desserts separately.

Architecture where each request is completely independent with no memory of previous requests. Like a vending machine that doesn't remember who used it before - every transaction is fresh.

Automated coordination and management of multiple cloud services, containers, or workflows to work together efficiently. Like a conductor directing an orchestra where each musician plays their part at the right time.

Software that connects different applications, services, or systems to help them communicate and share data. Like a translator that helps two people speaking different languages understand each other.

AWS Infrastructure as Code service that lets you define your infrastructure using templates. Like having blueprints that can automatically build identical buildings.

AWS managed Git repository service for storing and versioning code. Like a secure digital filing cabinet for your code that tracks every change.

AWS continuous integration and deployment service that automates your software release process. Like a factory assembly line for code that automatically tests and deploys changes.

AWS service that compiles source code, runs tests, and produces software packages. Like having a dedicated worker that takes raw materials and creates finished products.

Representational State Transfer - a set of rules for building web APIs that are simple and scalable. Like having a standardized menu format that all restaurants can use.

JavaScript Object Notation - a lightweight format for storing and transporting data. Like a universal language for computers to exchange information.

eXtensible Markup Language - a markup language for storing and transporting structured data. Like HTML but designed for data instead of web pages.

Azure service for creating workflows that integrate apps, data, and services across organizations. Like having a digital assistant that can connect different software tools and make them work together.

Software design where components communicate through events rather than direct calls. Like a newspaper where different departments react to breaking news independently.

Open-source Infrastructure as Code tool for building, changing, and versioning infrastructure. Like having blueprints and construction management for cloud resources.

Automation platform for configuration management, application deployment, and task automation. Like having a universal remote control for managing all your servers.

Open-source automation server for continuous integration and deployment. Like having a dedicated quality control manager who automatically tests and delivers your products.

Testing how well a system performs under expected user load. Like seeing how many people can fit in an elevator before it becomes uncomfortable.

AWS service for coordinating multiple AWS services into serverless workflows. Like a conductor orchestrating different musicians to play a symphony together.

Azure platform for building and managing microservices and container applications. Like a framework for building complex applications from many small, independent pieces.

Service mesh platform that provides traffic management, security, and observability for microservices. Like having a smart traffic control system for communication between application components.

Cloud Native Computing Foundation - organization that promotes cloud-native technologies and open source projects. Like a governing body that sets standards for modern cloud applications.

Query language and runtime for APIs that allows clients to request specific data. Like having a restaurant where you can order exactly the ingredients you want instead of preset meals.

High-performance Remote Procedure Call framework that can run in any environment. Like having a super-fast telephone system for applications to call functions on other computers.

Service that manages and routes API requests between clients and backend services. Like a receptionist that directs visitors to the right department and handles basic requests.

Method for applications to provide real-time information to other applications via HTTP callbacks. Like having automatic notifications sent when specific events happen.

Software Development Kit - collection of tools, libraries, and documentation for building applications. Like a toolbox with everything needed to build a specific type of project.

Cloud Development Kit - framework for defining cloud infrastructure using familiar programming languages. Like writing cloud infrastructure using the same code you use for applications.

Service Level Objective - specific measurable target for service performance. Like setting a goal to answer customer calls within 30 seconds, 95% of the time.

AWS service for monitoring and evaluating AWS resource configurations. Like having an audit system that tracks all changes to your cloud infrastructure.

AWS service for managing and configuring Amazon EC2 instances and on-premises servers. Like having a universal remote control for all your servers.

Yet Another Markup Language - human-readable data serialization standard. Like a simple format for writing configuration files that both humans and computers can easily understand.

Create, Read, Update, Delete - the four basic operations for managing data in databases. Like the essential actions you can perform on any information: add, view, change, and remove.

Design pattern that prevents cascading failures by stopping calls to failing services. Like having electrical breakers that shut off power to prevent house fires.

Design pattern that isolates critical resources to prevent total system failure. Like having watertight compartments on a ship so one leak doesn't sink the entire vessel.

Design pattern for managing distributed transactions across multiple services. Like coordinating a complex group project where different people handle different parts.

Software development methodology emphasizing flexibility, collaboration, and rapid iteration. Like building something by making small improvements based on regular feedback.

Agile framework for managing software development with defined roles, events, and artifacts. Like having a structured game plan with specific positions and plays for team coordination.

Visual workflow management method for tracking work progress. Like having a board with columns showing what needs to be done, what's in progress, and what's completed.

Infrastructure layer that manages service-to-service communication in microservices architectures. Like having a smart postal system specifically designed for application communication.

Design pattern where helper components are deployed alongside main applications. Like having a personal assistant that helps with specific tasks while you focus on your main work.

Design pattern using proxy services to handle external communications. Like having diplomats who handle all international communications on behalf of your organization.

Integrated Development Environment - software application providing comprehensive facilities for software development. Like having a complete workshop with all tools needed for building applications.

AWS service for centrally managing multiple AWS accounts. Like having a corporate headquarters that manages all branch offices with consistent policies.

AWS service for setting up and governing secure, multi-account AWS environments. Like having an automated system that sets up new offices with all security and compliance measures in place.

Google Cloud service for developing, deploying, and managing APIs. Like having a professional receptionist service that handles all API requests and manages access.

Deployment strategy that updates applications without any service interruption. Like renovating a store while keeping it open for customers by working on one section at a time.

Infrastructure approach where servers are never modified after deployment, only replaced. Like using disposable plates instead of washing dishes - throw away and get fresh ones.

Practice of intentionally introducing failures to test system resilience. Like conducting fire drills to ensure everyone knows how to respond to emergencies.

Technique for enabling or disabling application features without deploying new code. Like having light switches for different features that can be turned on or off remotely.

Cost of additional rework caused by choosing quick solutions instead of better approaches. Like taking shortcuts when building a house that require expensive fixes later.

Pattern of storing all changes to application state as a sequence of events. Like keeping a detailed diary of everything that happened instead of just the current situation.

Command Query Responsibility Segregation - pattern that separates read and write operations for data stores. Like having separate express lanes for deposits and withdrawals at a bank.

Software development approach that focuses on modeling software to match business domains. Like designing software to mirror how the actual business operates.

Recovery Time Objective - maximum acceptable time to restore service after a failure. Like setting a goal to reopen a store within 2 hours after any emergency closure.

Recovery Point Objective - maximum acceptable amount of data loss measured in time. Like deciding you can afford to lose at most 1 hour of work if your computer crashes.

Mean Time To Recovery - average time needed to restore service after a failure. Like measuring how long it typically takes to fix different types of problems.

Mean Time Between Failures - average time between system failures. Like measuring how long equipment typically works before needing repairs.

Plans and processes to restore technology systems after catastrophic events like fires, floods, or cyberattacks. Like having an emergency evacuation plan for your digital business.

Strategy for keeping critical business operations running during and after disasters or disruptions. Like having backup plans to keep your store open even during emergencies.

Regularly practicing disaster recovery procedures to ensure they work when needed. Like fire drills that prepare you for real emergencies.

GitOps continuous delivery tool for Kubernetes supporting multi-cluster deployments. Like having an automated deployment system that keeps your applications synchronized across multiple environments.

A collection of web pages accessible via the internet that contains information, images, videos, or other content. Like a digital brochure or magazine that anyone can visit.

Software application that lets you access and view websites on the internet. Like a window that shows you different websites when you type in their addresses.

The main software that manages your computer and runs other programs. Like the manager of a building who makes sure everything works properly.

Computer programs and applications that tell hardware what to do. Like instructions or recipes that make computers perform specific tasks.

A software program designed for end users to accomplish specific tasks. Like specialized tools - a calculator app for math, a camera app for photos.

An application specifically designed to run on smartphones and tablets. Like pocket-sized tools that you can use anywhere.

The visual elements (buttons, menus, screens) that let you interact with software. Like the dashboard and controls in a car that help you drive.

A website that helps you find information on the internet by typing keywords. Like a librarian who can instantly find any book or information you need.

Specific words or phrases you type into search engines to find information. Like asking for directions by naming the specific place you want to go.

Software that updates itself without you having to manually install new versions. Like having a car that automatically gets the latest safety features overnight.

Development and Operations combined - practices that unify software development and IT operations for faster, more reliable releases. Like having builders and maintenance crews work together instead of separately.

Continuous Integration/Continuous Deployment - automated process for testing and deploying code changes quickly and safely. Like an assembly line that automatically tests and ships products.

Deployment strategy using two identical environments where you switch traffic from old version to new version instantly. Like having two identical stages where you prepare the new show while the old one is running.

Gradual deployment strategy that releases changes to a small subset of users first before rolling out to everyone. Like testing a new recipe on a few customers before adding it to the full menu.

Deployment approach where infrastructure and application changes are managed through Git version control. Like using a blueprint repository where every change is tracked and can be reversed.

Service Level Agreement - a commitment between service provider and customer defining expected performance and reliability. Like a warranty that promises your service will work 99.9% of the time or you get compensation.

Site Reliability Engineering - approach that applies software engineering principles to infrastructure and operations. Like having software developers who specialize in making systems reliable and scalable.