CIOIT Best PracticesIT GovernanceRisk Management

5 Misconceptions about Microservices

New concepts come with new misunderstandings. Microservices are suddenly the new hot topic of conversation in IT, and because they are so new, not a lot of people actually “get” them yet. So to help clear the air, Kevin Casey identifies and corrects five misconceptions of microservices in an article for the Enterprisers Project:

  1. Microservices are basically a repeat of service-oriented architecture (SOA).
  2. Microservices eliminate complexity.
  3. Microservices have rigid implementation requirements.
  4. Microservices and APIs are the same thing.
  5. Microservices suit every application.

Little Mistakes

Microservices perform a single process each and may be combined in a modular way, resulting in software that can perform the same work as monolithic applications but with more versatility. Although some aspects of that may inspire flashbacks to SOA, there is a key difference:

SOA never delivered a radical new level of of speed. “Although the idea of modularity has been around for years, microservices architecture brings much more flexibility through the independence of services, enabling organizations to become more agile in how they deliver new services or respond to changing market conditions,” says Rich Sharples, Senior Director of Product Management, Red Hat.

Microservices and APIs are not the same thing either. Whereas APIs “specify how software components should interact,” microservices are more about providing efficient implementation solutions that are scaling-ready.

That being said, microservices only make complexity more manageable; they do not get rid of it altogether. In fact, a lousy microservice will just slow down the network. Casey further suggests that a DevOps approach is almost mandatory to succeeding with a microservices architecture. But on the bright side, microservices are applicable to a wide variety of hybrid environments, contrary to what some might expect.

The last thing to remember about microservices is that they do not need to be applied to every possible situation. Just like a business can go overboard automating tasks without an adequate ROI, a business can also go overboard introducing microservices without just cause. Common sense must always reign.

For additional insights, you can view the original article here:

Show More
Back to top button

We use cookies on our website

We use cookies to give you the best user experience. Please confirm, if you accept our tracking cookies. You can also decline the tracking, so you can continue to visit our website without any data sent to third party services.