SCTR’s Pune Institute of Computer Technology

Dhankawadi, Pune

AN INTERNSHIP REPORT ON

Title: Wayport

SUBMITTED BY
Name: Ayush Sakalkale
Class: TE 10
Roll no: 33268

Under the guidance of

Mrs. Sayali Gaikwad

DEPARTMENT OF INFORMATION
TECHNOLOGY
ACADEMIC YEAR 2024-25
 DEPARTMENT OF INFORMATION
TECHNOLOGY
SCTR’s Pune Institute of Computer
Technology Dhankawadi, Pune
Maharashtra 411043

CERTIFICATE

This is to certify that the SPPU Curriculum-based internship report entitled

“Wayport”

Submitted by
Ayush Sakalkale
Roll no: 33268

has satisfactorily completed the curriculum-based internship under the guidance

of Mrs. Sayali Gaikwad towards the partial fulfillment of third year
Information Technology Semester VI, Academic Year 2023-24 of Savitribai
Phule Pune University.

Mrs. Sayali Gaikwad Dr. Archana S. Ghotkar

Internship Guide Head
PICT, Pune Department of Information Technology
PICT, Pune

Place:Pune
Date:21/04/25
 ACKNOWLEDGEMENT

I would like to express my gratitude and appreciation to all

those who gave me the possibility to complete this report. Special
thanks is due to my Guide Mr. Manish R Khodaskar and
Reviewer Mr. Tushar A Rane whose help, stimulating suggestions
and encouragement helped me in all time of fabrication process and in
writing this report. I also sincerely thanks for the time spent proof-
reading and correcting my many mistakes
I would also like to thank my Internship Mentor Dr. Anant M
Bagade to continuously help me through the course of making this
report and also providing resources to complete the tasks.
Many thanks to the PICT faculty and Dr. A.S Ghotkar Mam
head of information technology department for providing me the
opportunity to complete my Internship and present this report by
providing all the resources required.

Name: Ayush Sakalkale

Roll No: 33268
 Contents

1 Title 5
2 Introduction 5
3 Problem Statement 6
4.1 Objectives 7
4.2 Scope 8
5.1 Designing and Developing 10
6 Modern Engineering Tools 12
8 Outcome/results of internship work 13
(screenshots of work done)

4
 1. TITLE
WAYPORT

2. INTRODUCTION
The Wayport platform represents a groundbreaking advancement in travel
technology, fundamentally transforming how users plan and book multi-
modal transportation journeys. Unlike conventional single-mode booking
systems that operate in isolation, Wayport creates a unified ecosystem that
seamlessly integrates flights, trains, and various combined routes into a
cohesive, user-centric platform. This integration allows travelers to discover
optimal journeys between any two locations without the traditional
constraints of mode-specific booking systems. The platform's sophisticated
architecture leverages a network of specialized microservices to process
complex routing algorithms that simultaneously evaluate multiple factors
including total travel time, cost efficiency, connection convenience, transfer
feasibility, and overall journey comfort. Each transportation mode is handled
by dedicated services running on specific ports allowing for specialized
processing while maintaining system cohesion through the aggregator
service. By addressing the long-standing fragmentation in the transportation
booking landscape, Wayport eliminates the need for travelers to manually
coordinate connections between different transportation modes, a process
that typically involves visiting multiple websites, comparing schedules
independently, and making separate bookings without any guarantee of
optimal connections. The system's comprehensive data models capture the
intricate details of each transportation mode, from flight segments with
terminal information to train journeys with class availability, creating a
foundation for meaningful comparison and integration of diverse journey
options

5
 3. PROBLEM STATEMENT

The transportation booking industry is fragmented, with separate platforms

for flights, trains, buses, and ferries. this forces users to manually coordinate
multi-modal journeys, navigating different interfaces, schedules, and policies.
planning such trips—especially to destinations without direct connections—
can be complex, time-consuming, and error-prone. travelers often need to
identify intermediate stops, match timetables across providers, calculate
connection times, and evaluate transfer feasibility without reliable local transit
information. this disjointed approach increases the risk of missed connections
and added costs due to delays, while also missing out on potential savings
from combined ticketing. wayport addresses these issues by offering an
integrated platform that algorithmically builds efficient, realistic multi-modal
routes, considering transfer logistics and alternative paths that are hard to find
manually. it simplifies planning, reduces effort, and reveals routes traditional
systems overlook.

6
 4.1 OBJECTIVES

1.Scalable Backend Architecture:

Develop a microservices-based system with dedicated ports for each
transportation mode, ensuring flexibility in processing multi-modal queries.
The architecture should support horizontal scaling, with integrated logging
and monitoring to provide insights into performance and potential issues.

2.Specialized Transportation Models:

