Development comparisons

[jhadobe]

This PR adds comparison info between in-process and out-of-process extensibility. Highlighting what is available in Commerce vs what is achievable with App Builder + Commerce.

staging:

• https://adobedocs.github.io/commerce-extensibility/app-development/
• https://adobedocs.github.io/commerce-extensibility/app-development/app-development-comparison/
• https://adobedocs.github.io/commerce-extensibility/app-development/services-comparison/

[jhadobe]

A few questions for @keharper:

• Do you have ideas for better page names?
• Should I break the third-party integrations section into a separate page?
• app-development-comparison looks a little flat due to the similarity between H2/H3, but the table structure was not conducive either. Any ideas on visually separating these sections? All I can think of is to use more unordered lists, like in services-comparison.md.
• How do we want to credit the developer?

[nuzil]

how about to add here a note that native HTML + CSS is also an option?

[nuzil]

Will pass it also to @keharper
We discussed that we need to add 2 sections for

1. Instead of treating in-process and out-of-process are equals, we should be clear that unless absolutely needed, we recommend developers always choose out of process
2. In services comparison, we should be clear that modifying the default MySQL database can cause upgrade issues, so we recommend using App Builder with state database for simple app specific data, and a 3rd party database for more complex needs.

My suggestion is to add block for point 1:

In-process extensibility model currently has a lot of disaadvantages like, increasing maintenance costs, reducing software stability, increasing AC server overload and more.
Looking on those factors and also on increasign of business compexity and technologies stack, we recommends to use out-of-process model as much as it possible

And similar for 2nd

[jhadobe]

Will pass it also to @keharper We discussed that we need to add 2 sections for

1. Instead of treating in-process and out-of-process are equals, we should be clear that unless absolutely needed, we recommend developers always choose out of process
2. In services comparison, we should be clear that modifying the default MySQL database can cause upgrade issues, so we recommend using App Builder with state database for simple app specific data, and a 3rd party database for more complex needs.

My suggestion is to add block for point 1:

In-process extensibility model currently has a lot of disaadvantages like, increasing maintenance costs, reducing software stability, increasing AC server overload and more.
Looking on those factors and also on increasign of business compexity and technologies stack, we recommends to use out-of-process model as much as it possible

And similar for 2nd

Thanks @nuzil I had already added bolded "Recommended method" text to all the "App Builder" sections to help clearly emphasize that OOP is the best option. I've also added a version of your quote above.

[slamech]

"Each approach has its own set of advantages and use cases, and understanding them is crucial for developers and businesses looking to maximize their platform's potential" - Can we change this line to say something like "Adobe recommends adopting out-of-process extensibility where possible due to its ease of maintenance."