Feature services vs Direct database connections: Is there a prefered editing approach?

[DrewDowling]

Does Esri have a preferred method of editing data? I've noticed that most of the new functionality coming out focuses on service-based editing, parcel fabric, Utility network, etc. Is traditional versioning still a fully valid approach to editing?

I have a new project that can go either way: Traditional or Branch versioning. Traditional with direct database connections is going to be easier to set up and integrate with existing workflows, but it's not a deal breaker.

Which approach does Esri recommend?

[MarlonAmaya]

Hi @DrewDowling ,

Yes, there are some technologies that only support Branch Versioning. If your workflow model can go either way, the decision to go either branch or traditionally will be based on many factors within the organization. A big factor is how we want user's accessing the data (DB access or not). Traditionally versioning is still a valid approach. Here are some resources that can assist you in making the decision.

To Branch or not to Branch Blog : https://www.esri.com/arcgis-blog/products/arcgis-enterprise/data-management/to-branch-or-not-to-bran...

Versioning Types (shown limitations on both) - https://pro.arcgis.com/en/pro-app/latest/help/data/geodatabases/overview/versioning-types.htm

Enterprise Data management strategies - https://pro.arcgis.com/en/pro-app/latest/help/data/geodatabases/overview/data-management-strategies....

Marlon

[DrewDowling]

Thanks, Marlon. I was wondering if Esri has a preferred approach, as both are equal from a client's point of view.

[MarceloMarques]

Branch Versioning is the new technology and users should switch to ArcGIS Pro and Branch Versioning to enable more modern web editing workflows. But ArcGIS Pro also works with Traditional Versioning.

[DrewDowling]

Thanks, Marcelo, that helps.

[MelissaJarman]

Most of the versioning editing and administration workflows are similar between the versioning types. It really comes down to if you are wanting more service based editing workflows from a range of client applications. If you are ONLY intending on using ArcGIS Pro and you don't have one of the industry specific data models (UN/TN/parcel fabric), then you can decide what is easier to configure for this project.

You can always have a mixture of registration types in your geodatabase. I recommend you give branch a test spin with a few datasets to see. 

This video from last year's UC has some high level similiaries and differences at the beginning. check out around the 5 minute mark. 
https://mediaspace.esri.com/media/t/1_6w6jmm4q/309413912