Mesoform's Technical Glossary

Numeric & Special Characters

• 429 "Too Many Requests" Error: A status code indicating that a user or client has sent too many requests to a server in a short timeframe, exceeding the rate limit to prevent abuse or overloading.
  
• 500 Internal Server Error: A generic server response code indicating that the server encountered an unexpected condition that prevented it from fulfilling the request.

A

• Accounting Reconciliation Service: A system or process that checks and compares financial records to ensure transactions, balances, and reports match accurately, catching errors or missing entries.

• ACID Compliance (Atomicity, Consistency, Isolation, Durability): A set of properties that guarantee database transactions are processed reliably, essential for financial and high-integrity systems.

• Advisory Notifications: A Google Cloud console communication service that delivers targeted, compliant security and privacy alerts, allowing teams to investigate and take action on critical events.

• Agile Software Development: An iterative approach to software delivery that builds applications incrementally, allowing teams to adapt to changing requirements quickly.

• API (Application Programming Interface): A set of protocols and definitions that allow different software applications to communicate and share functionality without needing to know how each is internally implemented.

• API Gateway: A server that acts as a single entry point for clients to access backend services, managing request routing, authentication, rate limiting, and traffic monitoring.

• API Rate Limiting: A control mechanism used by server interfaces to cap the number of requests a client can submit within a specified time window to prevent server strain or misuse.

• Artefact Registry: A managed service that stores, versions, and secures deployable software components, such as container images and packages, across CI/CD workflows.

• Asynchronous Processing: A design pattern where tasks are executed independently from the main execution thread, allowing systems to remain responsive without waiting for operations to finish.

• Auto-scaling: A cloud infrastructure capability that automatically adjusts the volume of compute resources up or down based on real-time application traffic demands.

B

• Back-end API: A programming interface designed for developers to interact directly with server-side infrastructure, databases, and application business logic.

• Base Asset & Quote Asset: In trading pairs, the base asset is what is being acquired (e.g., Bitcoin), while the quote asset is the currency used to pay for it (e.g., USDC or USD).

• BDD (Behaviour-Driven Development): A software development methodology focusing on business outcomes using plain language (Given/When/Then format) to align product, engineering, and QA teams on system requirements.

• BigQuery: Google Cloud’s fully managed, serverless data warehouse designed to analyse and query petabytes of structured and semi-structured data using SQL.

• Bitstamp: A Luxembourg-based, centralised cryptocurrency exchange (CEX) founded in 2011, providing fiat-to-crypto trading capabilities via web, mobile, and APIs.

• Blue-Green Deployment: A release strategy that utilises two identical environments (Blue for live, Green for new) to ensure zero-downtime updates and immediate rollback capabilities.

• BNB Smart Chain: A blockchain network within the Binance ecosystem optimised for running smart applications with lower fees and faster confirmation times than traditional blockchains.

• Bounty Programme (Bug Bounty): An initiative offered by organisations that rewards external security researchers for discovering and reporting vulnerabilities in their platforms.

• Broker API: An interface that provides traders and platforms access to real-time market updates, executing automated trading orders programmatically.

• Build Process: The automated steps taken to compile source code, dependencies, and configuration files into executable software components.

C

• Canary Deployment: A deployment strategy where a new software version is rolled out to a small subset of users first to test stability before distributing it to the entire infrastructure.

• Certificates: Digital files that verify the identity of a website, server, or client, enabling encrypted, tamper-proof communications over the internet.

• Chaos Engineering: The practice of deliberately introducing controlled failures into a system to test its resilience, stability, and automated recovery mechanisms.

• CI/CD Pipeline: Continuous Integration / Continuous Deployment. An automated system that builds code, runs automated tests, and safely deploys application updates to live environments with minimal human intervention.

• Cloud Armor: A Google Cloud security service offering enterprise-grade DDoS mitigation and Web Application Firewall (WAF) capabilities for Layer 3, 4, and 7 defences.

• Cloud NAT (Network Address Translation): A service that enables cloud resources lacking public IP addresses to securely make outbound connections to the internet without exposing themselves to inbound traffic.

• CloudSQL: Google Cloud’s fully managed relational database service for MySQL, PostgreSQL, and SQL Server, handling backups, replication, and patching automatically.

