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 develop, deploy, and scale their respective services independently. This enablement gives room for 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 the use of DevOps, continuous integration, continuous delivery (CI/CD), and containers. There will be no need to deploy code all at once as developers do in a monolithic environment. This feature makes updates frequent and fast, enabling CI/CD.

The Need for Microservices Orchestration
Microservices orchestration manages complex processes in products 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 in which 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 the development process.
Scalability. Unlike monolithic applications requiring multiple instances for every component, microservices allow teams to scale a part of an application independently, according to the resource the component needs.

Challenges with Microservices
Microservices have many advantages, but migrating away from a monolith introduces its own set of challenges.

Here are some drawbacks of using a microservice architecture:

Complexity. With a microservices architecture, service discovery, networking, testing, and monitoring all 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 exact 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 market 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 scale just as well and remains the best option in many scenarios.

Many business and process decisions are involved in transitioning to a microservices-based architecture. Still, there are 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.


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.
Robert Barron, having built his own miniature version of the james webb space telescope, showing how the honeycomb hexagon mirrors fold
DevOps / Microservices / Observability
James Webb Space Telescope and 344 Single Points of Failure
21 May 2022 5:00am, by Jennifer Riggins
Iterative SRE Transformation with photos of the speaker
CI/CD / Microservices / Observability
Vanguard’s Iterative Enterprise SRE Transformation
17 May 2022 2:00am, by Jennifer Riggins
Compliance / Kubernetes / Microservices / Technology / Sponsored / Contributed
The Kubernetes Manifest Life Cycle Too Often Overlooked
11 May 2022 7:34am, by Christian Lete
Microservices / Contributed
What Is a Microservice Catalog and Why Do You Need One?
10 May 2022 10:00am, by Erik Lindblom
Cloud Services / Data / Microservices
Confluent Adds Tighter RBAC, Grafana and Other Features
5 May 2022 6:50am, by B. Cameron Gain
Cloud Native Ecosystem / Microservices / Sponsored / Contributed
Embracing Testing in Production
2 May 2022 9:22am, by Matt Casperson
Microservices / Security / Software Development / Sponsored / Contributed
3 Ways Developers Can Boost Cloud Native Security 
11 Apr 2022 8:38am, by Tim Hinrichs
An overhead photo of a twisty road that runs through a green, wooded landscape.
Microservices / Security / Software Development / Technology / Sponsored
How to Build a Roadmap to App Modernization
8 Apr 2022 6:00am, by Jennifer Riggins
Microservices / Storage / Technology
Redis Puts (Almost) Everything Under a Single Module
7 Apr 2022 9:41am, by B. Cameron Gain
Kubernetes / Microservices / Tools
Chaos Engineering Was Missing from Harness’ CI/CD Before ChaosNative Purchase
29 Mar 2022 3:00am, by B. Cameron Gain
API Management / Microservices / Sponsored / Contributed
Why GraphQL for Microservices?
14 Mar 2022 6:22am, by Roy Derks
highway traffic at night
API Management / Containers / Kubernetes / Microservices / Observability
Open Source Mizu Unblocks View into Kubernetes API Traffic
1 Mar 2022 12:20pm, by Susan Hall
API Management / Compliance / Microservices / Technology / Sponsored / Contributed
Automated SBOM Generation with Paketo Buildpacks
28 Jan 2022 6:18am, by Ram Iyengar
Kubernetes / Microservices / Software Development / Technology / Sponsored / Contributed
Kubernetes DaemonSets: A Detailed Introductory Tutorial
26 Jan 2022 8:11am, by Dawid Ziolkowski
API Management / Microservices / Technology / Contributed
Lessons Learned Implementing a CMS Microfrontend
11 Jan 2022 10:00am, by Abhinav Paliwal
data
Data Science / Kubernetes / Microservices / Sponsored / Contributed
New Tools for Optimizing Data Resilience in Kubernetes
6 Jan 2022 9:00am, by Marcel Hergaarden
2022
DevOps / Microservices / Security / Sponsored / Contributed
What SecOps Teams Can Expect in 2022
22 Dec 2021 6:40am, by Faith Kilonzi
seconds
DevOps / Machine Learning / Microservices / Sponsored / Contributed
When Seconds Matter: Harnessing Real-Time Digital Operations
3 Dec 2021 10:34am, by Vivian Chan
Cloud Native Ecosystem / IoT Edge Computing / Microservices / Contributed
Apache Pulsar: A Unified Queueing and Streaming Platform
10 Nov 2021 6:00am, by Addison Higham
Ali Siddiqui, chief product offcer of BMC Software
Data Science / Machine Learning / Microservices / Sponsored
How StreamWeaver Supports BMC’s Updated Vision
3 Nov 2021 10:46am, by B. Cameron Gain
API Management / Microservices / Software Development / Contributed
The Rise of Event-Driven Architecture 
28 Oct 2021 10:00am, by Matthew O’Riordan
Cloud Native Ecosystem / Containers / Microservices
vFunction Guides Enterprises Toward Continuous Modernization
26 Oct 2021 5:00am, by Mike Melanson
Culture / DevOps / Microservices
Target Embraces Cross-Organizational DevOps Culture
15 Oct 2021 5:00am, by Jennifer Riggins
DevOps / Microservices / Security / Sponsored / Contributed
Microservices Transformed DevOps — Why Security Is Next
8 Oct 2021 8:00am, by Tim Hinrichs
API Management / Microservices / Software Development
AppWrite: A Cloud Native Backend-as-a-Service
7 Oct 2021 11:09am, by Mike Melanson
Kubernetes / Microservices / Software Development
Hadean’s Rust SDK Promises ‘Friction Free’ Cloud Native Computing
23 Sep 2021 4:00am, by Mike Melanson
Pagination Previous Button
1 2 3 4 5 6 7 8 9 10
11 12 13 14 15 16 17 18 19 20
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.