# reconciliation Published articles for reconciliation. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## B2B Cross-Border Payments: FX, Rails, and Tax DevFeed: [B2B Cross-Border Payments: FX, Rails, and Tax]() Original publisher: [Read original article]() Author: Deepak Jangir Published: 2026-09-16T00:00:00Z Content type: tutorial Language: en Sources: [Dodo Payments Blog]() Topics: [Finance]() Tags: [b2b](), [banking](), [cross-border](), [cross-border-payments](), [fees](), [payments](), [reconciliation](), [saas](), [tax]() ### AI overview This tutorial explains how B2B cross-border payments are affected by foreign-exchange spreads, correspondent-bank fees, settlement paths, compliance screening, payment rails, and jurisdiction-specific tax treatment. It highlights why international receivables can arrive late or short and become difficult to reconcile. ### Source excerpt How B2B cross-border payments actually work: FX spread and settlement timelines, correspondent banking, regional rails, why international transfers fail, and the tax and entity rules that catch sellers out. ## Five AI Questions We're Hearing from Financial Services Leaders DevFeed: [Five AI Questions We're Hearing from Financial Services Leaders]() Original publisher: [Read original article]() Author: Junta Nakai; Erin Butler; Roshni Joshi; Antoine Amend; Jennifer Miller; Andrea DeSosa; Rajaram Suresh; Kim Hatton; Naeem Rehman; Spencer Cook Published: 2026-09-09T18:09:29Z Content type: article Language: en Sources: [Databricks]() Topics: [Artificial Intelligence](), [databricks](), [audit trail](), [tokenization]() Tags: [2026](), [agentic-ai](), [ai](), [audit-trail](), [banking](), [compliance](), [data](), [databricks](), [financial](), [financial-services](), [governance](), [reconciliation](), [regulatory]() ### AI overview The article presents five questions that financial-services leaders are asking about trustworthy AI. It highlights governance, compliance, auditability, governed data, liquidity, reconciliation, tokenized settlement, financial-crime controls, and human oversight, with Databricks describing examples for banking operations. ### Source excerpt Last year at Sibos Frankfurt, the question was whether AI works. This year: can your... ## SCIM directory sync: A deep dive into deprovisioning DevFeed: [SCIM directory sync: A deep dive into deprovisioning]() Original publisher: [Read original article]() Author: WorkOS Published: 2026-09-08T00:00:00Z Content type: article Language: en Sources: [WorkOS Blog]() Topics: [Protocol (disambiguation)](), [Security](), [Parser](), [Entra ID]() Tags: [audit](), [deep-dive](), [filter](), [protocol](), [provisioning](), [reconciliation](), [security]() ### AI overview This deep dive explains how SCIM directory deprovisioning reaches applications, why identity providers commonly deactivate users instead of deleting them, and how provider-specific payloads and missed events can create security risks. It covers normalization, reconciliation, session termination, and inspecting provider requests. ### Source excerpt What actually happens when a user is removed: the event your app receives, the directories that never send one, and how to catch what gets dropped. ## Redesigning Kubernetes Workqueues and Resyncs to Reduce Thundering Herd Effects DevFeed: [Redesigning Kubernetes Workqueues and Resyncs to Reduce Thundering Herd Effects]() Original publisher: [Read original article]() Published: 2026-09-02T00:00:00Z Content type: article Language: en Sources: [Chainguard: Unchained]() Topics: [Kubernetes](), [systems](), [Concurrent Programming](), [Latency](), [Maintainers]() Tags: [architecture](), [concurrent](), [defense-in-depth](), [failover](), [goroutines](), [kubernetes](), [latency](), [maintainers](), [reconciliation](), [thundering-herd]() ### AI overview This article explains how Kubernetes controllers can experience thundering herd effects when restarts, leader failovers, or periodic resyncs cause many keys to enter an in-memory workqueue at once. It describes the queue and informer behavior behind the problem and introduces Chainguard's redesign of workqueues and resyncs to improve reconciliation under these conditions. ### Source excerpt The thundering herd is an architecture problem. See how Chainguard redesigned workqueues and resyncs to keep reconciliation running smoothly. ## How Kubernetes Actually Works DevFeed: [How Kubernetes Actually Works]() Original publisher: [Read original article]() Author: Nikki Siapno Published: 2026-08-21T12:52:09Z Content type: tutorial Language: en Sources: [Level Up Coding System Design Newsletter]() Topics: [Kubernetes](), [Containers](), [Deployment](), [API](), [Replication]() Tags: [api](), [components](), [containers](), [deployment](), [health](), [kubernetes](), [reconciliation](), [replication]() ### AI overview A tutorial explaining Kubernetes as a platform that continuously reconciles desired and actual cluster state. It covers Pods, scheduling, container health monitoring, failure recovery, and the roles of the control plane and worker nodes. ### Source excerpt The mental model that makes Kubernetes click. ## Online index migration and shard scaling in OpenSearch with the AOSC plugin DevFeed: [Online index migration and shard scaling in OpenSearch with the AOSC plugin]() Original publisher: [Read original article]() Author: Arpit Singla Published: 2026-08-18T21:56:28Z Content type: article Language: en Sources: [OpenSearch]() Topics: [Amazon OpenSearch Service](), [migration](), [Open Source](), [Routing (disambiguation)]() Tags: [blog](), [mapping](), [migration](), [open-source](), [opensearch](), [pipeline](), [plugin](), [production](), [reconciliation](), [routing](), [schema](), [technical](), [workflow]() ### AI overview This article introduces Automatic Online Schema Change (AOSC), an open-source OpenSearch plugin for migrating live indexes to pre-created targets with different mappings, settings, shard counts, or document shapes. It backfills existing documents, replays operations made during migration, and switches an alias after a short write block, while documenting its scaling behavior and limitations. ### Source excerpt Learn how the open-source AOSC plugin migrates live OpenSearch indexes--changing mappings, settings, or shard counts--without losing writes or requiring downtime. The post Online index migration and shard scaling in OpenSearch with the AOSC plugin appeared first on OpenSearch. ## Kubernetes Control Plane Internals and Reconciliation DevFeed: [Kubernetes Control Plane Internals and Reconciliation]() Original publisher: [Read original article]() Author: Alexandre Zajac Published: 2026-08-03T15:31:23Z Content type: tutorial Language: en Sources: [Hungry Minds]() Topics: [Kubernetes](), [distributed-systems](), [Containers]() Tags: [container](), [internals](), [kubernetes](), [reconciliation](), [scheduler]() ### AI overview This article explains how Kubernetes manages distributed workloads through its control plane, worker nodes, and reconciliation loop. It covers the API server, etcd, scheduling, kubelet, desired-versus-actual state, and automated recovery. ### Source excerpt PLUS: Ray 2x throughput boost ⚡, take-home interview breakdown 🔬, great work principles 📚 ## How to scale GitOps in the enterprise: From single cluster to fleet management DevFeed: [How to scale GitOps in the enterprise: From single cluster to fleet management]() Original publisher: [Read original article]() Author: Artem Lajko Published: 2026-07-23T05:40:01Z Content type: tutorial Language: en Sources: [Platform Engineering Blog]() Topics: [GitOps](), [Tooling](), [Git](), [YAML](), [flux]() Tags: [complexity](), [config](), [deployment](), [developers](), [git](), [guide](), [helm](), [how-to](), [kubectl](), [learn](), [operational](), [platform](), [reconciliation](), [scale](), [secrets](), [secrets-management](), [workflow](), [workflows]() ### AI overview This guide explains how to scale GitOps from a single cluster to enterprise fleet management across 50 or more clusters. It focuses on architectural patterns, state store strategies, multi-cluster topology, secrets and policy management, configuration sprawl, repository performance, reconciliation delays, and the organizational discipline required for reliable operations. ### Source excerpt Learn how to scale GitOps from 1 to 50+ clusters using advanced state store patterns (OCI, ConfigHub), multi-cluster topology, and enterprise secrets/policy management ## GitOps architecture, patterns and anti-patterns DevFeed: [GitOps architecture, patterns and anti-patterns]() Original publisher: [Read original article]() Author: Artem Lajko Published: 2026-07-23T05:40:01Z Content type: tutorial Language: en Sources: [Platform Engineering Blog]() Topics: [GitOps](), [Architecture & Design](), [Platform Engineering](), [CI/CD](), [Security]() Tags: [gitops](), [patterns](), [reconciliation](), [security]() ### AI overview A guide to designing GitOps for production, covering declarative and versioned configuration, pull-based deployment, continuous reconciliation, multi-cluster operation, and common anti-patterns. ### Source excerpt A platform engineer's guide to production GitOps architecture. Master advanced patterns, multi-cluster strategies, security, and avoid critical anti-patterns for scale ## From intent to enforcement: Lessons from operating Kubernetes controllers at scale DevFeed: [From intent to enforcement: Lessons from operating Kubernetes controllers at scale]() Original publisher: [Read original article]() Author: Sri Saran Balaji Vellore Rajakumar Published: 2026-07-17T12:00:00Z Content type: article Language: en Sources: [Kubernetes Overview, News and Trends | The New Stack]() Topics: [Kubernetes](), [Amazon Elastic Kubernetes Service](), [VPC]() Tags: [amazon-eks](), [aws-marketplace](), [clusters](), [controllers](), [declarative](), [kubernetes](), [networking](), [platform-engineering](), [policy-controller](), [post-contributed](), [reconciliation](), [scale](), [security](), [sponsor-aws-marketplace](), [sponsored-post-contributed](), [vpc]() ### AI overview This article explains lessons from operating Kubernetes controllers at scale in Amazon EKS. It focuses on how the Network Policy Controller and VPC Resource Controller reconcile declared intent with changing cluster state to enforce network traffic and AWS resource access policies. ### Source excerpt Kubernetes controllers are what make the platform's declarative model real. They observe the state, reconcile toward the intent, and keep The post From intent to enforcement: Lessons from operating Kubernetes controllers at scale appeared first on The New Stack. ## Remittance Advice: What It Is, When to Send One, and Free Templates DevFeed: [Remittance Advice: What It Is, When to Send One, and Free Templates]() Original publisher: [Read original article]() Author: Aarthi Poonia Published: 2026-06-07T00:00:00Z Content type: tutorial Language: en Sources: [Dodo Payments Blog]() Topics: [Software as a service](), [Finance]() Tags: [accounting](), [ach](), [b2b](), [bank](), [batch](), [glossary](), [id](), [payment](), [payments](), [reconciliation](), [saas](), [saas-billing](), [saas-finance]() ### AI overview A practical guide to remittance advice for B2B SaaS businesses. It explains what remittance advice is, when to use it for bank-transfer payments, the information it should contain, and how it supports invoice reconciliation. ### Source excerpt Remittance advice explained for SaaS founders. What it is, when buyers and sellers send one, formats, and how modern billing automates the whole flow. ## Metering LLM Token Usage: An Architecture Guide for AI SaaS DevFeed: [Metering LLM Token Usage: An Architecture Guide for AI SaaS]() Original publisher: [Read original article]() Author: Ayush Agarwal Published: 2026-05-17T00:00:00Z Content type: tutorial Language: en Sources: [Dodo Payments Blog]() Topics: [Large Language Model](), [Software as a service](), [Instrumentation](), [telemetry]() Tags: [ai](), [architecture](), [guide](), [instrumentation](), [llm](), [pitfalls](), [queue](), [reconciliation](), [saas](), [token](), [usage-based-billing]() ### AI overview This architecture guide explains how to build a production LLM token-metering pipeline for AI SaaS. It covers instrumentation at the provider-call boundary, queued billing events, hosted aggregation, customer attribution, retry deduplication, partial-failure handling, and reconciliation. ### Source excerpt Build a metering pipeline for LLM token usage that survives retries, supports multiple providers, and feeds clean billing events. Architecture and pitfalls. ## Running Multiple Brands on One Billing Stack: A Holding Company Guide DevFeed: [Running Multiple Brands on One Billing Stack: A Holding Company Guide]() Original publisher: [Read original article]() Author: Ayush Agarwal Published: 2026-05-09T00:00:00Z Content type: tutorial Language: en Sources: [Dodo Payments Blog]() Topics: [Software as a service](), [Transactions]() Tags: [architecture](), [b2b](), [billing](), [customers](), [guide](), [merchant-of-record](), [operations](), [reconciliation](), [saas]() ### AI overview A guide to running multiple brands through one billing stack and verified business. It explains how brands can share legal, compliance, payout, fee, tax, and processor arrangements while maintaining separate customer-facing identities and brand-specific transaction records. ### Source excerpt How holding companies and multi-product SaaS run several brands on one verified business: shared payouts, separate logos and descriptors, and clean transaction filing. ## How the Kubernetes control plane works DevFeed: [How the Kubernetes control plane works]() Original publisher: [Read original article]() Author: LearnKube Published: 2026-04-17T00:00:00Z Content type: tutorial Language: en Sources: [Learnk8s]() Topics: [Kubernetes](), [API](), [Cloud Native Ecosystem]() Tags: [api](), [api-server](), [authentication](), [authorization](), [declarative](), [kubernetes](), [reconciliation](), [scheduler](), [schema]() ### AI overview This tutorial explains how the Kubernetes control plane accepts changes, stores desired state, and keeps a cluster aligned with that state. It introduces the API server, etcd, scheduler, and controller manager, then describes request validation and persistence in etcd. ### Source excerpt A visual map of the Kubernetes control plane with linked deep dives into the API server, scheduler, controller manager, and etcd. ## Payment Reconciliation for SaaS: Automate Your Financial Operations DevFeed: [Payment Reconciliation for SaaS: Automate Your Financial Operations]() Original publisher: [Read original article]() Author: Ayush Agarwal Published: 2026-04-13T00:00:00Z Content type: tutorial Language: en Sources: [Dodo Payments Blog]() Topics: [Software as a service](), [Transactions](), [stripe](), [Finance]() Tags: [accounting](), [chargebacks](), [fees](), [finance](), [financial](), [operations](), [payment](), [reconciliation](), [saas](), [stripe]() ### AI overview A guide to payment reconciliation for SaaS businesses, covering how to match billing records with bank deposits, processor settlements, and accounting records. It explains why high transaction volumes, multiple currencies, fees, refunds, chargebacks, and settlement timing create discrepancies, and how automation can help. ### Source excerpt Learn how to automate payment reconciliation for your SaaS business - matching transactions, handling edge cases, and closing books faster. ## Net Profit Formula for SaaS: From Revenue to Real Earnings DevFeed: [Net Profit Formula for SaaS: From Revenue to Real Earnings]() Original publisher: [Read original article]() Author: Ayush Agarwal Published: 2026-04-11T00:00:00Z Content type: tutorial Language: en Sources: [Dodo Payments Blog]() Topics: [Software as a service](), [Finance](), [cloud-infrastructure]() Tags: [accounting](), [cloud-infrastructure](), [cost](), [payment-fees](), [pricing](), [reconciliation](), [revenue](), [saas](), [saas-finance](), [tax]() ### AI overview This guide explains how SaaS companies calculate net profit by subtracting all expenses from total revenue. It breaks profitability into stages and highlights the effects of cloud costs, acquisition, support, payment failures, taxes, and compliance. ### Source excerpt Understand the net profit formula for SaaS, which costs matter most, and how founders can move from top-line revenue to durable real earnings. ## DriftlessAF: Introducing Chainguard Factory 2.0 DevFeed: [DriftlessAF: Introducing Chainguard Factory 2.0]() Original publisher: [Read original article]() Published: 2026-01-29T00:00:00Z Content type: release Language: en Sources: [Chainguard: Unchained]() Topics: [chainguard](), [Artificial Intelligence](), [Automation](), [Bot](), [Open Source](), [event driven](), [legacy]() Tags: [agentic](), [ai](), [architecture](), [automation](), [bots](), [chainguard](), [chainguard-containers](), [chainguard-factory](), [chainguard-images](), [chainguard-libraries](), [cve](), [driftlessaf](), [event-driven](), [legacy](), [open-source](), [reconciliation](), [safe-source-for-open-source](), [self-healing]() ### AI overview Chainguard announces Chainguard Factory 2.0, powered by the DriftlessAF agentic framework. The system uses AI-driven, self-healing reconciliation to build and maintain more than 2,000 zero-CVE images, and DriftlessAF is being open-sourced. ### Source excerpt Chainguard Factory 2.0, powered by DriftlessAF, brings AI-driven, self-healing reconciliation to build and maintain 2,000+ zero-CVE images -- now open sourced. ## How banks are cutting development time in half while avoiding million-dollar outages with Temporal Cloud DevFeed: [How banks are cutting development time in half while avoiding million-dollar outages with Temporal Cloud]() Original publisher: [Read original article]() Author: Hannah Short Published: 2025-09-09T00:00:00Z Content type: article Language: en Sources: [Temporal Blog]() Topics: [Cloud](), [Development](), [reliability](), [distributed-systems]() Tags: [announcements](), [banking](), [cloud](), [distributed-systems](), [downtime](), [financial-services](), [productivity](), [reconciliation](), [reliability]() ### AI overview A Forrester Total Economic Impact study of Temporal Cloud describes banking organizations replacing homegrown workflow systems, with reported improvements including $14.3 million in preserved revenue over three years and feature delivery in half the time. ### Source excerpt Forrester's TEI study reveals Temporal Cloud delivers $14.3M in preserved revenue and 50% faster feature delivery for banking institutions. ## The Principle of Reconciliation DevFeed: [The Principle of Reconciliation]() Original publisher: [Read original article]() Published: 2025-07-14T00:00:00Z Content type: opinion Language: en Sources: [Chainguard: Unchained]() Topics: [systems](), [Resilience](), [Kubernetes](), [Concurrency]() Tags: [architecture](), [concurrency](), [kubernetes](), [reconciliation](), [resilience](), [retry](), [self-healing](), [software-development](), [state](), [systems]() ### AI overview The article presents reconciliation as a feedback loop that observes actual state, compares it with a desired state, and acts to close the gap. It explains how Kubernetes controllers, workqueues, retries, bounded concurrency, and idempotency support resilient, self-healing systems. ### Source excerpt The priniciple of reconciliation is what makes systems self-healing, adaptable, and robust in the face of change and failure. ## Introducing Codefresh GitOps Cloud - Seamless environment promotions across clusters using your existing Argo CD DevFeed: [Introducing Codefresh GitOps Cloud - Seamless environment promotions across clusters using your existing Argo CD]() Original publisher: [Read original article]() Author: Kostis Kapelonis Published: 2025-03-30T23:48:40Z Content type: release Language: en Sources: [Codefresh]() Topics: [GitOps](), [argo-cd](), [Automation](), [Cloud]() Tags: [argo-cd](), [automation](), [cloud](), [codefresh](), [continuous-deployment](), [gitops](), [kubernetes](), [product-and-tools](), [reconciliation](), [sync]() ### AI overview Codefresh announces GitOps Cloud, an offering for GitOps deployments that supports multi-environment application promotions across clusters using existing Argo CD. The article also explains GitOps concepts and practices, including version-controlled desired state and continuous reconciliation. ### Source excerpt We're excited to announce our new Codefresh GitOps Cloud offering that lets you bring your GitOps deployments to the next level. You get: In this blog post, we'll dive into some of the key features of Codefresh GitOps Cloud. Multi-environment application promotions with Argo CD As more organizations adopt Argo CD, platform engineers need to [...] The post Introducing Codefresh GitOps Cloud - Seamless environment promotions across clusters using your existing Argo CD appeared first on Codefresh. ## Controller-Driven Infrastructure as Code DevFeed: [Controller-Driven Infrastructure as Code]() Original publisher: [Read original article]() Published: 2025-03-19T20:36:25Z Content type: article Language: en Sources: [Brave New Geek]() Topics: [Infrastructure as code](), [Kubernetes](), [consistency](), [Terraform](), [AWS CloudFormation](), [configuration](), [API]() Tags: [cloudformation](), [consistency](), [controllers](), [declarative](), [iac](), [infrastructure](), [infrastructure-as-code](), [koreo](), [kubernetes](), [platform-engineering](), [policy](), [reconciliation](), [resource-orchestration](), [terraform]() ### AI overview The article explains Controller-Driven Infrastructure as Code, applying Kubernetes controllers and the Kubernetes Resource Model to infrastructure management. It contrasts this resource-centric, continuously reconciled approach with the operation-centric models used by Terraform and CloudFormation. ### Source excerpt Harnessing the Kubernetes Resource Model for modern infrastructure management Infrastructure as Code (IaC) revolutionized how we manage infrastructure, enabling developers to define resources declaratively and automate their deployment. However, tools like Terraform and CloudFormation, despite their declarative configuration, rely on an operation-centric model, where resources are created or updated through one-shot commands. The evolution of IaC: From operations to controllers In contrast, Kubernetes introduced a new paradigm with its controller pattern and the Kubernetes Resource Model (KRM). This resource-centric approach to APIs redefines infrastructure management by focusing on desired state rather than discrete operations. Kubernetes controllers continuously monitor resources, ensuring they conform to their declarative configurations by performing actions to move the actual state closer to the desired state, much like a human operator would. This is known as a control loop. ## Scaling Nextdoor's Datastores: Part 5 DevFeed: [Scaling Nextdoor's Datastores: Part 5]() Original publisher: [Read original article]() Author: Slava Markeyev Published: 2025-03-19T15:09:15Z Content type: article Language: en Sources: [Nextdoor]() Topics: [Databases](), [Cache](), [consistency](), [Scalability](), [Usability](), [data]() Tags: [cache](), [cache-invalidation](), [caching-strategies](), [consistency](), [database-consistency](), [database-scalability](), [databases](), [rdbms](), [reconciliation](), [scalability](), [stream](), [usability]() ### AI overview The final installment of Nextdoor's datastore-scaling series explains how cache consistency can fail when a database writer misses its cache update. It presents a Change Data Capture stream and a reconciler that uses database changes to repair cache inconsistencies. ### Source excerpt In this final installment of the Scaling Nextdoor's Datastores blog series, we detail how the Core-Services team at Nextdoor solved cache consistency challenges as part of a holistic approach to improve our database and cache scalability and usability. In Part 4: Keeping the cache consistent, we highlighted a class of consistency issues arising from racing cache writes and introduced an approach for forward cache versioning as a mechanism to avoid inconsistencies. The cache is able to decide which write to persist and which to reject because it is aware of the version of data it currently has. However, this is only a partial solution because it assumes writers will always succeed in communicating with the cache in a timely manner, if at all. Missed Writes Let's consider the scenario where Writers A and B both performed an update to the same row in the database and have not yet updated the cache. Writer A holds Version 1 and Writer B holds Version 2. What happens if Writer B with Value 2 fails to talk with the cache? Writer B fails to write to the cache. In this case the result is that the cache becomes inconsistent and we can't rely on the writers to provide that consistency. A process must exist outside of this interaction to fix-up the cache when Version 2 is written to the database but fails to be written to the cache. Change Data Stream To solve this problem we tap into a common feature provided by most modern databases, a Change Data Capture (CDC) Stream. A CDC Stream is a mechanism to subscribe to row level changes in a database. The change stream contains a row's previous column values along with the new values. Here's a visual example of the change stream when the last_name field gets updated in the database. For visual clarity the changed values have been underlined in red. Reconciler Since the database is the source of truth and the CDC Stream emits all changes, a consumer of this stream can clean up any consistency issues in the cache. In our system we ca ## Designing high-performance financial ledgers with Temporal DevFeed: [Designing high-performance financial ledgers with Temporal]() Original publisher: [Read original article]() Author: Tim Imkin Published: 2025-03-18T00:00:00Z Content type: article Language: en Sources: [Temporal Blog]() Topics: [Architecture & Design](), [Scalability](), [Transactions](), [Resilience](), [integrity]() Tags: [accounting](), [compliance](), [crashes](), [design](), [financial](), [fintech](), [high-performance](), [ledger](), [payment](), [performance](), [reconciliation](), [resilience](), [temporal-concepts]() ### AI overview The article discusses designing high-performance financial ledgers around scalable transaction handling, double-entry bookkeeping, flexible metadata, and resilient workflow coordination. It presents Temporal's durable execution as a way to address failures caused by network issues, service downtime, and process crashes. ### Source excerpt Learn how Temporal's durable execution solves core challenges -- scalability, reconciliation, and compliance -- to create reliable, future-proof ledger systems. ## The Ethernet/802.1 Protocol Stack DevFeed: [The Ethernet/802.1 Protocol Stack]() Original publisher: [Read original article]() Published: 2025-01-22T07:28:00Z Content type: tutorial Language: en Sources: [ipSpace.net blog]() Topics: [Ethernet](), [Protocol (disambiguation)]() Tags: [ethernet](), [gigabit-ethernet](), [lan](), [protocol](), [provisioning](), [reconciliation]() ### AI overview An explanation of the Ethernet and IEEE 802.1 protocol stack, including the MAC and LLC sublayers, physical-layer subdivisions, and the placement of discovery, link aggregation, spanning tree, VLAN, and provisioning protocols. ### Source excerpt The believers in the There Be Four Layers religion think everything below IP is just a blob of stuff dealing with physical things: People steeped in a slightly more nuanced view of the world in which IP is not the centerpiece of the universe might tell you that the blob of stuff we need is two things: Read more ... [Next page]()