<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Enterprise-Scale on CuraDevOps</title><link>https://curadevops.metacog.co.kr/tags/enterprise-scale/</link><description>Recent content in Enterprise-Scale on CuraDevOps</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 23 Sep 2026 15:14:55 +0000</lastBuildDate><atom:link href="https://curadevops.metacog.co.kr/tags/enterprise-scale/index.xml" rel="self" type="application/rss+xml"/><item><title>GitLab enterprise architecture guide: deployment, runners, HA</title><link>https://curadevops.metacog.co.kr/insights/2026-09-23-how-to-design-gitlab-for-enterprise-scale/</link><pubDate>Wed, 23 Sep 2026 15:14:55 +0000</pubDate><guid>https://curadevops.metacog.co.kr/insights/2026-09-23-how-to-design-gitlab-for-enterprise-scale/</guid><description>&lt;ul>
&lt;li>&lt;strong>Platform/SRE — Learn:&lt;/strong> Covers deployment model selection, high availability, DR, and Kubernetes considerations for GitLab at scale — useful design reference for teams evaluating or expanding a GitLab deployment, but no operational change required today.&lt;/li>
&lt;li>&lt;strong>CI/CD — Learn:&lt;/strong> The runner strategy section (workload isolation, operational load, capacity planning) is directly relevant, but the guide contains no new features, deprecations, or pipeline changes to act on.&lt;/li>
&lt;li>&lt;strong>Leader — Learn:&lt;/strong> Outlines the architecture trade-offs (SaaS vs. self-managed, HA tiers) that inform an enterprise GitLab standardization decision, but there is no new strategic fact — pricing, licensing, or vendor change — that requires a decision now.&lt;/li>
&lt;/ul></description></item></channel></rss>