All About Microservices
All About Microservices
A great primer on the what and why of microservices, this collection of DZone articles is a great place to get started or grow your knowledge.
Join the DZone community and get the full member experience.Join For Free
Need to learn the basics of microservices or need a refresher? If so, this article will be a great resource for you. Here, I’ve gathered five of the best articles about microservices on DZone so you can learn the basics and more. Different explanations can be helpful because sometimes one isn’t enough to clearly understand a topic. So, let’s jump into it.
1. “The Truth About Microservices” by Brian J. Atkission
“Microservices are a method of breaking down an application into a suite of small, lightweight services, and are processes that typically communicate over HTTP. Building a single microservice is easy, building a microservice architecture is extremely hard.”
DZoner Brian Attkisson provides an excellent paraphrase of John Frizelle’s talk on microservices where he explains where and why (or why not) you should deploy them. He also breakdowns the many challenges you will face when building a microservice architecture and suggests when you should consider transitioning to microservices.
2. “Why Microservices?” by Shamik Mitra
Many people have the wrong idea about microservices. Microservices aren't telling you to break your project down based on the tier, such as JMS, UI, logging, etc. No this is absolutely not. We need to break it down by function. A complete function and its functionality may consist of UI, business, logging, JMS, data access, JNDI lookup service, etc.
Before jumping into microservices, DZoner Shamik Mitra explains the traditional three-tier architecture (presentation layer, business layer, and data access layer) of monolithic software. This allows Mitra to explain the problems that typically occur when with monolithic software and how microservices solves those problems. This isn’t to say that Microservices don’t have their own shortcomings, which Mitra explains as well.
3. “Microservices Architecture: What, When, and How” by Mrityunjay Kumar
In short, Microservices architectural style defines a setup, where application components are standalone applications of their own. These independent application components talk to each other either using RMI (Remote Method Invocation), Restful Web Services or Push Messaging.
Mrityunjay Kumar uses the Gartner hype cycle model to show how microservices are at the peak of inflated expectations. Despite the possibly overexaggerated hype, Kumar does an amazing job explaining the reasonings for this hype and gives us reasons for why we should be excited as well. It’s also a great article that covers the basics of microservices: what it is, when it should be used, and how it should be used.
4. “What Are Microservices, Actually?” by Kristijan Arsov
“The goal of microservices is to ease the building, maintaining and managing of an application by breaking it down into smaller, composeable pieces which work together and can be independently deployed, upgraded, removed or scaled whenever the need arises.”
Somehow, DZoner Kristijan Arsov finds an amazing way to use spaghetti, pie, and doughnuts to explain monolithic and microservice architecture. He also makes an interesting point on how microservices brings us closer to the era of DevOps, where cross-functional teams work closer together.
5. “Introduction to Microservices: Part 1” by Chris Richardson
“Building complex applications is inherently difficult. A Monolithic architecture only makes sense for simple, lightweight applications. You will end up in a world of pain if you use it for complex applications. The Microservices architecture pattern is the better choice for complex, evolving applications despite the drawbacks and implementation challenges.”
Grab your reading glasses because DZoner Chris Richardson is about to teach you everything about Microservices. Don’t let the length of this read intimidate you, if there is anything you didn’t know about Microservices before, you will now.
As you can see, a lot of the same points are covered, but a lot of new explanations and thoughts about microservices are uncovered as well. Microservices may be an overhyped concept, but it’s exciting to think about the ways they can change the industry regardless.
Opinions expressed by DZone contributors are their own.