Return to Answer

added 3 characters in body

Source Link

edited Feb 21, 2018 at 7:50

I agree with most of the answer given, but let me shed my views on this too:

Without having DXA, you can achieve the same architecture where your Component Template serves JSON, so why would you need DXA? Well the truth is, you don't NEED DXA, but you might want it, because it is a community best practice. As Nuno already mentioned, you share a common code base with the rest and can get help from the entire community because they know at least some details about your implementation.
What exactly will you get in DXA? Well that depends on how you see it, the CD APIs are not so much replaced, b utbut wrapped around to provide you a more common API for web developers without needing specific Tridion knowledge, exactly aasas you already stated yourself. But note, DXA is not something magical or special, of course you can do something similar by using MVC, it is in essence just another MVC implementation, see answer #1 again for why you would want DXA.
DXA will never perform as fast as a static site where plain HTML pages are served from disk. But such an implementation haashas other drawbacks, like you need to republish the entire website for every little change etc. Dynamic web applications require a good caching strategy to perform, and DXA delivers that (allowing you to further improve when needed).

I agree with most of the answer given, but let me shed my views on this too:

Without having DXA, you can achieve the same architecture where your Component Template serves JSON, so why would you need DXA? Well the truth is, you don't NEED DXA, but you might want it, because it is a community best practice. As Nuno already mentioned, you share a common code base with the rest and can get help from the entire community because they know at least some details about your implementation.
What exactly will you get in DXA? Well that depends on how you see it, the CD APIs are not so much replaced, b ut wrapped around to provide you a more common API for web developers without needing specific Tridion knowledge, exactly aas you already stated yourself. But note, DXA is not something magical or special, of course you can do something similar by using MVC, it is in essence just another MVC implementation, see answer #1 for why you would want DXA.
DXA will never perform as fast as a static site where plain HTML pages are served from disk. But such an implementation haas other drawbacks, like you need to republish the entire website for every little change etc. Dynamic web applications require a good caching strategy to perform, and DXA delivers that (allowing you to further improve when needed).

I agree with most of the answer given, but let me shed my views on this too:

Without having DXA, you can achieve the same architecture where your Component Template serves JSON, so why would you need DXA? Well the truth is, you don't NEED DXA, but you might want it, because it is a community best practice. As Nuno already mentioned, you share a common code base with the rest and can get help from the entire community because they know at least some details about your implementation.
What exactly will you get in DXA? Well that depends on how you see it, the CD APIs are not so much replaced, but wrapped around to provide you a more common API for web developers without needing specific Tridion knowledge, exactly as you already stated yourself. But note, DXA is not something magical or special, of course you can do something similar by using MVC, it is in essence just another MVC implementation, see answer #1 again for why you would want DXA.
DXA will never perform as fast as a static site where plain HTML pages are served from disk. But such an implementation has other drawbacks, like you need to republish the entire website for every little change etc. Dynamic web applications require a good caching strategy to perform, and DXA delivers that (allowing you to further improve when needed).

Source Link

created Feb 21, 2018 at 7:44

I agree with most of the answer given, but let me shed my views on this too:

Without having DXA, you can achieve the same architecture where your Component Template serves JSON, so why would you need DXA? Well the truth is, you don't NEED DXA, but you might want it, because it is a community best practice. As Nuno already mentioned, you share a common code base with the rest and can get help from the entire community because they know at least some details about your implementation.
What exactly will you get in DXA? Well that depends on how you see it, the CD APIs are not so much replaced, b ut wrapped around to provide you a more common API for web developers without needing specific Tridion knowledge, exactly aas you already stated yourself. But note, DXA is not something magical or special, of course you can do something similar by using MVC, it is in essence just another MVC implementation, see answer #1 for why you would want DXA.
DXA will never perform as fast as a static site where plain HTML pages are served from disk. But such an implementation haas other drawbacks, like you need to republish the entire website for every little change etc. Dynamic web applications require a good caching strategy to perform, and DXA delivers that (allowing you to further improve when needed).