30

Guys guys guys. Conversation had right just now. A PM from the company I’m freelancing for just said

“We need to move away from SQL server and shift all the data to MongoDB. I don’t want it to take more than a month tops”

Verbatim. No context. Nothing. The website is for a small time supply chain software that’s been chugging along for a decade now with spaghetti code everywhere.

How do I even respond? The other guy who works with me sent πŸ˜‚πŸ˜‚πŸ˜‚ to me privately and now is offline lol wtf

Comments
  • 27
    "The system is tied down to the current infrastructure like an anchor to a ship"

    We will have to redesign the ship to move that anchor.
  • 11
    Really is this Mongo so trendy? It's a f*****g json. How can it be faster?
  • 24
    @davide devs find relationships hard.
  • 4
    We are thinking about dropping this project. This PM has been a pain in the ass for a while and this might be the last straw.
  • 6
    @davide it’s so hip it’s so nosql reeeeeeeeeeeee
  • 2
    @davide Oooh! Shiny!

    That's it.
  • 2
    @C0D4 "devs find relationships hard."

    ooh, i see what you did there
  • 3
    @C0D4 you made my day πŸ˜‚πŸ˜‚πŸ˜‚
  • 2
    @webdev am I wrong though?

    @davide I'm glad someone got it😁
  • 1
    @davide It depends on utilization.
    I find CosmosDB (Or monfoDB, same shit) very suitable for something like User Preferences.

    Because you don’t care about each individual preference, usually you want them all for a user. This also allows to add new user settings on the fly.

    Yes, you can create a table SQL with user id and JSON second column containing same thing. But mongo/cosmos offers some more flexibility. Ex : Get all users, having access to feature X and have value Y for threshold of feature Z.

    Ex of usage : Custom notifications. “Get all users, who activate this notification option with these parameters”.

    (Yes, I’m aware you can parse JSON in SQL server, but I still prefer Cosmos for these type of things)

    But for raw data, I still prefer SQL, especially if it has more than 10000 lines.
  • 1
    @NoToJavaScript Great explication, thanks!
  • 1
    @davide In benchmarks I've done with loads of inserts and selects, mongo was definitely faster!
Add Comment