I like my old friend

 

It is an old post based on old idea, it is not relevant anymore.

 

XML VS JSON. Which one is the super-power to exchange data from server-side to client-side? This is old debate. You will find thousands article about it. Why am I writing about it?

When I was working with IBM Toronto Lab, someone asked me why I like XML. I said my reason and I have only one reason. Most of the people like JSON because of its hype and unfortunately, they did not get the opportunity to work with complex data. 

JSON is the best approach to transfer data from server-side to the client-side because JSON is lighter than XML and easy to fetch data from JavaScript. It is true only if complexity of data and business requirement are simple.

Now think about the following scenario, I am working with scheduling software where XML contains schedule of each team member. I need to send more than 1000 data from server to client side such as, RIA at a time.  The big picture of the XML is:

<company>
 <department-list>
  <team-list>
   ---------------------
  </team-list>
 </department-list>
</company>

[I am assuming, number of department are 10, teams of each department are 10, and members of each team are 10. Here, I am concerning only list type data. Obviously, in real life we have more data, like name, tile, skills, vacations etc.]

So company contains list of departments where each department contains list of teams, each team contains list of team members and each team member contains schedule data list. Schedule data list contains 5/7 days schedule of each team member. Now it is not so easy to produce JSON string according to this business requirement. JSON will produce a number of brackets (), {} [] because of chain list of objects. JSON's brackets will be more shocking than angle brackets <> of XML. Too many brackets of JSON generate terrible maintenance procedure in the future.

XML might be verbose than JSON, but XML is easy to follow, easy to debug, easy to parsing, and easy to modify according to the business needs because of its simple structure. According to my point of view, XML is the best where large amount of data need to be sent from server to client at a time. So I like my old friend XML very much.

Comments

Post a Comment

Popular posts from this blog

There is a process already using the admin port 4848 -- it probably is another instance of a GlassFish server; ERROR

After long time later, I am writing my programming blog again. Today, I downloaded glassfish-3.1.2.2-unix.sh. I am running Fedora 16. After successful installation of the glassfish, I was getting error when I ran the the following command: asadmin>start-domain "There is a process already using the admin port 4848 -- it probably is another instance of a GlassFish server. Command start-domain failed." Then I checked my hostname of the machine: hostname I got my hostname is nix-domain Now, nix-domain is not listed in the /etc/hosts file. Therefore, I added nix-domain in the file. 127.0.0.1               localhost nix-domain Now, I tried to run the start-domain again. It started perfectly without any error. Therefore, I understood that my machine assigned hostname 'nix-domain' is not listed in the hosts file, glassfish generated the error. I am hoping, it is not only the solution, there must be...
Read more

How to install Homebrew in Mac OSX (High Sierra)

Homebrew setup guide This guide describes how to install Homebrew and few ferequently used Homebrew commands. Using Homebrew you can install software very easily. It is like linux "yum" command. Install Homebrew (The missing package manager for OS X): $/usr/bin/ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)" $brew doctor   (You should see "Your system is ready to brew." on the console output. Do not move forward unless you see this.) Common commands: Check version of brew:    $brew --version Search Homebrew repo: $brew search %app name% (i.e: I want to check "wget" is available or not. $brew search wget) Check app information:    $brew info %app name% (i.e: $brew info wget) Install software package: $brew install %app name% (brew install tree) Uninstall software package: $brew uninstall %app name% (brew uninstall tree) Check installed packages in your system: $brew list Ins...
Read more

WildFly 19 and Log4J2

In this post, I would like to share my story about external configuration file of Log4J2. I developed a Java web application in WildFly 19 application server. It was my pet project. I followed few strict rules about 3rd party libraries. For example, I did not use log4j2-web library/jar file. It was the challenge because in some workplace you cannot have luxury to get all bells and whistle. You have to accept the situation. Therefore, I took this challenge to use external configuration file of Log4J2 in the web application without depending on log4j2-web jar file. My development environment's logging configuration is not same as production environment. In this case, I do not want to swap between development configuration and production configuration file during deployment.    The above situation can be mitigate by two ways: Use external logging configuration file. User application server specific logging system. For exampke, ...
Read more