Microservice is not the silver bullet Software Industry is heavily trend-driven. People love going behind the trendy hypes microservices are cool containers are cool noSQL is cool this new language/framework is cool what makes a good use case for microservice? functionality has very clear demarcation/boundary (the most important.. don’t try to force split an already domain complex module) functionality needs independent scaling functionality needs lot of re-use (many components need it) functionality demands language agnosticity (rapid iterations, deployment) what should you ensure?

Building Technical Sophistication As A Developer Idea and concept wise it’s something we all developers are quite aware of. I first came through this exact term, “technical sophistication” in Michael Hartl’s article in Learn Enough Society. The basic idea is as developer one requires a certain set of skills which can elevate their overall vision and can see things in a broad sight. One need not be technically proficient at everything but having good understanding of fundamentals enables us to debug and reach the solution faster.

Recently I came to know about a wonderful online learning resource called Learn Enough. (https://www.learnenough.com)[Learn Enough] is an initiative by (https://twitter.com/mhartl)[Michael Hartl] who is popular for his highly acclaimed Ruby on Rails tutorials series, which was, at one point, Wikipedia founder (https://en.wikipedia.org/wiki/Jimmy_Wales)[Jimmy Wales]s’ favorite book. I came to know about learn enough through one of the links in StackOverflow answer where I was reading through some answer on UNIX. After going through some of the articles on (unix, git, dev-environment) I was amazed at the simplicity and the narrative way of teaching.