Skip to content

HaotingLiu/fdsSystem

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

2 Commits
 
 
 
 
 
 

Repository files navigation

fdsSystem

This is a system which is used to take the place of the old gds system.

The overall architecture

The overall components of this system will be Kafka and redis. Considering the ditribution feature of this system, the server will be nginx.

The implemention of this system

Why kafka

kafka is actually the main part of this project. As kafka can achieve the function of distribution and with high parallesim. In this project, kafka will be used as the main distributor, take the palce of the si and frontend function of the old system.

Why redis

The redis is used as the cache to take the place of the aac in the old system.

What will be the new database

The new data base can be any one, but I prefer nosql one. I am not sure by now.

How to implement AAM in this system

This is the main problem of this project.

Should we use the edifact or change to xml or json

I still want to stick to the old edifact. But let's keep json as a choice.

How this system will beat the old system

The old system got money from the aieline company, and this gave them great profit. The new system will charge nothing, the whole system will be all free. We get profit by advertising the airline companies and the hotels and many such things, but no fee for booking for checking availability.

Can we search the journey as the old engine did

Now, no. But it will be online in the future. This will be a key for designing the whole system. As we have to be flexible to the possible change in the future.

About

This is a system which is used to take the place of the old gds system.

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

 
 
 

Contributors