https://community.esri.com/t5/arcgis-enterprise-questions/service-based-gis-branch-versioning-how-are-you/m-p/1699710#M44123 <P>We’re mid-migration to a more service-based Enterprise GIS and trying to understand how others are handling this transition.</P><P><STRONG>Our current setup:</STRONG></P><UL><LI>300+ layers in an enterprise geodatabase</LI><LI>8-10 editors, and a large number of read-only viewers</LI><LI>Utility Network (water, storm, wastewater) is branch versioned in separate geodatabases</LI><LI>Remaining data is traditional versioned</LI><LI>Attribute rules are in place and currently being validated with an asset management integration</LI><LI>Current workflow still uses geodatabase replication (edit DB + read-only DB)</LI></UL><P>As we move toward Portal/web map–based access and away from direct database connections, we’re running into a mismatch between replication and the newer service-based/branch versioning model.</P><P><STRONG>Questions:</STRONG></P><OL><LI>How are you handling edit vs read-only access? Separate services for each, or view layers/permissions from a single service?</LI><LI>How are you avoiding service duplication for hundreds of layers?</LI><LI>For those using Experience Builder or Instant Apps - Do you build app-specific grouped services, or do you rely on web maps built from services that are published for general use?</LI></OL><P>Would really appreciate hearing what has worked (and what hasn’t).</P><P>Thanks!</P> Sat, 02 May 2026 22:13:52 GMT JuneAcosta 2026-05-02T22:13:52Z https://community.esri.com/t5/arcgis-enterprise-questions/service-based-gis-branch-versioning-how-are-you/m-p/1699710#M44123 <P>We’re mid-migration to a more service-based Enterprise GIS and trying to understand how others are handling this transition.</P><P><STRONG>Our current setup:</STRONG></P><UL><LI>300+ layers in an enterprise geodatabase</LI><LI>8-10 editors, and a large number of read-only viewers</LI><LI>Utility Network (water, storm, wastewater) is branch versioned in separate geodatabases</LI><LI>Remaining data is traditional versioned</LI><LI>Attribute rules are in place and currently being validated with an asset management integration</LI><LI>Current workflow still uses geodatabase replication (edit DB + read-only DB)</LI></UL><P>As we move toward Portal/web map–based access and away from direct database connections, we’re running into a mismatch between replication and the newer service-based/branch versioning model.</P><P><STRONG>Questions:</STRONG></P><OL><LI>How are you handling edit vs read-only access? Separate services for each, or view layers/permissions from a single service?</LI><LI>How are you avoiding service duplication for hundreds of layers?</LI><LI>For those using Experience Builder or Instant Apps - Do you build app-specific grouped services, or do you rely on web maps built from services that are published for general use?</LI></OL><P>Would really appreciate hearing what has worked (and what hasn’t).</P><P>Thanks!</P> Sat, 02 May 2026 22:13:52 GMT https://community.esri.com/t5/arcgis-enterprise-questions/service-based-gis-branch-versioning-how-are-you/m-p/1699710#M44123 JuneAcosta 2026-05-02T22:13:52Z