We where working on a project in order to link our own 2 different websites.
Then we (my dept. and IT) decided for one of it to take over its others content and user data. (The "master" site had CMS, the "slave" site doesn't)
So without replace it, or take it down, we wanted to collect and use personal information from one website in order to provide personalized information and unique user journeys and also a better User Experience on the other website.
Also to have by it's CMS a way to run personalized campaigns by our own, without the help of IT department.
The 2 websites where on different machines, different platforms, different data bases, etc. (one on APACHE and other on TomCat) Both websites where hosted on our DMZ on machines installed in JAIL, and with 2 layers of security above (firewalls) So we deiced to use SOAP APIs to read and write data from one system to the other. Plain XML files.
Our head of IT department rejected all of our work after 6 months of development, and with fully and perfectly running API's, he takes down our project stating the following:
The reason why the decision was made, is based on the following facts:
- Data security related issue.
- Increase of complexity of the systems introducing a new interface in the architecture.
- Increase points of failure
- Longer time to market for every new change
- From customer point of view, they will have inconsistent customer experience. Same order capture functionality exists in ["System"].
All above were the reason to not develop the site in this way.
My response was:
- We have written approval form Security Dept. Data exposure with web services lower the security risk, being internal server to server communication, instead of client-server connection
- This new interface replace older one: [System name] front end. So instead of complicated JAVA scripts, HTML page, Ajax, etc, we rely on XML files
- As log as it replace the existing [System] front end, the point of failure are identical, as layers. But lower by complexity.
- Any change it will be done in the same way as it was before, the only difference is that, as I said before, instead of changes in Front end, it will be replaced by changes in Web Services.
- The existing setup is inconsistent customer experience, as some orders came from multiple systems ( Shop and [System name]). The shop should have this functionality, only.
Am I wrong?! Why?