• Cloudspace: An isolated virtual environment (also called a Virtual Private Cloud) hosted on cloud infrastructure to manage computing, storage, and networking securely.

• Cold Wallet: An offline cryptocurrency wallet used to store private keys away from internet access, mitigating the risk of online hacking.

• Composite Module: A software module or application architecture created by combining multiple distinct components into a cohesive system.

• Containerisation: Packaging an application along with its dependencies, libraries, and configurations into a single standardised unit (e.g., Docker container) to run consistently across environments.

• Cross-Site Scripting (XSS): A web security vulnerability where malicious scripts are injected into trusted websites, allowing attackers to compromise user sessions or steal data.

• Cryptographic Hash: A mathematical algorithm that maps arbitrary data to a fixed-size bit string, used to verify data integrity and secure blockchain blocks.

• CSV (Comma-Separated Values): A simple text file format used to store tabular data where values are divided by commas.

D

• Dark Launching: Releasing new software features to a small, hidden subset of users in production to test performance and stability before a full roll-out.

• Data Loss Prevention (DLP): Policies, tools, and strategies designed to detect, monitor, and prevent sensitive data (like PII or secret keys) from being accidentally exposed or exfiltrated.

• Data Studio (Looker Studio): A business intelligence and data visualisation tool by Google that transforms raw data into customisable, interactive dashboards.

• Database Credentials: Authentication data (usernames, passwords, or tokens) used by systems or users to gain authorised access to a database.

• Database Error (DB Error): An issue where the host application or server fails to connect to, write to, or read from its backend database.

• Database Resilience: The architectural capability of a database system to continue operating, self-heal, or recover rapidly when unexpected hardware, network, or software failures occur.

• Decentralised Finance (DeFi): Financial applications built on blockchain technology that enable peer-to-peer trading, lending, and borrowing without traditional intermediaries.

• Deployment: The process of packaging, releasing, and running an application on a target compute platform (e.g., test server, staging, or production).

• Development Environment: An isolated setup where software engineers write, modify, and conduct initial testing on new code before sharing it.

• Distributed Denial of Service (DDoS): A cyberattack that floods a target network, application, or server with malicious traffic to overwhelm resources and cause service disruption.

• DNS Zone: A specific administrative portion of the global Domain Name System namespace managed by a single organisation.

• Dry Run: An execution step that simulates a command, script, or infrastructure deployment without applying permanent changes to verify system behaviour.

• Dynamic Application Security Testing (DAST): Security testing executed while an application is running to identify vulnerabilities that could be exploited in a live environment.

E

• E2E (End-to-End) Testing: A testing methodology that validates an entire application workflow from start to finish, including backend components, interfaces, network, and database connections, simulating real user interactions.

• Edge Computing: A distributed computing paradigm that brings application processing and data storage closer to the physical location of the user to reduce latency.

• Encrypted Data: Information that has been converted into ciphertext using cryptography, rendering it unreadable without the corresponding decryption key.

• Ethereum: A decentralised, open-source blockchain network featuring smart contract functionality, powered by its native asset, Ether (ETH).

• Event-Driven Architecture: A software design pattern where decoupled services communicate by capturing, publishing, and consuming real-time state changes (events).

F

• Feature Flags (Feature Toggles): A software engineering technique that enables developers to turn specific application features on or off remotely without redeploying code.

• FIDO Passkeys: A passwordless authentication standard using public-key cryptography and device biometrics or PINs to replace weak passwords and defend against phishing.

• Fiat Gateway: A service or platform that allows users to convert traditional government-issued currencies (e.g., GBP, EUR, USD) into digital crypto assets, and vice versa.

• Firebase App Check: An app attestation security layer that blocks unauthorised clients, scrapers, and modified software from accessing backend services and APIs.

• Folders: Hierarchical grouping structures within cloud platforms used to logically organise software projects, access rights, and policies.

• Function: A self-contained block of code designed to execute a specific task, often taking inputs and returning an output.

G

• Gas Fee: The operational transaction fee paid on blockchain networks (such as Ethereum) to reward miners or validators for computing power spent executing transactions.

