Code for Careem Hackathon Event Bangalore India 2017

The code has been delpoyed in AWS you can see here live: http:https://ec2-35-167-86-187.us-west-2.compute.amazonaws.com/

One of the goals we strive towards at Careem is creating a perfect booking experience for our Customers- extremely reliable ETAS, accurate locations, best Captains and so on. Build a ride dispatching platform that collects location updates from ‘drivers on the move’ to later be used as data to dispatch the best driver to a customer that wants to book a ride. It is up to you to creatively decide the features, capability and complexity of the platform (Eg: Moving cars on the map, multiple bookings per driver etc.)

What REST frameworks you will use In-memory vs. persistent storage Testing (unit testing/integration testing/mocking etc.) Optimized dispatching algorithms Service Oriented Architecture Asynchronous processing of location updates like message queues Horizontal scaling Design patterns, dependency injection etc. We will be judging you on the following criteria:

1. Innovativeness
2. Architecture
3. Manageability and Scalability
4. Application Performance
5. Code Toxicity
6. Robustness
7. Completeness (Demoable)

Project is all about booking a ride. Here We are priortized things for booking a cab based on the following criteria such as Minimum wage of the driver on that current day, Longest waiting time of the driver and shortest distance driver. We covered the distance of 1 Km from the current customer location based on the latitude and longitude We will search the cab and allocate based on the above criteria. The user setting preferences can be done apart from the default settings like switching driver gender and Minimum driver rating as well.

In order to prevent Race Condition upon booking a Queueing system is used for a specific driver. The location of the driver is get trakced for every 5 seconds and we are using a Amazon SQS queue to process the location queue. We are using Redis to keep track of the moving car with the customer latitude and longitude until the destination is reached. We can lively locate a vehicle. After the destination is reached location data is moved to mysql from redis.

1. SPRING MVC
2. Hibernate
3. MySql(All Meta informations)
4. Redis(frequest changes to the current location of the cab is stored here.)
5. SQS(Location Changes Information will be stored by lining up in Amazon SQS)
6. Queuing System(To Prevent Race Condition, an internal queuing system is used)
7. JUnit(For unit run cases)

1. mvn clean
2. mvn install
3. mvn deploy

UserModel:
{
	Long userId;
	String name;
	String email;
}

DriverModel:
{
	Long driverId;
	String bookingStatus;
	Date lastDriveFinishedDate;
	Long userId;
	String name;
	String email;
	Long cabid;
	CabType cabType;
	String gender;
	String rating;
	Double latitude;	
	Double longitude;
}

Returns CustomerModel GET /customer/list Returns CustomerModel POST /customer/create Returns CustomerModel PUT /customer/edit Returns CustomerModel DELETE /customer/delete

CustomerModel: 
{
	String preference;
	Long customerId;
	String name;
	String email;
	String gender;
	Long userId;
}

CabModel
{
  Long cabId;
  CabType cabType;
  Long seatsCount;
}

CabType {
	MINI,
	PRIME
}

BookingModel {
	Date lastDriveFinishedDate;
	Long customerId;
	Long driverId;
	String preference;
	Date lastDrive;
	String bookingStatus;
	CabType cabType;
	Long seatsCount;
	String distanceTravelled;
	String rating;
	Double cost;
	String costDenomination;
	Double customerFromLatitude;
	Double customerFromlongitude;
	Double driverFromLatitude;
	Double driverFromLongitude;
	Double driverEndLatitude;
	Double driverEndLongitude;
}

1. Prathap Manohar Joshi : https://github.com/itisjoshi

2. Karthekeyan Devanand : https://github.com/Karthekeyan-Engine