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.
API Management / Cloud Native Ecosystem / Microservices / Service Mesh / Software Development
The Role of API Gateways in Microservice Architectures
21 Sep 2017 12:54pm, by Joab Jackson
Containers / Kubernetes / Microservices / Observability
Netsil Visualizes the Performance of Microservices
21 Sep 2017 6:00am, by Susan Hall
Cloud Native Ecosystem / Microservices
CNCF Adds Oracle, Onboards the Envoy and Jaeger Projects
13 Sep 2017 9:00am, by Joab Jackson
Containers / Kubernetes / Microservices / Observability / Service Mesh / Software Development
StackPointCloud Augments Kubernetes with the Istio Service Mesh
13 Sep 2017 6:00am, by TC Currie
DevOps / Microservices / Observability
New Relic’s FutureStack 2017 Prepares Monitoring for DevOps Speeds
12 Sep 2017 5:00am, by TC Currie
CI/CD / Data Science / Microservices
From Monolith to Microservices: One Company’s Plan
12 Sep 2017 2:00am, by Jennifer Riggins
Cloud Native Ecosystem / Culture / IoT Edge Computing / Microservices / Serverless / Software Development
Event-Driven Architecture Is the Wave of the Future
11 Sep 2017 9:00am, by TC Currie
CI/CD / Cloud Native Ecosystem / Culture / Microservices
Microservices: The Good, the Bad and the Hype
11 Sep 2017 2:00am, by Jennifer Riggins
Microservices / Software Development
Netlify Grows from SSG to CMS — and Launches a Microservices Gateway
7 Sep 2017 2:00am, by Michelle Gienow
Cloud Services / Containers / Kubernetes / Microservices / Observability / Service Mesh / Software Development
Nginx Pairs with Istio to Simplify the Service Mesh
6 Sep 2017 9:30am, by Alex Handy
CI/CD / Cloud Native Ecosystem / Containers / DevOps / Kubernetes / Microservices
Considerations for CIOs and IT Implementers to Assess Kubernetes
5 Sep 2017 3:00am, by Craig Martin, Janakiram MSV and Krishnan Subramanian
DevOps / Microservices / Sponsored / Contributed
Site Reliability Engineering Is a Kind of Magic
30 Aug 2017 6:00am, by Peter Waterhouse
Containers / Kubernetes / Microservices / Serverless
Explore Multicloud Deployments with Microsoft’s ACI Connector for Kubernetes
30 Aug 2017 2:00am, by Janakiram MSV
API Management / Cloud Native Ecosystem / Containers / Microservices / Contributed
Distributed Systems Are Hard
25 Aug 2017 6:00am, by Anne Currie
Cloud Services / Containers / Data Science / Microservices
Tutorial: Building and Deploying a Microservices Application with Azure Container Instances
25 Aug 2017 2:00am, by Janakiram MSV
DevOps / Kubernetes / Microservices / Security / Contributed
Aporeto’s Vision for a Shared Orchestration and Security Platform
24 Aug 2017 2:00am, by Scott M. Fulton III
API Management / Cloud Native Ecosystem / Microservices
Why Microservices Succeed in App Integration Where Web Services Stumbled
22 Aug 2017 3:21pm, by Alex Handy
Cloud Services / Containers / Kubernetes / Microservices / Serverless
Lightning Fast Container Provisioning with Microsoft’s Azure Container Instances
18 Aug 2017 2:00am, by Janakiram MSV
Cloud Native Ecosystem / IoT Edge Computing / Microservices / Software Development
Behind the Scenes of Lyft’s New Application Service Mesh, Envoy
17 Aug 2017 5:00am, by TC Currie
Cloud Native Ecosystem / Containers / Kubernetes / Microservices / Networking
Tigera Aims to Ease Connectivity Pain with Kubernetes
11 Aug 2017 9:00am, by Susan Hall
Containers / Culture / Microservices
Ancestry.com’s Docker Story and How It Eventually Led to Kubernetes
7 Aug 2017 9:00am, by TC Currie
API Management / CI/CD / Cloud Native Ecosystem / Data Science / Kubernetes / Microservices / Security / Serverless / Software Development
This Week in Scalability: The KEG Hangover
29 Jul 2017 6:00am, by Joab Jackson
Containers / DevOps / Kubernetes / Machine Learning / Microservices / Security
StackRox Offers a Fine-Grained View of Container Security
25 Jul 2017 6:00am, by Susan Hall
Containers / Microservices
Docker Basics, Part Zero: Why Should I Care about Containers (and Microservices) Anyway?
21 Jul 2017 6:00am, by Michelle Gienow
Cloud Native Ecosystem / Kubernetes / Microservices
Salesforce, Comcast Test Kubernetes for Massively Scalable Workloads
19 Jul 2017 11:42am, by Joab Jackson
https://cdn.thenewstack.io/media/2016/01/PodcastBrandingOverlay_TNS_Makers.svg
Cloud Native Ecosystem / DevOps / Microservices / Sponsored
Comcast Has Over 1,500 Developers Working on Cloud Foundry
18 Jul 2017 2:41pm, by Alex Williams and Scott M. Fulton III
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.