• GitOps: A modern operational methodology that uses Git repositories as the single source of truth for declaratively defining infrastructure and application state.

• Google Service Accounts (GSAs): Non-human accounts used by applications and automation workloads to authenticate and access Google Cloud resources securely using assigned roles.

• Graceful Degradation: The ability of a software system to maintain limited operational capabilities even when parts of its infrastructure or features fail.

H

• Hard Fork: A non-backward-compatible upgrade to a blockchain protocol requiring all nodes to update, effectively splitting the blockchain into two separate networks if unaligned.

• Health Check: An automated endpoint ping used by load balancers and orchestrators to determine whether an application instance is healthy and capable of serving traffic.

• Hot Wallet: A cryptocurrency wallet connected to the internet, offering quick access for trading and transactions at the cost of higher exposure to online threats.

• HTTPS Load Balancer: A proxy-based Layer 7 system that distributes incoming encrypted web traffic across multiple backend targets to ensure high availability and scalability.

I

• Idempotency: A system design property where executing an API request or operation multiple times yields the exact same result as executing it once.

• Identity Aware Proxy (IAP): A security control that verifies user identity and context before granting access to web applications and cloud resources without requiring a traditional VPN.

• Identity Provider (IdP): A system that creates, maintains, and manages identity information for principals while providing authentication services to applications.

• Identity and Access Management (IAM): A security framework of policies and tools ensuring that authenticated entities (users or applications) have the exact permissions required to access targeted resources.

• Immutable Infrastructure: An operational approach where servers or environment components are never modified once deployed; updates are applied by replacing old instances with new ones.

• In-App Localisation: Adapting an application's design, text, dates, currencies, and behaviour to fit the cultural and linguistic norms of specific target geographic regions.

• Infrastructure as Code (IaC): Managing and provisioning compute, storage, and networking infrastructure using machine-readable configuration files rather than manual user interface operations.

• Integration Environment: A shared test bed where modular code changes from multiple engineering teams are combined and validated for system compatibility.

• Internal Developer Platform (IDP): An ecosystem of tools, infrastructure, and workflows maintained by a platform engineering team to provide self-service "golden paths" for developers.

K

• Keap: A cloud-based customer relationship management (CRM) and sales/marketing automation suite designed primarily for small businesses.

• Know Your Customer (KYC): Mandatory identity validation procedures financial institutions and crypto exchanges perform to confirm user legitimacy and counter fraud.

• Know Your Transaction (KYT): Real-time compliance monitoring that analyses cryptocurrency transactions to detect suspicious patterns, money laundering, or sanctions breaches.

• Kubelet: An agent that runs on each node in a Kubernetes cluster to ensure containers are running inside their assigned pods as intended.

• Kubernetes: An open-source container orchestration platform designed to automate the deployment, scaling, and management of containerised applications.

L

• Latency: The time delay between a client sending an instruction or data packet and the target system receiving and processing it.

• Least Privilege Principle: A foundational security principle stating that users, processes, and service accounts should be granted only the absolute minimum permissions needed to complete their work.

• Limit Order: An instruction given to an exchange to buy or sell a financial asset at a specific price or better, rather than at current market rates.

• Liquidation Event: A corporate scenario where an organisation closes, sells its assets, settles debts, and distributes remaining funds; in crypto margin trading, it refers to the forced closure of a position due to margin shortfall.

• Liquidity Pool: A collection of cryptocurrency tokens locked in a smart contract that facilitates decentralised trading, lending, and automated market-making.

M

• Maintenance Mode: An operational state where new feature development stops, and engineering focus shifts strictly to critical bug fixes, operational upkeep, and security patches.

• Market Capitalisation (MCAP): The total value of an asset, calculated by multiplying its current price per unit by its total circulating supply.

• Market Order: An order executed immediately at the current prevailing market price to ensure rapid completion over price precision.

• Mesh Network (Service Mesh): A dedicated infrastructure layer (like Istio) that manages fast, secure, and observable service-to-service communication across cloud services.

• Microservices: An architectural paradigm that structures an application as a collection of small, loosely coupled, independently deployable services.

• Multi-Factor Authentication (MFA): An electronic authentication method in which a user is granted access to a website or application only after successfully presenting two or more pieces of evidence.

