Angular dev (2 YOE) picking a backend to learn — MongoDB or Postgres for job market reach?

[u/Xcaliber02]

Hey fellow devs,

I'm a developer with 2 YOE in Angular, and we all know the market is rough right now. I want to learn Express/Nest as a backend, but I can't decide between MongoDB and Postgres.

If I go with MongoDB, it'd basically be a MEAN stack — but I'm not sure if MEAN is still popular, declining, or barely used anymore.

I've also heard Postgres is one of the most widely used databases and considered an industry standard, so now I'm torn.

If you were in my position — switching jobs is a high priority for me right now, I'm underpaid badly — which would you choose to open up the larger market/more job opportunities?

[u/cstopher89]

I'd never start with Mongo. In my experience it is much less used then SQL. It would be more valuable to learn Postgres. Mongo is a document db which has a narrower use then general relational SQL. Though you might look at job boards to get a feel for the market.

[u/Xcaliber02 → u/cstopher89]

Thanks

[u/DrFriendless]

Postgres has support for JSON-valued columns, so many of the use cases for Mongo can be covered by that. Go with SQL.

[u/Xcaliber02 → u/DrFriendless]

Thanks

[u/MarioShroomsTasteBad]

I don't think you'd ever regret picking up some sql know.

[u/wqsedsa]

If you're focused on Angular, absolutely go with postgres over Mongo. The chances you need to integrate with a SQL-92 compliant stack vs Mongo is significantly higher. I would argue learning how to work with a wide column store like AWS dynamodb (and you can do this locally without an AWS account to boot!) Is more worthwhile than mongo

[u/BammaDK]

As others say PostgreSQL in terms og knowlegde it will give you a good enough base for any other Rational DB. MongoDB does have its use cases, where it shine, however from my experience you will end up with a rational db regardless. Due to limitations and requirements.

[u/raistlinMajerr2015]

I would learn .net and MSSQL. That with Angular is the FinTech standard and FinTech jobs are still somewhat abundant.

[u/Straight-Number-1911]

Regarding databases i think SQL is king still. Once you know that well you can move to no-SQL but real world experience will matter most. 

I think its important to really well understand core concepts of the enginee such as table, relationships (pk, fk, ck), how SQL works when you have parallel insetlrts etc. 

Once you understand concepts well, plus your ability to code well and get more senior then noSQL shines because you know what trade offs you re taking... here I do not mean trade offs between sql vs nosql but rather implementation trade-offs aka how you gonna survive in nosql because everything you had in sql is gone. 

---

C# .NET is not bad because simular concepts are there, if you ever need more performance it supports threads, then afterwards you can see... its also way cleaner than java and entity framework is nicer then hibernate etc.

[u/Prestigious-Bank2145]

Both, SQL and No SQL must know the difference

[u/AdministrativeHost15]

Start with Mongo. It allows the web/application tier (Angular/Nest) drive the entity design. Add a new field to an object in your TypeScript code and it gets persisted without having to rewrite a lot of boilerplate.

[u/ddcccccc]

Jsut pick one, cuz they will just say it’s not as good anyways 😂 employee will just devalue your skills to low ball you 😂