Design distinct models for various transportation combinations,
incorporating unique business logic tailored to each mode's constraints.
Address specific challenges such as connection times, platform changes, and
transfer logistics while optimizing pricing strategies based on dynamic factors
like discounts and seasonal variations. Each model should ensure feasibility,
accounting for practical travel conditions and fare structures.

3.Aggregation System for Results:

Create an aggregation layer that manages asynchronous results from
various specialized transportation models, using parallel processing for
efficiency. Implement ranking algorithms to evaluate journey options based
on criteria such as price, duration, comfort, and convenience, with a
deduplication mechanism to avoid redundant choices.

4. User-Friendly Frontend Interface:

Design an intuitive, React-based user interface that clearly displays
complex multi-modal journeys, utilizing interactive elements like timelines
and filtering. Implement a progressive disclosure pattern, allowing users to
expand sections for detailed trip information, including transfer logistics and
terminal maps. Ensure accessibility features such as screen reader support,
keyboard navigation, and responsive design across all devices.

5. Optimized Route Search Algorithms:

Develop high-performance search algorithms that efficiently identify
viable routes while balancing speed and comprehensive results. Use
geographical heuristics to prioritize reasonable connections and apply search
space pruning to discard suboptimal routes early. Leverage caching strategies
and parallel processing to enhance the overall speed and accuracy of route
finding.

7
 4.2 SCOPE
1. Integration of Multi-Modal Transportation Data
Developed integration layers for real-time flight and train data using
robust APIs:

a) Integrated Amadeus API for accessing global flight schedules,

pricing, availability, and ancillary services.
b) Connected to specialized rail data sources for fetching train schedules,
platform info, seat availability, and class-wise pricing.
c) Implemented adapter services to standardize external data formats,
manage authentication, and handle API rate limits.
d) Applied error handling mechanisms with retries, fallback strategies,
and circuit breaker patterns to maintain system resilience.
e) Designed multi-level caching strategies for optimizing performance
and reducing redundant API calls.

2.Handling Direct and Indirect Flights

Designed logic to support both direct and multi-segment flight routes:

a) Evaluated routing options based on airport transfer times,

immigration/customs clearance, and baggage logistics.
b) Accounted for airline partnerships and codeshare agreements for
determining protected vs unprotected connections.
c) Used historical delay data to calculate connection risks and prioritize
more reliable options.

3.Train Journey Support with Class and Availability Details

Enabled comprehensive train journey planning with real-time seat
availability and dynamic pricing:

a) Parsed multiple class types (e.g., sleeper, first class, general) with
availability status like "available", "waitlist", etc.
b) Handled platform-level data, seat reservations, meal inclusion, and
coach positions.
c) Supported international rail connections, factoring in border control
delays and station transfer times.

8
4.Combined Route Planning Across Modes
Built logic for hybrid air-rail journey planning:

a) Identified optimal intermediate cities for switching modes (e.g., train

to flight), based on geographical and logistical feasibility.
b) Considered transfer times, local transport options, and airport/station
connectivity.
c) Filtered impractical combinations (e.g., overnight stays or peak traffic
areas) to recommend only realistic multimodal routes.

5.React-based Frontend with Advanced Visualization

Developed a fully responsive, accessible React application to visualize complex
journeys:

a) Implemented journey timelines, interactive maps, and progressive

disclosure for layered information display.
b) Provided filters for price, time, duration, number of stops, and mode
preference.
c) Ensured accessibility (keyboard navigation, ARIA labels, contrast
compliance) and device responsiveness.

6.Microservices Architecture and Deployment

Deployed the system using a containerized microservices architecture:

a) Packaged services using Docker with individual configurations and

dependencies.
b) Used service discovery, load balancing, and CI/CD pipelines for
smooth operation and scalability.
c) Integrated monitoring tools for technical (CPU, memory) and
business metrics (cache hit ratio, processing time).
d) Included canary deployments, rollback mechanisms, and alert
systems for operational resilience.

9
 5.1 DESIGNING AND DEVELOPING
The development of the Wayport Application followed a modular
and agile approach, ensuring continuous integration of features and customer
feedback. The design and development process consisted of the following:

Microservices architecture with specialized transportation models:

wayport is built on a microservices-based architecture where each transport
mode operates as an independent service with its own logic, data, and
runtime. this enables parallel development, isolated testing, and independent
scaling. the services include:
 Flight
 Train
 Train-Flight
 Flight-Train
 Train-Train
 Train-Flight-Train
 Bus-Train
 Train-Bus
Each service has domain-specific logic for routing, connections, and
pricing, communicating via standard rest apis. an aggregator service (with
configurable port) handles orchestration by routing queries, managing async
responses, and synthesizing results into a unified output for the frontend. this
architecture allows independent evolution of services with customized
optimizations per transport type.
Comprehensive data models for multimodel travels:
the system uses robust typescript interfaces (in models_types.ts) to model
flights, trains, and combined journeys.
 Flightsegment: includes airports, times, duration, airline details, and
