SEARCH (ENTER TO SEE ALL RESULTS)
Cancel Search
POPULAR TOPICS
Contributed
sponsored-post-contributed
News
Analysis
The New Stack Makers
Tutorial
Podcast
Feature
Research
Profile
The New Stack Logo
Skip to content
  • Podcasts
  • Events
  • Ebooks
    • DevOps
    • DevSecOps
    • Docker Ecosystem
    • Kubernetes Ecosystem
    • Microservices
    • Observability
    • Security
    • Serverless
    • Storage
    • All Ebooks
  • Newsletter
  • Sponsorship
  • • • •
    • Podcasts
      • TNS @Scale Series
      • TNS Analysts Round Table
      • TNS Context Weekly News
      • TNS Makers Interviews
      • All Podcasts
    • Events
    • Ebooks
      • DevOps
      • DevSecOps
      • Docker Ecosystem
      • Kubernetes Ecosystem
      • Microservices
      • Observability
      • Security
      • Serverless
      • Storage
      • All Ebooks
    • Newsletter
    • Sponsorship
Skip to content
  • Architecture
    • Cloud Native
    • Containers
    • Edge/IoT
    • Microservices
    • Networking
    • Serverless
    • Storage
  • Development
    • Development
    • Cloud Services
    • Data
    • Machine Learning
    • Security
  • Operations
    • CI/CD
    • Culture
    • DevOps
    • Kubernetes
    • Monitoring
    • Service Mesh
    • Tools
Search The New Stack
 

Microservices

▾ 4 MINUTE READ — CLOSE

Application development greatly benefits from the growing popularity of microservices — a technique that involves a group of loosely coupled services. Netflix and Amazon are part of the early pioneers of microservices.

What Are Microservices?

Microservices are an architectural approach to software development based on building an application as a collection of small services. There is no standard definition for what amount of code constitutes a “small service.” Some experts say it’s about the size at which a team can query the service’s health with a single request that returns a “yes” or “no” answer. Similarly, a service is too big if it requires more than one team to manage it.

Each service has its unique and well-defined role, runs its process, and communicates via HTTP APIs or messaging. Teams can deploy, upgrade, scale, and restart each microservice independent of all the sibling services in the application. These microservices are typically orchestrated by an automated system, making it possible to have frequent updates of live applications without affecting the end-users.

Benefits of the Microservices Framework

Microservices are an evolution of a service-oriented architecture (SOA) — and some would argue that microservices are just SOA rebranded to make it hip again. Cloud-native microservices take the SOA concept to a new level, though. The difference now is that cloud infrastructure has finally caught up to the SOA concept so that loosely-coupled services (aka microservices) are now feasible to implement and manage at scale.

Here are some benefits of microservices architecture:

Enabling independent development. Microservices architecture enables small autonomous teams to independently develop, deploy, and scale their respective services. This enablement allows more developers to work on smaller codebases, lightening the workload.

Increasing development speed. Microservices parallelize development, thereby speeding up the production cycle exponentially.

Promoting continuous delivery. The adoption of microservices facilitates using DevOps, continuous integration, continuous delivery (CI/CD), and containers. There will be no need to deploy code simultaneously as developers do in a monolithic environment. This feature makes updates frequent and fast, enabling CI/CD.

Discover the Ten Commandments of Microservices

The Need for Microservices Orchestration

Microservices orchestration manages complex production processes to enable developers to operationalize containers at scale. Orchestration coordinates workload management, communication, and microservices architecture readability. Microservices orchestration ensures that there is no data loss in the process of coordination. This capability eases system development for developers and enables support teams to fix problems quickly.

Several microservices orchestration solutions are available in the market. Here are some factors to consider when deciding on an orchestrator for your microservices:

Multiplatform integration. All teams should be able to use the orchestrator at once. For example, the tool should support teams using an open-source developer platform and object programming languages.

Ease of use. Ideally, the orchestrator has a simple environment where the microservice interaction is easily visible.

Error processing. A microservices orchestrator allows developers to set up multiple retries and timeouts when a malfunction occurs.

Non-synchronized workflow support. During development, some workflows run parallelly and may not be simultaneous. An orchestrator should save current data, stabilize general performance, and simplify development.

