Your problem description is pretty thin, so it's hard to tell which approach works best for your users. Since you mentioned configuration information, I would assume that user input has to be validated so that you don't store inconsistent data.

Saving the data explicitly with a submit button is probably reasonable. You might use visual feedback in the form to signal changed data and invalid inputs, enabling the submit button only when there are changes and the entered data is consistent as far as your frontend can determine.

In any case, be prepared for a few rounds of implementing a form, testing it with actual users, and analyzing the usage patterns to improve.

Your problem description is pretty thin, so it's hard to tell which approach works best for your users. Since you mentioned configuration information, I would assume that user input has to be validated so that you don't store inconsistent data.

Saving the data explicitly with a submit button is probably reasonable. You might use visual feedback in the form to signal changed data and invalid inputs, enabling the submit button only when there are changes and the entered data is consistent as far as your frontend can determine.

In any case, be prepared for a few rounds of implementing a form, testing it with actual users, and analyzing the usage patterns to improve.

Regarding real world examples: Most UX designers will probably have considered the options and made a reasonable decision, but you will still find bad examples all over the place. Use examples such as that of Discourse to learn about options, but don't simply copy them. Find out what works well for your application and users.