Too often as developers, we end up not having a good baseline estimation of things. There is a lot of things to know about and so many technologies to explore.

Estimating and making accurate judgement is the hardest skill in the world in every field and walk of life.

Every developer wants to make an impact at the global scale but unless you work at FAANG, no way you get an estimate of what is possible and what a small contribution can do at a huge scale.

Enter ipify to the rescue!

ipify serves billions of requests per month and the codebase is so small (can go through it in less than 30 minutes properly) and costs so small to maintain(less than 300$ according to this post), it doesn’t take a lot of effort to make a dent in the universe :)

If I were to take a freshman class, this codebase would be one of the examples I would tell to everyone since I so badly wanted examples like this service to motivate me as to what is possible.

So the problem of making something big? I think comes to working on the right things(it can get random how to make it happen) at the opportune time along with iterating as we go along!!

(Ofcourse, redux-thunk source code is even smaller but takes a lot of context to understand it so we are giving it a pass)

P.S : ipify codebase(as explained in this post) along this course on Pluralsight on heroku deployment can give a perspective on how a backend microservice can be deployed end-to-end as well iterating on the product as time passes by. k8s,docker and elastic beanstalk can sleep meanwhile :)