Scalability. Unlike monolithic applications requiring multiple instances for every component, microservices allow teams to scale a part of an application independently, according to the component’s resource needs.

Challenges with Microservices

Microservices have many advantages, but migrating away from a monolith introduces challenges.

Here are some drawbacks of using a microservice architecture:

Complexity. With a microservices architecture, service discovery, networking, testing, and monitoring become more complex and difficult, if not impossible, to manage following reliable older systems and practices. And the problem is amplified as the number of services grows.

Excess Resource Consumption. Tools that once seemed essential, such as logging, are now racking up huge bills that can send a microservices migration into negative return on investment (ROI) territory. Although microservices support the efficient use of resources, they can also increase resource consumption as services grow. Each microservice would need its own container and instance, which may increase the CPU and storage use.

Routing Microservices. In a traditional microservices approach, teams run only the small services they need and nothing else. It’s a sleek setup, but these services are not aware of each other until you step in to orchestrate them. Orchestrating services requires time and resources beyond the engineering reach of many small to midsize organizations.

Relationship between Microservices and Containers

A microservice architecture splits applications into different services that perform specific functions. Each microservice has a unique logical function for each part of a monolithic application.

Containers are packages that contain microservices. These containers also house code, dependencies, binaries, and libraries. Container-based — and open source — systems like Docker and Kubernetes are a very effective way to develop, deploy, and manage microservices in an enterprise environment. Many mature and robust tools, platforms, and other services exist in the container space, rendering containerization a natural fit for microservices-based applications.

Why Organizations Are Embracing Microservices Solutions

A leap forward is now happening with microservices. There is a virtual tech sector land rush on, with companies feverishly producing not just microservices themselves but also the platforms, tools, and frameworks necessary for joining them together.

Keep up with Microservices Developments on The New Stack

It can be difficult to gauge both best fit and ultimate longevity at this stage in the developing ecosystem around microservices. Despite the abundant potential benefits, microservices are not the right solution for every project. A well-built monolithic architecture can also scale and remains the best option in many scenarios.

Many business and process decisions are involved in transitioning to a microservices-based architecture. Still, many companies for which microservices are the best option and well worth the immediate challenge.

At The New Stack, we monitor microservice architecture developments, new orchestration tools, and microservices frameworks. Be sure to bookmark this page to read the latest articles on microservices.

Discover more about microservices:

Microservices 101

The Future of Microservices? More Abstractions

Primer: Microservices Explained


