Skip to content
View rajibkuet07's full-sized avatar
🏠
Working from home
🏠
Working from home
3 followers · 18 following

Achievements

Achievement: Pull Sharkx3Achievement: QuickdrawAchievement: YOLO
BetaSend feedback

Achievements

Achievement: Pull Sharkx3Achievement: QuickdrawAchievement: YOLO
BetaSend feedback
Block or Report

Block or report rajibkuet07

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Please don't include any personal information such as legal names or email addresses. Maximum 100 characters, markdown supported. This note will be visible to only you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse
rajibkuet07/README.md

Hey! Nice to see you.

I'm Back-End Developer | PHP, NodeJS, JS, TS | Problem Solver | Learning Blockchain

Things I code with

JavaScript TypeScript PHP Solidity Nodejs NestJs Apollo GraphQL REST API React redux SolidJS Material UI Tailwind CSS Bootstrap WordPress MySql PostgreSQL MongoDB redis Docker Postman Insomnia

With dedication and continuous learning over the last few years, I have had the opportunity to support various small and mid-level companies with my technical skills. My commitment to critical thinking and attention to detail helped me provide efficient, scalable, and robust solutions to problems that address real-world issues. Throughout my journey as a proficient Back-End developer, I have contributed numerous web applications specifically microservices, RESTful, and GraphQL APIs collaborating with diverse teams. I'm eager to leverage my technical talents in tackling new challenges and driving impactful initiatives to any new opportunities.

  • 🌱 I’m currently learning Blokchain Development & advance development with Nest JS

  • 💬 Ask me about Microservices(gRPC, Kafka), RESTful or GraphQL APIs, Node, Nest, React, Solid, PHP, WP, Redux

  • 📫 Write me something to contact@rajibdey.dev

  • 👨🏻‍💻 Have a look at my portfolio on Rajib Dey

  • ⚡ Fun fact I love to play badminton & riding bike!

Counters

Most Used Languages

Rajib's GitHub Stats

Rajib's GitHub Streak Stats

Get in touch with

Github Twitter LinkedIn HackerRank LeetCode

Pinned

  1. plugin-scaffold plugin-scaffold Public

    A fully object-oriented boilerplate for WordPress Plugin created by the developers for the developers. Incomplete!

    PHP 1

  2. wc-waafi-payment-gateway wc-waafi-payment-gateway Public

    HTML 1

  3. data-structures data-structures Public

    Data structures and algorithms in PHP and JS. Random problem solving with the explanation.

    PHP 1

  4. nest-kafka-best-practice nest-kafka-best-practice Public

    TypeScript

  5. Consume OpenAPI Specifications in an... Consume OpenAPI Specifications in any application
    1 
    ### Consume OpenAPI Specifications in any application
    2 
    
              
    
              
    
                3
                
    > Suppose the api that we will use for openapi specs is `ucs` and the app that will consume the openapi spec is `core`
    
              
    
              
    
                4
                
    
              
    
              
    
                5
                
    #### Approaches for handling all routes of ucs from core with proper type safety
    
              
    
          
    
    
    
  
    

    6. 

      

  6. 
  
    
    
    
      
    
        
        
          Kafka Retry Mechanism
Kafka Retry Mechanism      
    

          
    
              
    
                1
                
    ## Retry Mechanism in Kafka
    
              
    
              
    
                2
                
    
              
    
              
    
                3
                
    - Create a database table for the retry events - id, topic, partition, message, hash(md5(the unique identifier for the failed message)), offset, counter(count of retry for this message), nextEventTime(DateTime | gradually increase based on the counter), published(false | true whether or not a retry message is published in the topic again), handled(false | true whether the message handled again), status(success | error status of the event when handled again)
    
              
    
              
    
                4
                
    - When an error happens in any consumer emit an event to the retry topic. The retry topic can get a message consisting of hash(md5(the unique identifier for the failed message), topic(topic name of the failed message), partition(partition number of the failed message), message(actual message of the failed message), error(error data or string for which the previous message failed), fallback(optional | {topic: "fallback topic name", value: "fallback message value"} | if max count exceeds then produce this fallback topic with the value as message), configs(optional | if some configs need for this retry event message like initial retry time, max retry time, max count))
    
              
    
              
    
                5
                
    - In the retry topic consumer, it will store a retry event data for the failed event in the database
    
              
    
          
    
    
    
  
    

    7.