This message was imported from the Ruby/Rails Modularity Slack server. Find more info in the import thread.
Message originally sent by slack user U72HFS2TEFJ
q: how many lines of code makes an “extra large” monolith?
This message was imported from the Ruby/Rails Modularity Slack server. Find more info in the import thread.
Message originally sent by slack user U72HFS2TEFJ
q: how many lines of code makes an “extra large” monolith?
Message originally sent by slack user U70K2MT6OHQ
Tough question to answer. What does it mean to be “extra large”? What are you trying to convey by knowing the answer to this?
Message originally sent by slack user U717GMJTWHJ
It is tough. It’s kind of a “you know it when you see it” thing, but when you’ve got not dozens of models, but dozens of domain concepts and some of them are pretty mature, then you’re there.
Message originally sent by slack user U717GMJTWHJ
Like, I thought a previous app I worked on was huge with a few hundred models, then I started at gusto and there were a few hundred packs/components.
Message originally sent by slack user U72HFS2TEFJ
mostly just trying to get a sense of where i’m at relative to gusto I think. saw this note on the packs README at https://github.com/alexevanczuk/packs
Currently can serve as a drop-in replacement on Gusto's extra-large Rails monolith
Message originally sent by slack user U72HFS2TEFJ
I think w/ more research I found posts suggesting that gusto is managing ~4mil loc
Message originally sent by slack user U72HFS2TEFJ
so yea, i’m in the same ballpark. packs
looks interesting, might give it a whirl on our repo
Awesome <@U72HFS2TEFJ>! Would love to hear your feedback That 4M number is a bit outdated – I believe we’re at least 50% larger now. I’ll see if we have a public number I can use to improve the clarity of the language and help folks compare/gauge more easily.
Message originally sent by slack user U72HFS2TEFJ