DEV Community

Cover image for Legacy codebase to
Mathias Nilsson
Mathias Nilsson

Posted on

Legacy codebase to

The 27th of November I got a legacy codebase that needed to be maintained. I had never seen the code, but after some poking around in the codebase it was evident that it needed maintenance.

I had just built an app using

and was ready for more.

The app was built using C#, Angularjs, JQuery, FabricJS, chartjs and MySQL as DB. The short version of what the app does is calculating reverberation-time of a room/connected rooms taking into consideration the NRC and absorption of the material in the room. Using graphs and adding material/absorption to the room the app can be used to get close to the RT-60 goal or at least as near as possible.

I dicided to go with, MongoDB (with Prisma), Fabricjs and chartjs and Tailwindcss. The app should live side by side with the original app. I planned to use for deployment.

I literally started with this.

npx create-remix@latest
Enter fullscreen mode Exit fullscreen mode

My plan was to look at the db model, dive into how the old website looked and mimic the functionality and try to improve on user experience.

Show material

I have made rewrites before, but to be honest I never felt this happy with the progress. In a couple of days, I had rewritten the material routes and entity routes. The Graphs were just client side but with useEffect hook I could get them easily to not server render.

My mongodb is located in Sweden using Mongo Atlas. The app was deployed with running in Frankfurt. This is initial load with cache disabled and this kind of load from the database.

export const loader: LoaderFunction = async () => {
  const materials: MaterialPick[] = await db.material.findMany({
    select: {
      id: true,
      name: true,
      absorbtionLevels: true,
      attributes: true,
      absorberClass: true,
      description: true,
      physicalMaterial: {
        select: {
          name: true,
      materialType: {
        select: {
          name: true,
    orderBy: [
        name: "asc",
  return json(
      (material) => {
        const jsonData = material.absorbtionLevels as Prisma.JsonArray;
        const attr = material.attributes as Prisma.JsonArray;
        return {
          absorbtionLevels: => {
            const obj = a as Prisma.JsonObject;
            const absorbtion = obj["absorbtion"] as number;
            const frequency = obj["frequency"] as Frequency;
            return { absorbtion, frequency };
          attributes: attr,
Enter fullscreen mode Exit fullscreen mode

No waterfall

Pretty fast!!

If I could do this all over again and pick whatever stack I wanted, I would never move away from Maybe I could have used PostgreSQL instead since MongoDB with Prisma is beta. The app is a work in progress, but the main bits are in place with a superfast iteration.

Hands down! If you ever needed to rewrite legacy code and you had the luxury to choose for yourself. Give a try and make a POC to see for yourself. It can only be explained by using it.

I'm glad to be a frontend/backend coder again.

Top comments (2)

asadsaleh profile image

Hi Mathias, interesting read!

I'm currently also trying remix to build an app.

If you have the luxury of time, maybe you can help me with 2 things:

  1. How do you integrate chartjs into remix?
  2. How do you you set a component to run only on client side (not in the server)?

Thank you!

aidenberzins profile image
Aiden Berzins

I am working to resolve the same issue. It seems it will have something to do with the ESM modules import.

Use Effect can be used for client side only rendering or you can use the 'remix-utils' package.