Technologies Used: Drupal 9, Subscription API, secured API, DND API, product catalogue API, catchup TV API, OTM Ad API, Callerfeel API, Docker, Azure blob storage, Azure RDS, Azure Kubernetes, Bootstrap, JS, CSS, Search API, Drupal commerce, Cron Job, Auth0 SSO login, Google Analytics, Oracle event API

Responsibilities: 

• Setup the site architecture
• Setup the commerce module
• Setup search API for advanced search
• Prepare a Docker file to deploy the image in the Azure container.
• Migrate public files from the virtual machine to Azure blob storage.

Critical ChallengesBackend:

1. The search API indexing failed due to the Azure RDS primary key setting.
2. Setting up search history when the user clicks on the search box is similar to the Google search engine.
3. Customize the cart and payment page for variable prices for on-demand services.
4. Calling additional API before and after subscription API to check whether the user session is still valid, and each API depends on the other API response.
5. Storing logs of API that will be required to investigate in case the payment failed and the user was charged.
6. Import the product from the API on the nighttime of Nigeria and reset the API date filter to fetch the new/updated records from the previous import date.

Solutions Implementation:

1. I did some investigations on it. I tried to override the parameter from the settings.php file, but that didn't work, so I created a patch for the search API module.
2. I used views with search API and AJAX autocomplete to return the popular search result in autocomplete with the statics module. I used JS with cookies to store and show the recent search below the searchbox.
3. There was one subscription where the user needed to enter the price amount in some range. I created a custom module. I created a custom module with a service class for DND, a subscription payment gateway, and a secured API to authenticate the user's transaction, whether it is a bot or a real transaction.
4. There were too many use cases. The one API depends on the other API response, and we need to handle and store the API responses and also need to check if the API was down.
5. Storing API logs and responses with each order in a fieldable database increases overhead in the database, so to overcome this issue, we stored the information in a private file system.
6. I created a custom module to fetch the subscription product information from the product catalogue. The API response was in pagination. The variation was in a nested array, and there were a lot of manipulations before storing the information in the backend. I used the que API with controller queue and service worker class with cron tab to solve this.

Critical ChallengesFrontend:

1. Lazy loading of the home page sections
2. Customize the add-to-cart form to remove the Ajax event and pass the additional parameter from the product variation custom field value to authenticate the user with a secured API and pass the plan details.
3. Separate checkout complete page for success, failed, and pending screens.
4. Customize the partner landing page for logged-in and non-logged-in users.
5. Integrate the Oracle event API to track the user's complete lifecycle from add to cart till payment completion.

Solutions Implementation:

1. The site has around 4 million records. The home page has a lot of sections with images, so I loaded the first few sections, and then after a few sections, I loaded with Ajax.
2. Changing the plan on the product cart was taking time due to AJAX, so I used the preprocess function to pass the variable in the twig and created an accordion with the data attribute to pass that information in the add-to cart. The cart button was custom. It was redirecting the user to another site for authentication and coming back on the checkout page with a third part to double-confirm before payment submission whether the user session is still valid or not.
3. I created a custom route with dynamic parameters. The page was redirected from the checkout based on the API response.
4. For logged-in users, we had to show the users subscription information based on the API response. There was an issue with caching, so I loaded the subscription information after page loading with Ajax.
5. We had a PWA that was calling the API in twice, and it was creating duplicate entries in the Oracle tracking dashboard. I created a patch for PWA. I also added a conditional logic on the add to cart, checkout, and payment complete pages to execute the Oracle event based on the API response.

Technologies Used: Headless Drupal, cron tab, bash script, Angular, Java, Skyword API, Rest API, Acquia

Responsibilities:

• Managing the project
• Creating a custom module to expose the product information for the frontend team.
• Run the product import at a specific time with the Drush and bash script in Acquia.
• Java was used as an intermediate layer to handle the single cart feature for five sites.
• Angular was used for frontend

Critical ChallengesBackend:

1. Returning more than 10K products with a single API response and all the necessary fields slow down the server, and sometimes it slows down the server also.
2. Importing or updating only those products that were needed without doing operations on all the products and running the Drupal queue API at a specific time was quite complex.

Solutions Implementation:

1. I used cachable response in the custom module. I made the module fully dynamic with a field type helper function to return the field value. I used varnish cache to cache the API response and also used 1 day for cache expiration.
2. I used ID and some additional parameters to check the existing product to see whether it has been updated or not. I used queue service worker, bash script, drush command, and Acquia cron tab to run the import at a specific time.

Technologies Used: Drupal 8, MySQL, CSS, JavaScript, BSD API, Pantheon, Migration, Drupal 7, Amazon Kindle

Responsibilities:

• Drupal 7 to Drupal 8 migration
• Redesign the website
• Twig template creation

Critical ChallengesBackend:

The initial version of Drupal 8 was just launched, and we had a very tight deadline to complete the project in 2 months.

Solutions Implementation:

I did a lot of research for custom module creation since I was new to Drupal 8. Drupal 8 code was purely based on OOPS, so the debugging was quite complex. I used the devel module and breakpoint in the code to debug the code.

Critical ChallengesFrontend:

Passing information from the preprocess function to Twig was complex since we were new in Drupal 8 and the initial version was just launched. A minor code mistake throws a website encounter error.

Solutions Implementation:

I researched the core theme for creating a Twig template, used the Twig template debug function, and did some research on how to write a Twig plugin.