JSON only between backend and frontend

 

I'm designing the architecture for a new web application. I think that communications between the backend (server) and the frontend should be JSON only. Here are my arguments:

  • Its the client responsibility to manipulate and present data in its own way. The server should just send to the client the raw information needed.
  • JSON is lightweight and my application might be used by remote clients over poor mobile connections
  • It allows multiple front-end developments (Desktop devices, mobile devices) and has the potential to create an API for other developers

    • I can't see any counter-argument to this approach, considering that we have internally the frontend skills to do almost everything we need from raw JSON information.

    Could you provide counter-arguments to this JSON-only choice so that I can make a more informed choice? There must be some as a lot of backend frameworks (think about the php ones) still advertise HTML templating to send HTML formatted responses to the clients. Thanks

    UPDATE: Even though I researched the topic before, I found a similar and very interesting post: Separate REST JSON API server and client?

    在市场上已经有很多支持Json的前端框架，其中一些是骨干，下划线，角度等。现在如果我们谈论后端，我们通常使用基于REST的通信来处理这种类型的应用。所以我认为这种类型的体系结构已经退出市场并且运行得很好，特别是如果我谈论基于移动的应用程序。

    链接地址: http://www.djcxy.com/p/45642.html

    上一篇: 从另一个控制器消费本地JSON API

    下一篇: JSON仅在后端和前端之间