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.
Microservices / Observability / Tools / Sponsored / Contributed
Why New Relic Supports W3C’s Distributed Tracing Protocol
3 Feb 2020 2:51pm, by Jodee Varney
Machine Learning / Microservices / Software Development
This Week in Programming: Forget Microservices, Monoliths Are the Way Forward
1 Feb 2020 6:00am, by Mike Melanson
https://cdn.thenewstack.io/media/2016/01/PodcastBrandingOverlay_TNS_Makers.svg
Microservices / Networking
Distributed Systems and the Butterfly Effect
27 Jan 2020 4:00pm, by B. Cameron Gain and Alex Williams
Cloud Native Ecosystem / Data Science / Microservices
Stateful Data: Couchbase and Its Multiple Consistency Models
20 Jan 2020 11:23am, by Simon Bisson
Microservices / Service Mesh / Sponsored / Contributed
Part 3: The Best Way to Select a Proxy Architecture for Microservices Application Delivery
16 Jan 2020 1:25pm, by Pankaj Gupta
Microservices / Observability / Serverless
Solving Serverless and Tracing Is Key to Success in Observability
14 Jan 2020 12:39pm, by Lawrence E Hecht
Post Malone // Stavernfestivalen // Post Malone // 2018-07-14 20:29:40 // Larvik golfbane, Larvik, Vestfold, Norway (NOR) /
Microservices / Software Development
This Week in Programming: When NOT to Do Microservices
11 Jan 2020 6:00am, by Mike Melanson
https://cdn.thenewstack.io/media/2016/01/Podcasts-Overlay-Context.svg
Microservices / Sponsored
The New Stack Context: Microservices for Dummies
3 Jan 2020 5:00pm, by TNS Staff
Cloud Native Ecosystem / DevOps / Microservices / Sponsored / Contributed
NetApp’s DevOps Struggles and Lessons Learned
3 Jan 2020 6:00am, by Michael Morris
Microservices / Observability
Q&A: Ben Sigelman on the Emergence of “Deep Systems” in Microservices
28 Dec 2019 8:00am, by Kimberley Mok
Data Science / Microservices / Sponsored / Contributed
How Redis Fits with a Microservices Architecture
20 Dec 2019 11:33am, by Loris Cro and Kyle J. Davis
Microservices / Networking / Sponsored / Contributed
Part 2: The Best Way to Select a Proxy Architecture for Microservices Application Delivery
18 Dec 2019 10:48am, by Pankaj Gupta
https://cdn.thenewstack.io/media/2016/01/PodcastBrandingOverlay_TNS_Makers.svg
James Watters and Sina Sojoodi at KubeCon San Diego 2019
Microservices / Sponsored
The Next Movement to Follow Microservices
11 Dec 2019 5:00pm, by Jennifer Riggins
https://cdn.thenewstack.io/media/2016/01/PodcastBrandingOverlay_TNS_Makers.svg
Data Science / Microservices / Sponsored
Gwen Shapira on the Power of Event-Driven Architecture
10 Dec 2019 5:10pm, by Jennifer Riggins
Microservices / Networking / Service Mesh / Sponsored / Contributed
Part 1: The Best Way to Select a Proxy Architecture for Microservices Application Delivery
9 Dec 2019 12:36pm, by Pankaj Gupta
Microservices / Observability / Sponsored
Q&A: Epsagon Brings Automated Distributed Tracing to Microservices, Serverless
27 Nov 2019 2:00pm, by Mike Melanson
Microservices / Security / Technology
Palo Alto Networks to Acquire Aporeto for its Growing Prisma Cloud Native Security Suite
26 Nov 2019 4:26pm, by Joab Jackson
Microservices / Service Mesh / Sponsored
With Gloo Enterprise 1.0, Solo.io Builds the Stepping Stones to Service Mesh
21 Nov 2019 1:29pm, by Jennifer Riggins
Microservices / Service Mesh / Sponsored
Buoyant Launches Dive, a ‘Team Control Plane’ for Microservice Identification
21 Nov 2019 9:00am, by Mike Melanson
Cloud Native Ecosystem / Microservices / Security / Sponsored
SPIFFE/SPIRE Brings Federated Identity to Distributed Architectures
19 Nov 2019 8:00am, by Mike Melanson
CI/CD / Microservices / Sponsored / Contributed
Four Steps to Set Up a CI/CD Pipeline in 20 Minutes
15 Nov 2019 8:04am, by Darby Frey
Microservices / Contributed
Are Your Microservices Overly Chatty?
12 Nov 2019 6:58am, by Amir Souchami
Pods on a beach
Cloud Native Ecosystem / Microservices / Technology
Tutorial: Deploying Microservices to Knative Running on Google Kubernetes Engine
8 Nov 2019 8:06am, by Janakiram MSV
Kubernetes / Microservices / Sponsored / Contributed
Kubernetes Debugging: What Works and What Fails
5 Nov 2019 11:45am, by Or Weis
Cloud Native Ecosystem / Microservices / Contributed
Build or Buy? How to Think About Assembling Software in the Cloud
31 Oct 2019 1:00pm, by Jevon MacDonald
Microservices / Service Mesh
Microsoft’s Open Source Dapr Could Help Developers Build Agnostic Microservice Applications
17 Oct 2019 11:12am, by Mike Melanson
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.