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.
Cloud Native Ecosystem / Kubernetes / Microservices
Telekube Offers Remotely-Managed ‘Private SaaS’ Kubernetes
23 Nov 2016 7:29am, by Susan Hall
API Management / CI/CD / Cloud Native Ecosystem / Containers / Data Science / DevOps / Kubernetes / Microservices / Software Development / Contributed
Cloud Native: Service-driven Operations that Save Money, Increase IT Flexibility
17 Nov 2016 7:53am, by Craig McLuckie
Cloud Native Ecosystem / Containers / Kubernetes / Microservices / Observability
Weaveworks Knits Networking, Prometheus Monitoring into a Cloud-Native Service, Weave Cloud
17 Nov 2016 6:50am, by Susan Hall
https://cdn.thenewstack.io/media/2016/01/PodcastBrandingOverlay_TNS_Makers.svg
API Management / Cloud Native Ecosystem / Cloud Services / Containers / DevOps / Kubernetes / Microservices
Create At-Scale Cloud Native Deployments with HPE and OpenStack
14 Nov 2016 9:21am, by Kiran Oliver
Cloud Native Ecosystem / Microservices / Contributed
The Reality of Microservices in the Enterprise
9 Nov 2016 9:37am, by Jonah Kowall
API Management / Cloud Native Ecosystem / Cloud Services / Containers / Data Science / Kubernetes / Microservices / Security / Sponsored
Kubernetes: An Overview
7 Nov 2016 10:00pm, by Janakiram MSV
https://cdn.thenewstack.io/media/2016/01/PodcastBrandingOverlay_TNS_Makers.svg
Cloud Native Ecosystem / Microservices / Sponsored
NGINX, an Open Source Web Server for Microservice Architectures
7 Nov 2016 10:01am, by Kiran Oliver
Cloud Native Ecosystem / Data Science / Machine Learning / Microservices
The Enterprise of the Future Will Need Connected Big Data
7 Nov 2016 7:34am, by TC Currie
https://cdn.thenewstack.io/media/2016/01/PodcastBrandingOverlay_TNS_Makers.svg
Cloud Native Ecosystem / Kubernetes / Microservices / Open Source / Software Development / Sponsored
Tame the Monolith with Cloud Foundry
3 Nov 2016 2:05pm, by Kiran Oliver
CI/CD / Cloud Native Ecosystem / Containers / Kubernetes / Microservices / Observability / Contributed
Is Your Infrastructure Ready for a Decoupled Deployment?
2 Nov 2016 9:02am, by Swarna Podila
Cloud Native Ecosystem / Containers / Kubernetes / Microservices / Security / Storage
Apcera’s New Platform Brings Legacy Applications into the Container Fold
1 Nov 2016 1:30am, by Susan Hall
API Management / Kubernetes / Microservices / Security / Contributed
Make the Most from Kubernetes’ New Network Policy API
28 Oct 2016 9:47am, by Andy Randall
API Management / Culture / IoT Edge Computing / Kubernetes / Microservices / Serverless
Nanoscale.io Connects Legacy Systems to Microservices
27 Oct 2016 7:09am, by Mark Boyd
https://cdn.thenewstack.io/media/2016/01/PodcastBrandingOverlay_TNS_Makers.svg
API Management / Cloud Native Ecosystem / Microservices / Observability / Sponsored
Cloud Foundry, Microservices, and the Multi-Cloud Future
26 Oct 2016 9:05am, by Kiran Oliver
API Management / Cloud Native Ecosystem / Kubernetes / Microservices / Serverless / Software Development
TNS Guide to Serverless Technologies: The Best Frameworks, Platforms and Tools
26 Oct 2016 12:09am, by Lawrence E Hecht
Cloud Native Ecosystem / Containers / Microservices / Contributed
Why CTOs are Warming Up to Microservices
25 Oct 2016 8:44am, by Chris Latimer
DevOps / Microservices
How the 12-Factor App Methodology Streamlines Application Development
25 Oct 2016 7:43am, by Jennifer Riggins
Cloud Native Ecosystem / Kubernetes / Microservices
Cloudsoft AMP: The Universal Control Plane
19 Oct 2016 10:32am, by Scott Hartzel
Seven Deadly Sins
API Management / CI/CD / Data Science / DevOps / Microservices / Open Source / Software Development
Seven (More) Deadly Sins of Microservices
19 Oct 2016 1:00am, by Dawn Foster
Containers / Data Science / Kubernetes / Microservices / Observability / Open Source / Software Development
Fluentd Offers Comprehensive Log Collection for Microservices and Cloud Monitoring
18 Oct 2016 3:00am, by Mary Branscombe
https://cdn.thenewstack.io/media/2016/01/PodcastBrandingOverlay_TNS_Makers.svg
Microservices / Serverless
What Makes IBM OpenWhisk Different? Openness
17 Oct 2016 3:52pm, by Kiran Oliver
Containers / Data Science / Kubernetes / Machine Learning / Microservices / Observability
Instana Brings Microservices Monitoring to the Service Level
11 Oct 2016 7:51am, by Susan Hall
CI/CD / Containers / DevOps / Kubernetes / Microservices / Security / Open Source / Contributed
Container Camp U.K.: Some Best Practices for Continuous Security
5 Oct 2016 11:52am, by Jennifer Riggins
Cloud Native Ecosystem / Microservices / Open Source / Software Development / Contributed
Meet Zipkin: A Tracer for Debugging Microservices
5 Oct 2016 9:21am, by Joab Jackson
Data Science / Microservices
Twitter’s IT Chargeback System Sets the Stage for End-to-End Service Lifecycle Management
20 Sep 2016 10:08am, by Joab Jackson
API Management / Containers / DevOps / Kubernetes / Microservices / Observability
The Five Principles of Monitoring Microservices
13 Sep 2016 9:16am, by Apurva Dave and Loris Degioanni
Pagination Previous Button
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.