We’re mid-migration to a more service-based Enterprise GIS and trying to understand how others are handling this transition.
Our current setup:
- 300+ layers in an enterprise geodatabase
- 8-10 editors, and a large number of read-only viewers
- Utility Network (water, storm, wastewater) is branch versioned in separate geodatabases
- Remaining data is traditional versioned
- Attribute rules are in place and currently being validated with an asset management integration
- Current workflow still uses geodatabase replication (edit DB + read-only DB)
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.
Questions:
- How are you handling edit vs read-only access? Separate services for each, or view layers/permissions from a single service?
- How are you avoiding service duplication for hundreds of layers?
- 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?
Would really appreciate hearing what has worked (and what hasn’t).
Thanks!
