Scribd Logo
Upload

Welcome to Scribd!

  • How It Worked: Application

    Uploaded by

    Firstnaukri
    6 views7 pages
    The document describes a solution for centralizing dropdown data across multiple applications. Previously, each application had its own dropdown cache files that needed updating during deployment whenever the dropdown options changed. The new solution involves a centralized dropdown API with a database backend. Dropdown changes are made through a web interface and then propagated to all applications, clearing old caches and regenerating new ones. This reduced the time needed to deploy dropdown changes from about 1.5 weeks to just 1.5 minutes.

    Original Description:

    Original Title

    U4fd9b03d84f39

    Copyright

    © Attribution Non-Commercial (BY-NC)

    Available Formats

    PPT, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    Report this Document
    The document describes a solution for centralizing dropdown data across multiple applications. Previously, each application had its own dropdown cache files that needed updating during deployment whenever the dropdown options changed. The new solution involves a centralized dropdown API with a database backend. Dropdown changes are made through a web interface and then propagated to all applications, clearing old caches and regenerating new ones. This reduced the time needed to deploy dropdown changes from about 1.5 weeks to just 1.5 minutes.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as PPT, PDF, TXT or read online from Scribd
    Flag for inappropriate content
    Download as ppt, pdf, or txt
    6 views7 pages

    How It Worked: Application

    Uploaded by

    Firstnaukri
    The document describes a solution for centralizing dropdown data across multiple applications. Previously, each application had its own dropdown cache files that needed updating during deployment whenever the dropdown options changed. The new solution involves a centralized dropdown API with a database backend. Dropdown changes are made through a web interface and then propagated to all applications, clearing old caches and regenerating new ones. This reduced the time needed to deploy dropdown changes from about 1.5 weeks to just 1.5 minutes.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as PPT, PDF, TXT or read online from Scribd
    Flag for inappropriate content
    Download as ppt, pdf, or txt
    of 7

    How it worked

    Application

    database

    Generator Script

    Cache (PHP Array/ Javascript Array)

    How it worked
    MNJ ResDex JobSearch

    Cache

    Cache

    Cache

    generator

    generator

    generator

    Database

    The Problem

    Different applications have similar dropdowns, eg: City, College, Course Cache files has to go through deployment process. Any addition/change in common dropdown required change in every application.

    Process time: 1.5 weeks

    Solution: Centralized Dropdown


    Centralized Dropdown DD API Clients MNJ

    Client configs DD API Generators ResDex

    cache

    DD API

    JobSearch

    Database

    How it works
    Dropdown web Interface

    Changes queue

    Cache

    Read Queue

    Update DB

    Clear Cache

    Run Generators

    Call Client Triggers

    DD Queue Processor Database

    Cache Synchronization: Harmony

    Server 1 folder

    Server 2 folder

    Server 3 folder

    Harmony sync folder

    Achievement

    Time needed to deploy any change in a dropdown has reduced to 1.5 minutes from about 1.5 weeks.

    1.5 weeks to 1.5 minutes

    You might also like