layovers.
 Trainmodel: captures stations, availability, fare structures, and class-
specific info via classdetail.
Combined models (like flighttrainmodel, traintrainmodel):
Extend base models and add connection points, total duration, and aggregated
cost. Supporting models like ttsourceintermediateobject help assess viable
connections between segments. consistent typing improves integration,
validation, and frontend rendering.

External API Service:

10
 External data from amadeus and tripozo is fetched through dedicated
adapter services (running on port 5001). these adapters handle authentication,
retries, token refresh, rate limiting, and data transformation into internal
formats. caching is used at multiple levels:
 short-term for session-based results
 long-term for stable data like schedule error handling and fallback
mechanisms ensure platform stability even with third-party instability.
Containerization with Docker:
All microservices and supporting components are containerized for
consistent environments. dockerfiles use multi-stage builds for lean images
and resource-efficient deployments. containers include health checks, logging
via stdout/stderr, and runtime configuration through environment variables.
this supports seamless movement from dev to prod and reproducible local
setups.
Environement configuration management:
Services are configured via environment variables for things like
ports, api endpoints, credentials, and feature flags. startup-time validation
ensures proper setup before serving requests. defaults and documentation
support smooth transitions between environments while maintaining secure
and maintainable configurations.
Frontend Development with performance optimization:
The react-based frontend uses modern practices (via create react
app) like code splitting, tree shaking, and compression for performance.
production builds are hashed for caching, served via cdn, and optimized for
global access. apis are backward-compatible to support zero-downtime
deploys. performance metrics like load time and interactivity are monitored
and enforced.
API Gateway with orchestration:
The aggregator also serves as an api gateway, handling request
validation, centralized auth, rate limiting, and orchestration of multi-service
queries. it manages async calls, error responses, caching, and circuit breakers
for backend stability. this abstraction simplifies the frontend and enables
flexible backend evolution.

11
 6. MODERN ENGINNERING TOOLS USED
To build and deploy the Wayport Application efficiently and effectively, a
variety of modern engineering tools and technologies were utilized. These
tools facilitated frontend and backend development, version control, API
integration, deployment, and collaboration.

Tool/
Category Purpose
Technology
Building
Frontend interactive and
React.js
Development responsive user
interfaces
Creating RESTful
Backend
Node.js + Express.js APIs and handling
Development
server-side logic
Storing user data,
appointments,
Database MongoDB + SQL
feedback, and
resources
Source code
Version Control Git + GitHub management and
team collaboration
Testing backend
API Testing Postman APIs and
endpoints
Writing and
Code Editor Visual Studio Code debugging code
efficiently
Managing tasks,
GitHub Projects /
Collaboration issues, and
Issues
progress tracking
JWT (JSON Web Handling
Security
Tokens) authentication
Containerizatio To containerize
Docker
n application/service

12
 8. Outcome/ results of internship work
(screen- shots of work done)
1. Seamless Integration of Multiple Transportation Modes
 Users can book journeys combining flights, trains, and other modes in
one place.
 The system considers connection proximity, transfer times, and
immigration requirements for international transfers.
 It identifies optimal connection points, including major hubs and
intermediate cities for cost or schedule benefits.
 Baggage logistics and different ticketing systems are handled
automatically, providing a unified user experience.

2. Efficient Route Finding

 Advanced algorithms evaluate journeys based on duration, cost,
transfers, and comfort.
 It identifies non-obvious, cost-effective routes through intermediate
cities.
 The system adapts to multi-city trips, flexible dates, and alternate
airports.

3. Comprehensive Journey Visualization

 Journey info is displayed with clear times, durations, and transitions.
 Interactive visuals like timelines and maps make it easy to understand
each segment.
 Pricing is broken down by segment, with detailed info about terminals
and transfers.

4. Responsive User Interface

 The React frontend adapts for desktop, tablet, and mobile users.
 Touch-friendly and keyboard-accessible, ensuring smooth interactions
across devices.
 The UI is consistent, maintaining branding while adapting for
different screen sizes and input types.

5. Scalable Architecture
 Microservices ensure the system scales efficiently under high demand.
 The architecture supports horizontal scaling and handles failures with
resilience mechanisms (circuit breakers, fallbacks).
13
 Caching and optimized database queries ensure fast performance even
with high traffic.

Fig 1.Map Visualizer

14
 Fig 2. Routes Display 1

Fig.3 Routes Display 2

15
Fig 4. Routes Display 3

16
Fig.5 Routes Display 3

Fig 6. Route Detail Display 1

17
Fig 7. Route Detail Display 2

18
19
20
21