• Mutating Admission Webhook: A Kubernetes feature that intercepts and modifies API requests before objects are saved to storage, enforcing automated configuration standards.

N

• NGINX: An open-source software suite used widely as a web server, reverse proxy, HTTP cache, and load balancer.

• Non-Fungible Token (NFT): A unique digital identifier recorded on a blockchain used to certify ownership and authenticity of distinct digital or physical assets.

O

• Observability: The degree to which a system's internal state can be inferred solely through its external telemetry outputs, specifically metrics, logs, and traces.

• Open-Source Software (OSS): Software released with source code accessible for anyone to inspect, modify, enhance, and distribute freely.

• Order Book: An electronic ledger containing all active, unfulfilled buy and sell orders for a specific financial asset arranged by price level.

• Orchestration: The automated management, coordination, and scheduling of complex computing systems, containerised workloads, and cloud networks.

P

• Peer-to-Peer (P2P): A decentralised communications model in which both parties have equivalent capabilities and either party can initiate a communication session.

• Penetration Testing (Pen Test): A security assessment where authorised professionals simulate real-world cyberattacks against systems to find vulnerabilities.

• Personally Identifiable Information (PII): Any data point that can be used independently or in combination to identify, locate, or trace a specific individual.

• Pipeline: A series of automated computational stages used by DevOps teams to compile, test, validate, and deploy code.

• Portal: A high-traffic gateway website or interface aggregating diverse services, tools, and content in a central location.

• Production Environment: The live environment hosting active applications serving real end-users and handling critical business operations.

• Project: A cloud architecture container used to isolate resources, define security boundaries, and track operating costs.

• Proof of Stake (PoS): A blockchain consensus mechanism where network validators stake their own cryptocurrency tokens to confirm transactions and secure the network.

• Proof of Work (PoW): A cryptographic consensus mechanism where computational power is spent solving complex mathematical puzzles to validate blockchain transactions.

Q

• QA/Test Environment: A specialised infrastructure layer used by quality assurance teams to run functional tests, identify bugs, and verify system behaviour.

R

• Rate Limiter: A defensive system component that restricts the frequency of incoming requests from individual clients to maintain overall service stability.

• Read Replica: A secondary, read-only copy of an active database used to offload analytical and read-heavy queries from the primary read-write database.

• Recovery Point Objective (RPO): The maximum acceptable period of data loss measured in time that a system can sustain during an outage before impacting business viability.

• Recovery Time Objective (RTO): The targeted duration of time within which a business process or system must be restored after a service failure.

• Refactoring: Restructuring existing code without modifying its external capabilities, aiming to improve maintainability, reduce complexity, and improve efficiency.

• Regression Testing: Re-testing software after code changes to confirm that updates have not broken existing functionality.

• Repository (Repo): A central source control storage location housing application source code, infrastructure files, revision histories, and documentation.

• Reverse Proxy: An intermediary server that receives external client requests, forwards them to backend servers, and returns the response, masking the backend architecture.

• Role-Binding: An authorisation mapping that assigns defined role permissions (e.g., read, write, admin) to specific users, groups, or service accounts.

S

• Sandbox Environment: A safe, isolated testing environment enabling engineers to experiment, test third-party integrations, and run unverified code without risking system state.

• Sanitisation: The process of scrubbing and cleaning user inputs to strip out dangerous characters or scripts before processing, protecting against injection attacks.

• Secret Manager: A secure system designed to store, rotate, control, and audit access to sensitive operational credentials, such as API keys, tokens, and passwords.

• Secrets: Sensitive digital keys, authentication strings, passwords, or certificates used by systems to authorise access to protected resources.

• Security Command Centre (SCC): A centralised cloud dashboard for identifying misconfigurations, tracking vulnerabilities, and responding to threats across infrastructure.

• Serverless Computing: A cloud execution model where cloud providers automatically manage server infrastructure provisioning and scaling, charging only for active runtime.

• Shift Left Security: The security practice of integrating security checks, testing, and threat modelling into the early stages of the SDLC rather than near release.

• SIEM (Security Information and Event Management): A centralised security management architecture that aggregates log data and alerts across an organisation to analyse, detect, and respond to incidents.

