Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 937719
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 15, 20262026-05-15T21:31:21+00:00 2026-05-15T21:31:21+00:00

Consider that you have System_A which is a web application. And System_A has simply

  • 0

Consider that you have “System_A” which is a web application. And System_A has simply 3 layers: UI, BusinessLayer and Data-Layer.

And now you want to make a widespread refactoring of System_A (the UI and BusinessLayer only) while it is working as a live product.

What should be the safest strategy of refactoring System_A and release the refactored product after a good testing -let’s call it “RF_SystemA”- in a way that it can be reversed to System_A even in case of an unexpected bug (without forcing the users to change their URLs)?

  • 1 1 Answer
  • 1 View
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-15T21:31:22+00:00Added an answer on May 15, 2026 at 9:31 pm

    I haven’t much to do with Web-Development, but just an idea:

    You could write/generate a redirect-Layer first like so:

    Let’s say you had three functions in System_A like this:

    System_A.Call1(...)
    System_A.Call2(...)
    System_A.Call3(...)
    

    Then you could rename the calls like this…

    System_A.Call1(...) -> Old_System_A.Call1(...)
    System_A.Call1(...) -> Old_System_A.Call2(...)
    System_A.Call1(...) -> Old_System_A.Call3(...)
    

    …and create a temporary redirect system like this:

    System_A:Call1(...) { Old_System_A.Call1(...); }
    System_A:Call2(...) { Old_System_A.Call2(...); }
    System_A:Call3(...) { Old_System_A.Call3(...); }
    

    This system could go live immediatly.

    Then you could create your Refactoring classes bit by bit, test them and just change the redirection calls.
    After refactoring is complete, you remove the redirection calls and just use the reafactored system.

    The granularity of your redirection should correspond to the granularity of your refactoring. So if you refactor individual functions and the function signatures stay the same, you can use the approach as stated above.
    If you completely redesign whole parts of your system, you could redirect the whole parts.

    Example for web:
    You have index.php which mainly calls 3 functions: header(), body() and footer().

    You could either redirect the calls to header, body and footer (if the signatures stay the same), or you could redirect the whole thing and call only one function from your index.php like “currentIndexPhp()”;

    currentIndexPhp() would then initially call header, body and footer.

    If you organize your folders and files accordingly, you should be able to control the refactoring quite nicely.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.