On the other hand I sometimes wonder why Calculus is made a big deal out of. It was probably the easiest among all the parts of maths. You just have to imagine an small unit and how to extrapolate for integration and imagine how to break it down to small parts for differentiation. When I originally learnt Calculus in high school it was couple of days of learning the concepts and the a week of deriving everything from that and move on!
Thanks for sharing this insight. Is this a issue with just the web server.
If I have a standalone task, which tires to use 128 cores and manages parallel tasks using goroutines communicating via channels - will I be able to successfully leverage 128 cores.
With such drastic diet - gastric system goes for a toss. You don't want to wait that long between pooping. One option is to try buffered vitamin c. It was definitely give you a poop whenever you want without side effect and dependency.
I agree with this. Most people need just 2 years during grade 11 and 12. Starting earlier might give minor edge at best but more damage to other aspects of personality and growth!
In IIT, in under 1000 rank, most people who spent more than 2 years were people who were intelligent but didn't take preparation seriously during their grade 11-12 but put in effort after that.
I also know people who were extremely intelligent who could crack under 100 if they gave the exam in grade 8. But they were outliers.
There were many questions asking about recent experience with MongoDB. I have some recent experience so wanted to share with everyone.
My background:
2007-2010: Used MySQL to run a social network for 50M+ users. Would send 2B messages on peak days. All powered by Mysql.
2015-2020: Used Mongo to power a top 5k site. Zero downtime and dataloss in 5 years. Used Postgres for internal non user facing database
So I have familiarity with all of these databases at a decent scale. I am going to list pros and cons of each and why I would use. Again a tool is a tool. Just because I love a wrench, doesn't mean that I am going to use it instead of a hammer when I need to put some nails.
MongoDB:
They have come a long way since I started using them in 2012. If your use case is CRUD, you would be fine. There is still a lot of marketing fluff about sharding, multi document transactions etc which might not be fully reliable. I stay away from those things. But if you just use CRUD and you data can fit in a single db you are going to be fine at decent scale.
Following are some reasons I prefer Mongodb. It's possible that Postgres/MySQL has some of them even though I couldn't find them:
1. I don't like to manage schema migrations. During development you constantly add columns and it's a pain to make sure that this column is added to the sql databases on development, testing, staging, prod etc. With mongo, you just add a column and you are done.
2. No downtime on migrations: You can change you server type or mongo version with zero downtime. Did that since 6 years. Couldn't figure out how to do that with postgres (even with Aurora).
3. If you data structure fits document and subdocument schema, mongo is really easy to use. I tried jsonb with postgres and didn't find it as easy to use at mongo. If you data fits this paradigm, you can essentially get atomicity for multiple updates because they are all in a single document.
4. The admin interface of MongoDB Atlas is really development friendly. You can easily add read only replicas. You can easily add replicas in different regions. I shudder at the thought of managing Postgres myself and even Amazon Aurora is not as easy to admin as Atlas.
At this point I would consider Postgres only in the following case:
If my data structure is like a non-tree graph. In that case I would expect to do multiple complex join and expect transaction consistency between tables.
If I am building a financial product which directly handles money or money instruments (bank, stock trading) I would definitely not use mongo for that.