Saturday, May 4, 2019

What would be a possible answer to this legacy problem?

So, there was a question for a job interview for a .NET Developer, which had me stumped. Looking for some answers here, to improve my knowledge (I obviously got rejected for the job). It goes like this:

There is a web application which lists a company's products. It has two pages - a login page and a page displaying the products (which is loaded after the user logs in). It uses a Microsoft Access database for the backend, which was built over a decade ago. The application also crashes often (the reason is unknown). The original developer of the application is no longer available.

The application needs to be redesigned, with the following goals:

  • The existing data needs to be preserved.
  • The application needs to support concurrent login of 500 users, and have the ability to be scaled up in the future.
  • The application should allow offline access

Describe how you would perform the redesign, along with an overview of the architecture and the technologies you would use.

I have never dealt with such projects in my career, and I had no clue what to say. I am really curious to know possible approaches from experienced and skilled .NET Developers.

What would be a possible answer to this legacy problem? Click here
  • Blogger Comment
  • Facebook Comment

0 comments:

Post a Comment

The webdev Team