The New Stack Newsletter Sign-Up
A newsletter digest of the week’s most important stories & analyses.
Do you also want to be notified of the following?
We don’t sell or share your email. By continuing, you agree to our Terms of Use and Privacy Policy.
Microservices / Software Development / Sponsored / Contributed
Monoliths to Microservices: An API-First Approach
29 Apr 2020 9:22am, by James Burns
Microservices / Observability / Contributed
6 Things to Consider in a Prometheus Monitoring Platform
27 Apr 2020 1:40pm, by Loris Degioanni
Microservices / Observability / Software Development / Sponsored / Contributed
The Importance of Resilience Testing and Observability
20 Apr 2020 9:36am, by James Burns
CI/CD / Cloud Native Ecosystem / Microservices / Contributed
Map Your Journey to Monolith Modernization
14 Apr 2020 1:36pm, by Derek Magill
Cloud Native Ecosystem / Kubernetes / Microservices / Sponsored / Contributed
Elements of Cloud Native Business Automation
13 Apr 2020 8:18am, by Balakrishnan Balasubramanian
Microservices / Observability / Service Mesh / Sponsored / Contributed
Observability: From Service Discovery to Service Mesh
10 Apr 2020 10:04am, by Peter McCarron
DevOps Tools / Microservices / Sponsored / Contributed
TARS Microservices Extended to the ARM Architecture
9 Apr 2020 11:33am, by Katharine Wong
Microservices / Observability / Software Development / Sponsored / Contributed
Why Observability Is Crucial for Developers
9 Apr 2020 8:38am, by Karthik Kumar
Microservices / Networking / Service Mesh / Contributed
Istio 1.5 Brings Advanced Automation for Secure Performance
8 Apr 2020 3:00am, by Karen Bruner
Cloud Native Ecosystem / Microservices / Observability
Cortex 1.0 Offers ‘Enterprise-Ready’ Distributed Prometheus Monitoring
6 Apr 2020 1:50pm, by Mike Melanson
balance
DevOps / Microservices / Service Mesh / Sponsored / Contributed
Agility with Stability: Why You Need a Service Mesh
3 Apr 2020 8:21am, by Randy Almond
Microservices / Observability
Lightstep: Pay for the Observability, Not Just the Telemetry
2 Apr 2020 9:15am, by Joab Jackson
https://cdn.thenewstack.io/media/2016/01/PodcastBrandingOverlay_TNS_Makers.svg
Microservices / Observability / Sponsored
The 3 Pillars of Observability
2 Apr 2020 9:00am, by Alex Williams and B. Cameron Gain
DevOps / Microservices / Service Mesh
An Exploratory Guide to the Service Mesh Platforms
31 Mar 2020 7:45am, by Janakiram MSV
https://cdn.thenewstack.io/media/2016/01/PodcastBrandingOverlay_TNS_Makers.svg
Cloud Services / Containers / Microservices
What COVID-19 Means for Microservices, Multicloud and Kubernetes
30 Mar 2020 4:01pm, by B. Cameron Gain and Alex Williams
https://cdn.thenewstack.io/media/2016/01/Podcasts-Overlay-Context.svg
Microservices
Kelsey Hightower and Ben Sigelman Debate Microservices vs. Monoliths
27 Mar 2020 5:00pm, by TNS Staff
DevOps / Microservices / Service Mesh / Sponsored / Contributed
The Importance of Uptime and Efficiency in the Application Economy
27 Mar 2020 8:02am, by Zach Jory
https://cdn.thenewstack.io/media/2016/01/PodcastBrandingOverlay_TNS_Makers.svg
Microservices / Service Mesh
Why an IBM ‘Master Inventor’ Calls Istio Service Meshes ‘Storage Boxes’
26 Mar 2020 1:57pm, by Alex Williams and B. Cameron Gain
Cloud Native Ecosystem / Kubernetes / Microservices / Sponsored / Contributed
How Persistent Storage Offers Cloud Native Developers More Freedom
18 Mar 2020 8:03am, by Michael St-Jean
Cloud Native Ecosystem / DevOps / Microservices / Networking
Stateless Rethinks Modern Networking
16 Mar 2020 11:25am, by Susan Hall
https://cdn.thenewstack.io/media/2016/01/PodcastBrandingOverlay_TNS_Analysts.svg
Kubernetes / Microservices / Service Mesh
What the Numbers Say about How Service Meshes Are Used Today 
13 Mar 2020 8:04am, by Alex Williams and B. Cameron Gain
Kubernetes / Microservices / Storage
How OpenEBS Brings Container Attached Storage to Kubernetes
6 Mar 2020 9:42am, by Janakiram MSV
Kubernetes / Microservices / Service Mesh / Sponsored / Contributed
When You Do (and Don’t) Need a Service Mesh
26 Feb 2020 1:45pm, by Andrew Jenkins
Microservices / Software Development / Contributed
Event Sourcing Design with Amazon Web Services
25 Feb 2020 6:00am, by Paul Bourdel
Kubernetes / Microservices / Software Development
Tutorial: First Look at Dapr for Microservices Running in Kubernetes
14 Feb 2020 9:39am, by Janakiram MSV
Microservices / Networking / Service Mesh
How Much Will App Services Like Service Mesh Grow?
13 Feb 2020 7:20am, by Lawrence E Hecht
Pagination Previous Button
1 2 3 4 5 6 7 8 9 10
Pagination Next Button
Architecture
  • Cloud Native
  • Containers
  • Edge/IoT
  • Microservices
  • Networking
  • Serverless
  • Storage
Development
  • Cloud Services
  • Data
  • Development
  • Machine Learning
  • Security
Operations
  • CI/CD
  • Culture
  • DevOps
  • Kubernetes
  • Monitoring
  • Service Mesh
  • Tools
The New Stack
  • Ebooks
  • Podcasts
  • Events
  • Newsletter
  • About / Contact
  • Sponsors
  • Sponsorship
  • Disclosures
  • Contributions

© 2022 The New Stack. All rights reserved.

Privacy Policy. Terms of Use.