Skip to main content

Deals You Can't Miss

1 Year Subscription

10 Myths About Microservices

10 myths about Micro-services, that we often hear to believe it is true.

Micro-services has become a very hot topic in the last half-decade. After Agile, DevOps, its Microservices that we hear everywhere I go. The unfortunate thing that I witnessed though, is that, every organization and every person in that organization has their own definition of what a  Microservice is. Just as the way, Agile and DevOps momentum are abused because of the cult status it achieved, Microservices too seem to have fallen in the same bandwagon.

This post is about recording the top 10 myths that we often hear often about Microservices to believe it is true. And they are:
  1. Microservices is the fancy term for SOA
  2. Managing  Microservices are easier than managing a Monolith
  3. Embrace Microservices so you can avoid XP practices (esp., to hell with TDD)
  4. Micro-services implies developing and deploying an app using a web-framework like Spring-boot.
  5. Microservices are small apps sharing a common DB
  6. Microservices are apps built using certain tools:
    • SpringBoot/DropWizard, Docker and K8 on a Java platform
    • Flask, Docker and K8 on  a Python platform
    • Koa/ExpressJS, Docker and K8 on a Javascript platform
  7. Microservice is a silver bullet to scalable systems
  8. Building microservices FORCES YOU to think about building your apps in a more modular way
  9. Building a Monolith and building Microservices aren't different paradigms
  10. The smartest thing is to start building your systems the Microservice way from the very beginning.
If you believe any of the above myths to be true, you should get your understanding right by grabbing a right book or wait until my next post where I intend to explain these myths.

Do let me know what you think as comments to this post..

My Popular Posts

Ten Commandments of Egoless Programming

We are nothing but the values we carry. All through my life thus far, I tried to influence people around me with the virtues I value. Thanks to some good reading habits I had inculcated, and the fortune of being in good community of peers and mentors alike, I managed to have read some real good books. This post is about the 10 commands of egoless programming in Weinberg's book. I shall explain the commandments based on my experience here. So very many decades ago, Gerald M. Weinberg authored  The Psychology of Computer Programming . In it, he listed The Ten Commandments of  Egoless Programming , which remains relevant even today for us as not just programmers but as team-members. Weinberg is regarded as a pioneer in taking a people-centric approach to computing, and his work endures as a good guide to intelligence, skill, teamwork, and problem-solving power of a developer. When they appear to inspire and instruct, we find that they can apply to just about every business area, and e

Should I buy refurbished laptop from Amazon?

This post is based on my experience with amazon.in and guess it to be true on all other platforms as well. At least you can check out and verify for these pointers before you make that decision to buy renewed/refurbished laptop on Amazon with your hard earned money. I see this question propping up in several forums and on many different occasions. In the recent past, I had my 5 year old dell laptop that gave up because its motherboard failed. One of the options that I had in my mind was to re-use the HDD and the 16GB DDR4 RAM of that old laptop in the one that I purchase next as secondary.  I had come to a conclusion that it is not worth buying a refurbished/renewed laptop at all. Why? For the following reasons, most of which I see as BIG #RedFlags: You got to remember that Amazon provides a platform for 3rd party sellers to sell their products as well. So in your search for refurbished laptops you wouldn’t want to choose some random 3rd party seller who Amazon doesn’t endorse. You cou

Multi-tenant Architectures

  Multi-tenancy Application Deployment Architecture could be modeled in 4 broad ways: Separate Apps & Separate Databases Shared Apps & Shared Databases Separate Apps & Shared Databases Shared Apps & Separate Databases There is no right or wrong here. It's about choice and consequence that you should consider taking into your business context and constraints. In this post I intend to jot down a some key points to keep in mind for each of these multi-tenant architecture. These are more of quick notes for my quick reference, a cheat-sheet of sorts when I have to make choices. And I guess this can come handy to you too in your wise decision making. Separate Apps & Separate Databases Easiest to implement from development and deployment stand-point. Just automate the deployment infrastructure for every tenant for quick set-up. Most expensive of all the models from infrastructure cost stand-point. Relatively longer deployment t