• Single Sign-On (SSO): An authentication scheme that allows a user to log in with a single ID to any of several related, yet independent, software systems.

• Site Reliability Engineering (SRE): A discipline applying software engineering principles to operations tasks to build highly scalable and reliable software systems.

• SDLC (Software Development Life Cycle): A structured sequence of phases (planning, design, building, testing, deploying, and maintaining) used to deliver high-quality software.

• Software Bill of Materials (SBOM): A formal, structured inventory of all components, libraries, and modules that make up a software package.

• Slippage: The difference between the expected price of a trade order and the actual price at which the order executes, often caused by market volatility or low liquidity.

• Smart Contract: Immutable, self-executing code stored on a blockchain that automatically verifies and enforces contractual conditions without intermediaries.

• Smart Contract Audit: A comprehensive security check of a smart contract's code to discover bugs, vulnerabilities, and security flaws before deployment.

• SQL (Structured Query Language): The standardised domain-specific programming language used to query, manage, and manipulate relational database management systems.

• SSL (Secure Sockets Layer): An older cryptographic protocol (succeeded by TLS) designed to secure communications over a computer network.

• Staging Environment: A pre-production clone of the live system used to perform final release testing, smoke tests, and deployments in conditions mimicking production.

• Staking: The process of locking up digital assets within a blockchain network to support its consensus protocol and earn rewards in return.

• Static Application Security Testing (SAST): A set of automated security tests that analyse source code for vulnerabilities without executing the application.

T

• Technical Debt: The implied future cost of extra development work created by choosing a fast, temporary solution over a better-architected long-term approach.

• Telemetry: Automated remote collection and transmission of system metrics, logs, and trace data used for monitoring and analysis.

• Terraform: An open-source, declarative Infrastructure as Code (IaC) tool created by HashiCorp to provision and manage cloud infrastructure using configuration files.

• TLS (Transport Layer Security): The modern cryptographic protocol used to encrypt network communications, protecting web traffic and sensitive data from tampering and interception.

• Tokenomics: The economic model and structure governing a crypto token's issuance, distribution, supply, utility, and burn mechanisms.

• Tracing (Distributed Tracing): A monitoring method used to track the path of a request as it passes through various microservices across a distributed system.

U

• UAT (User Acceptance Testing): The final software testing stage where target end-users and business stakeholders evaluate the product to confirm it fulfils business requirements.

• UAT Environment: A designated test environment where business stakeholders perform final deployment readiness testing under simulated real-world conditions.

• UI (User Interface): The graphical layout, components, visual elements, and interactive controls through which a human interacts with an application.

• USDC: A fully collateralised digital stablecoin pegged to the value of the US Dollar on a 1:1 basis.

• User Service: The customer service, support frameworks, or specific microservice components designed to handle end-user interactions and accounts.

V

• Validation: The automated process of verifying that incoming data formats, configurations, or inputs meet required business logic and schema constraints.

• VPC (Virtual Private Cloud): An isolated private network running within a public cloud provider, allowing custom IP address control, subnets, and routing table definitions.

• VPC Service Controls (VPC-SC): A Google Cloud security capability that constructs virtual perimeter boundaries around service resources to mitigate unauthorised data exfiltration.

• Vulnerability Scanning: Automated checks run against networks, systems, or application containers to detect known security flaws and misconfigurations.

W

• Web Application Firewall (WAF): A protective filter placed between a web application and the internet to monitor, analyse, and block malicious HTTP traffic.

• Web3: A term describing a decentralised vision of the internet built on blockchain technologies, tokenised economies, and open protocols.

X

• XRP Trade: The act of buying, selling, or swapping XRP tokens across crypto trading platforms or liquidity networks.

Y

• Yield Farming: The practice of staking or lending crypto assets within DeFi protocols to generate high returns or rewards in the form of additional cryptocurrencies.

Z

• Zero Trust Architecture: A cybersecurity model based on the principle "never trust, always verify," enforcing strict identity authentication and authorisation for every request, regardless of whether it originates inside or outside the network perimeter.

Thanks for exploring our technology glossary!

Have feedback or want to learn more about our platform? Get in touch with us today → 

Contact Us

Athena Internal Developer Platform