Scribd
Upload
5 views

Solving XML Problem

The document addresses a slow hotel listings issue after XML integration, likely due to real-time data fetching, large data volume, and synchronous parsing. Solutions include using a local cache, optimizing search results delivery, preprocessing the XML feed, implementing asynchronous background sync, and utilizing CDN for media. While the problem is manageable, it requires setting up a backend, database, and scheduling logic.

Uploaded by

aym.djebaili
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
5 views

Solving XML Problem

The document addresses a slow hotel listings issue after XML integration, likely due to real-time data fetching, large data volume, and synchronous parsing. Solutions include using a local cache, optimizing search results delivery, preprocessing the XML feed, implementing asynchronous background sync, and utilizing CDN for media. While the problem is manageable, it requires setting up a backend, database, and scheduling logic.

Uploaded by

aym.djebaili
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 1

Solving XML problem

Yes, the issue you're facing is solvable, and while it can be technically involved, it’s
not insurmountable.

Here’s what’s likely going on and how to fix it:

🔍 Problem: Slow hotel listings after XML integration


This typically happens because:

1. Your mobile app is fetching hotel data in real time from the other company’s
XML API.
2. The XML feed might return a large volume of data with slow response times
or no caching.
3. You're possibly parsing and rendering data synchronously on the client side.

✅ Solutions:

1. 🧠 Use a Local Cache or Sync Database


o Instead of fetching data from the XML feed every time a user searches,
fetch and store the data periodically (every few hours) in your own
database.
o Your mobile app then queries your optimized database, not the slow
XML source.
o Tools: Use a cron job + a small ETL pipeline to parse and update your
local DB.
2. 🚀 Optimize Search Results Delivery
o Add pagination, filtering, and sorting on your backend to avoid
sending too much data at once.
o Use indexes in your database for faster query responses.
3. 📦 Preprocessing the XML Feed
o Convert the XML feed to JSON or insert into a structured format once
and reuse.
o Clean and normalize the data once during ingestion.
4. Asynchronous Background Sync
o Use background jobs to fetch and update hotel availability, prices, or
images in intervals.
o Your app stays fast because it’s not waiting for the XML server to
respond every time.
5. 🌐 Use CDN or Image Caching (if media is slow to load)
o If hotel images are part of the delay, use CDN hosting or lazy-loading
on the frontend.

Is the problem difficult? Not really, but it requires:

 Setting up a small backend and database.


 Some XML parsing + scheduling logic.
 Possibly a DevOps tweak for regular syncing.

If you'd like, I can help you plan a technical architecture or even give you starter code
for syncing and caching the XML feed.

You might also like