Next-steps scaling up and expanding
Hey guys, so I wanted your opinion and seek some guidance on how to proceed with this issue
For some background, I'm tech lead at this edtech company and we average 5k unique users per day and have been in the field for several years now.
Our current codebase is razzle.js + mui + sass (and other frameworks to get it working), pages vary from landings, dashboards, admin panels, complete authentication pages, and a 'content viewer' thats a major application by itself.
This current version has styles which are on a "whatever works works" basis b/w mui and sass, with components being re used by copy paste and updating rather than making a component and using an instance which also means making changes isn't easy.
For our '23 roadmap, we've got many major additions planned which would literally more than double the complexcity of the whole application (its not small rn either), and I hope to make it as well strucutred, developer friendly and sustainable in the long term as I can. Since building on the current version is possible but as we keep on doing it it'll eventually reach a limit of chaos where it's v v v hard to expand on, a refactor there is months in itself.
So, I want to make it more developer-friendly, consistent (in terms of css/components), for which I am very skeptical about what path to take. We even started a next.js migration a few days back but halted that since it dosen't feel correct and certainly needs more planning.
This is where I need your guidance on how to proceed, and what all things to 'have' and follow as we grow.
48 Replies
Unknown User•2y ago
Message Not Public
Sign In & Join Server To View
(Currently it's mern, we're split into two environments where the frontend is razzle.js/mui/sass and backend is express/mongo/node)
the frontend is what's in a chaotic state
The 'side by side and redo' sounds like the best option now - ie after i decide on the frontend stack
Unknown User•2y ago
Message Not Public
Sign In & Join Server To View
The problem is the amount of code/styles
and I'm skeptical because if we refactor it all just to realize a few months down it wasn't the best choice would be painful
Unknown User•2y ago
Message Not Public
Sign In & Join Server To View
That would be great
Nextjs + tailwind + storybook components sound's like a good idea too
Unknown User•2y ago
Message Not Public
Sign In & Join Server To View
Will keep that in mind
Yeah, rewrites are prolly easier than copy-paste and get it working
Unknown User•2y ago
Message Not Public
Sign In & Join Server To View
😂
but iirc
Shouldnt v13 not break stuff unless you switch to the app directory?
Unknown User•2y ago
Message Not Public
Sign In & Join Server To View
I havent really looked much into the changelist
Our current codebase can't get through its package.json without --force rn anyways, prolly never will 😦
Unknown User•2y ago
Message Not Public
Sign In & Join Server To View
It does-?
Unknown User•2y ago
Message Not Public
Sign In & Join Server To View
ahaha ill stay away from next13 for now 😂
Unknown User•2y ago
Message Not Public
Sign In & Join Server To View
true
Unknown User•2y ago
Message Not Public
Sign In & Join Server To View
I bet that broke everything
Unknown User•2y ago
Message Not Public
Sign In & Join Server To View
hahhaa literally
Unknown User•2y ago
Message Not Public
Sign In & Join Server To View
A lot of libraries out there say we'll only work with 16 or 17 but work so smoothly with 18 too
Unknown User•2y ago
Message Not Public
Sign In & Join Server To View
sucks
Unknown User•2y ago
Message Not Public
Sign In & Join Server To View
The founder (and ig my boss to say) is rushing our 23 roadmap and here I am telling him we wont be able to do anything for a month
I SWEAR ITS SO ANNOYING
Unknown User•2y ago
Message Not Public
Sign In & Join Server To View
Like, gatsby is node 18 as you know and razzle is node 16
Everytime I switch im like nvm use this nvm use that
frustrating
Unknown User•2y ago
Message Not Public
Sign In & Join Server To View
Touche.
Unknown User•2y ago
Message Not Public
Sign In & Join Server To View
And the newest changes every quarter
Unknown User•2y ago
Message Not Public
Sign In & Join Server To View
static html and js?
I would love to but the app currently has 1200 urls in its sitemap and 1100 of them are hierarchy permission protected 😠ðŸ˜
Unknown User•2y ago
Message Not Public
Sign In & Join Server To View
I can't wait for an emp to wipe out all of the worlds tech
Back to the good ol' stone age
Unknown User•2y ago
Message Not Public
Sign In & Join Server To View
ahaha i miss those days
Python + Flask + Bootstrap
Now it's all so messy
Unknown User•2y ago
Message Not Public
Sign In & Join Server To View
well
honestly
HTML webpages will only be a thing for 7th grade in school the way we're progressing
maybe one day students will learn nextjs as cs beginner programs
Unknown User•2y ago
Message Not Public
Sign In & Join Server To View
It's 3.30am -
lets continue this chat tomorrow
Unknown User•2y ago
Message Not Public
Sign In & Join Server To View
idk svelte gives me fucked up jinja vibes
gonna stay away from it
Unknown User•2y ago
Message Not Public
Sign In & Join Server To View
Yessir
200k users and we'll keep the security flows in mind, and yes our whole infrastructure in on aws split on eb, codepipeline, s3 and ec2s
The fact that I've been programming for 4 years now helps me