HackerTrans
TopNewTrendsCommentsPastAskShowJobs

steffan

no profile record

comments

steffan
·il y a 3 mois·discuss
MongoDB | Senior Developer Advocate | REMOTE (Dublin, Ireland) | Full Time

My org is hiring for multiple openings for Senior Developer Advocate roles. We aren't just doing "content." We are the technical "tip of the spear" for MongoDB's largest global accounts.

- The Scale: You'll be solving data architecture and performance bottlenecks at a scale very few engineers ever get to see. - The Impact: It's incredibly rewarding to optimize systems for household-name companies and see the immediate ripple effect. - The Culture: You'll join a tight-knit group of MongoDB experts who actually enjoy collaborating. - The Mix: This is a high-engagement role.

There are multiple open positions:

For significant travel across the UK/Europe (and occasionally Asia) to work face-to-face with devs, balanced with deep-dive technical work. Apply at https://www.mongodb.com/careers/jobs/7241758

For mostly remote, apply at https://www.mongodb.com/careers/jobs/7495485.

If you have 5+ years of experience in consulting/SA/DevRel and want to bypass the recruiter screen, contact Hubert directly: https://www.linkedin.com/in/hubertnguyen/ or message me directly @mongodb.com
steffan
·il y a 6 mois·discuss
This is the equivalent of having the previous 50GB base plan and going over by $50 worth of data (an additional 50GB). If you were routinely going 50GB over the 50GB plan, I'd suggest that maybe a 50GB plan wasn't the right plan for you. Under the old plan, 100GB of data would have cost $100. Residential unlimited is $120, so for most users this would seem like an improvement.
steffan
·il y a 10 mois·discuss
[I work for MongoDB] For your use case, I would consider just holding all of the data in MongoDB. With an appropriate data model, you'd be able to quickly retrieve the information you need for the initial page display as well as article details.

This isn't to say that there aren't use cases that might be better served by either database or a combination, but for your particular use, you may not be gaining enough to offset the added complexity of using two different databases.

Obv. I'm biased, but I would recommend using MongoDB :)

Here's a reference for some design patterns to consider: https://www.mongodb.com/company/blog/building-with-patterns-...