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.
Culture / Microservices / Contributed
How Culture Impacts Technology Choice: A Review of Netflix’s Use of Microservices
25 May 2021 1:41pm, by Itiel Shwartz
Culture / DevOps / Microservices / Sponsored / Contributed
When Will the Microservices Hangover Hit?
25 May 2021 11:00am, by Nočnica Fee
DevOps / Microservices / Sponsored / Contributed
Getting Open Policy Agent Up and Running
11 May 2021 12:00pm, by Anders Eknert
Cloud Services / Microservices / Open Source / Sponsored / Contributed
Unified Event-Driven Architecture for the Cloud Native Enterprise
4 May 2021 8:00am, by Chris Latimer
API Management / Microservices / Sponsored / Contributed
AsyncAPI 2.0: Enabling the Event-Driven World
29 Apr 2021 7:38am, by Shekhar Banerjee
Kubernetes / Microservices / Software Development / Sponsored / Contributed
How Vodafone Greece Built 80 Java Microservices in Quarkus
27 Apr 2021 8:22am, by Alex Handy
Data Science / Microservices / Observability / Sponsored / Contributed
Quickstart to Apache Kafka Stream Processing with ksqlDB
26 Apr 2021 1:37pm, by Michael Drogalis
API Management / DevOps / Microservices / Sponsored / Contributed
Supercharging Event-Driven Integrations using Apache Kafka and TriggerMesh
21 Apr 2021 3:00am, by Sebastien Goasguen
Containers / Microservices / Observability
Thundra Sidekick Expands Microservices Debugging to Python, Kotlin, Scala
15 Apr 2021 3:00am, by B. Cameron Gain
traffic at night
API Management / Microservices / Serverless
AsyncAPI Looks to Unify API Workflow under Linux Foundation
7 Apr 2021 4:00pm, by Mike Melanson
API Management / Microservices / Security / Sponsored
Okta Expands Free Identity Management Services, Cloud Native Deployment Options
6 Apr 2021 4:00pm, by Joab Jackson
DevOps / Microservices / Sponsored / Contributed
Full-Service Ownership: The Key to Unlocking Business and Customer Value
6 Apr 2021 7:43am, by Michael Cucchi
Microservices / Networking / Service Mesh / Contributed
Service Meshes in the Cloud Native World
5 Apr 2021 2:05pm, by Pavan Belagatti
CI/CD / Microservices / Software Development / Sponsored / Contributed
Migration from Monolith to Feature Module
5 Apr 2021 11:00am, by Sangeetha Rao
Kubernetes / Microservices / Service Mesh / Sponsored
Solo.io Offers an Enterprise-Ready Istio Service Mesh as a Cloud Service
23 Mar 2021 9:00am, by B. Cameron Gain
Kubernetes / Microservices / Sponsored / Contributed
Scaling Microservices on Kubernetes
22 Mar 2021 11:00am, by Ashley Davis
Kubernetes / Microservices / Sponsored / Contributed
How Puppet Replatformed Its Fastest-Growing Product to Run Via Kubernetes
17 Mar 2021 7:00am, by Abby Kearns
Cloud Services / Microservices / Contributed
3 Key Factors for Future-Proofing SaaS Cloud Platforms
9 Mar 2021 1:56pm, by Mike Tria
Data Science / Microservices / Serverless
Datastax Astra Offers a Serverless Option for Cassandra
1 Mar 2021 3:00pm, by Mike Melanson
CI/CD / Microservices / Security / Sponsored / Contributed
5 OPA Deployment Performance Models for Microservices
1 Mar 2021 12:59pm, by Anders Eknert
Culture / Microservices / Software Development / Sponsored / Contributed
Why Remote Development Might Be a Better Option Than Local Development
17 Feb 2021 11:00am, by Ismail Egilmez
API Management / Data Science / Microservices / Sponsored / Contributed
A Distributed Application Architecture for a Search Platform
17 Feb 2021 4:00am, by Vikas Singh
API Management / Cloud Native Ecosystem / Microservices / Contributed
Primer: Microservices Explained
16 Feb 2021 10:00am, by Catherine Paganini
Containers / Microservices / Observability
New Relic One Platform ‘Reimagines’ Full Stack Observability
10 Feb 2021 1:25pm, by B. Cameron Gain
Cloud Services / Microservices / Software Development
Thundra Cloud Debugging Platform Supports Java/Spring Hotfix Capabilities
2 Feb 2021 11:59am, by B. Cameron Gain
Microservices / Security / Service Mesh / Sponsored / Contributed
Mutual TLS: Securing Microservices in Service Mesh
1 Feb 2021 7:00am, by Pankaj Gupta
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.