Md Mostafizur Rahman

Developed a Swiss bike rental company's application's back end to manage their bikes.

The application's primary purposes were onboarding new vehicles into the platform, managing different inventory, and managing the servicing of the bikes. Additionally, the app provided warehouse management, platform user management, and can display a comprehensive report graphically.

Implemented in the project was a REST API to create a mobile application for better service management. The REST API was designed and delivered to produce various reports and historical data quickly.

I led the project and was one of the core individuals that planned the whole architecture and developed the back-end portion.

To view additional details about this project:
https://sharing-platform-staging.welldev.io
Username: mostafizur.rahman@welldev.io
Password: 123456
ENV: Staging

The API documentation for flight content suppliers (GDS, NDC, airlines), hotels, and car rental suppliers had been investigated and implemented with either REST or SOAP. As all suppliers differ, the API structure, layout, response, and requests differ. The project involved consuming those APIs to expose a normalized fixed response to the customer. Customers would consume only one REST API to receive the content from all the different suppliers.

The challenges comprised managing different requests, authentication processes, sessions, etc., for those varying suppliers. Also, as the documentation was not enriched, finding the right way to consume those APIs was challenging.

In this project, the codebase had been divided into different layers and services so that every layer and service would be responsible for various purposes. For example, layers for accepting the customer request, validating the request, converting the customer request to a supplier-specific request, making requests to a different supplier (a parallel process), mapping layer, data storing layer, exception handling layer, response structuring layer, and finally, a response layer.

The project entailed building a web application to track the different vehicles using the API provided by the vehicle tracking device. It was an admin-based app. The user would not have access to this platform.

Organization-authorized personnels could perform the following operations:
1. Add a new vehicle into the system
2. See the list of vehicles with essential details
3. Visualize all the vehicles on the map
4. Select a specific vehicle and check the status, position, and other details of that vehicle
5. Turn on the alarm using the 'find vehicle' button via the tracking device placed on the vehicle
6. Retrieve essential information about the vehicle, including power status, speed, temperature, battery, connection, odometer, distance, charging status, etc.
7. Set the max speed of the vehicle
8. Turn on or off the power of the vehicle
9. Add new users to the platform for proper management
10. Manage the existing users

Since it was a role-based application, not all users could perform all the tasks; only the authorized user could perform privileged actions.

I designed the back-end architecture and developed the entire back end, including the project specification and remote device tracking API integration.

An eCommerce website that was developed with Spree Commerce or Solidus. I built the back end to load all product data from a legacy system and worked with front-end developers to display it. The application accepted different types of payment options, including invoice and post-finance.

A highly confidential application with some essential features and functions such as:
1. Storing customers' credit card details.
2. The customer can use the stored credit card when purchasing any item.
3. If the customer wanted to use a saved card, the vault performed all the communication with the third party for a successful payment.
4. The application only maintains the payment process. It does not emphasize the third party or any other aspect of the transaction.

My responsibility was to create the system to fetch the credit card and send it to the appropriate third party to make the successful payment.

The project was Self-Assessment Questionnaire D (SAQ D) certified, and I am also a Payment Card Industry Data Security Standard (PCI-DSS) certified member.

Developed a SOAP API system based on FerryGateway standard protocol to deliver ferry content to customers. I was responsible for the architectural design of the back-end API, flow management, and SOAP API design planning and development.

The project was the innovation of a Ruby gem to consume the REST API of a rental management system. I developed the Ruby gem with the help of Ruby gem rest-in-peace and Faraday, which resulted in this communication gem.

Creating a SOAP API has become challenging recently. I developed a Ruby gem to generate the SOAP API with a Web Services Description Language (WSDL) file for any project if required. The Ruby gem helped to maintain the structure of SOAP APIs.

A Ruby Gem that tracked different types of real-time system exceptions and reported them to Rollbar Inc. so that the development team could get the update of any system exception and follow them. The project allowed the action to be performed directly with Rollbar's integration, but the Ruby gem helped to manage it consistently with a proper backtrace and metadata reporting.

I developed the Ruby gem.