Microservices segmentation by type classifies the architectural patterns and runtime models that underpin service delivery. The API‑gateway model, representing roughly 30 % of deployments, centralizes request routing, authentication, and rate‑limiting, thereby reducing downstream complexity and enabling unified security policies. Service‑mesh implementations account for about 20 % and provide intra‑service communication, observability, and traffic‑management capabilities through a lightweight sidecar proxy, crucial for large‑scale, polyglot environments. Function‑as‑a‑Service (FaaS) or serverless functions contribute near 15 % as organizations offload event‑driven workloads to managed runtimes, achieving pay‑per‑use cost efficiency. Container‑based microservices, which dominate with an estimated 25 % share, rely on Docker or OCI containers orchestrated by Kubernetes, delivering consistent packaging and rapid scaling across clouds. Event‑driven architectures, comprising roughly 5 %, decouple producers and consumers via message brokers, supporting real‑time analytics and asynchronous processing. The remaining 5 % includes hybrid and bespoke frameworks that blend multiple patterns. Each type adds distinct value propositions—operational agility, resource optimization, or resilience—that collectively expand the total microservices market, as enterprises select the model aligning with their technical debt and business objectives.