I joined FB 1.5 years ago and having a hard time as a front end engineer. I’m not a big fan of how things work with graphql, react, hack, etc. The stack is a mess, logic everywhere between frontend and backend, untraceable calls due js-minimizing in obscure ways. I was at a tiny startup before. Paid 🥜, but I loved the simplicity of writing straightforward nodejs code, integrate with mongoose and just query mongodb json objects. If I even say the word MongoDB the seniors look weird at me and ignore me. I wrote a post about my experience above and it got no reactions at all 😢. I have seen a much nicer way of doing things, but my team doesn’t even want to look. Setting up a mongodb in FB infra looks really hard to do as well, so I can’t prototype a release. The internal group of mongodb users seems to have gone silent since 2013-2014. Dear blind, what do I do? IC3 YoE: 2.5 TC: 340k
mongodb is webscale
If you want things your way you have to join a small startup where you have more say. Usually in big companies, things aren't done as straightforward as you would want them to. Even though there may be an obvious Better solution.
I’d love to move a startup, but with stock appreciation recently I will lose a lot of TC. Plus FB brand looks good on my resume
How should we convince you that MongoDB isn’t that great beyond the small startups? Though, your senior engs suck because I would expect them to discuss with you the pros and cons instead of giving you a weird look.
care to share what persistent data stores to consider for huge transactional data storage and/or document db
DynamoDB with Redis cache for transactions, S3 with CloudFront cache for files.
troll post
why?
how the fuck an IC3 gets 340k without promo
You get 340k to deal with it…
You focus on the problem and get consensus on that before proposing a solution. Not go around begging for people to let you use MongoDB…
Simple answer: You don’t. More often than not things were done certain way for a reason and you may not be aware of that reason or the reason may no longer be valid but change would be too costly or risky.
It sounds like what you really want is an orm in front of a nosql dB, not necessarily Mongodb
we have graphql for that I think, but it makes it harder and not easier
OP you really don't seem to know what you're talking about. Graphql is not an ORM, and further Facebook does have an ORM, so it makes no sense to bring up graphql as being FB's ORM.
I am not an swe. I work at fb on the business side and this problem is rampant at fb on other areas too. Fb has a way of doing things and any deviation from the norm/mean is looked down upon. It’s bad. I’ve seen people push for change and realize that things won’t change. You can’t change the system. So they quit. So your choices are, you adapt or your walk.
What are some examples of this on the business side?
exactly! People in many cases won’t even hear you out or look at your demo. They just dismiss based on ‘nobody uses MongoDB’ without trying. Need to focus on impact in the short term
MongoDB sucks
It’s really great actually. So much easier than sql and performs so much better.
If you don't know any SQL, sure.