SEARCH (ENTER TO SEE ALL RESULTS)
Cancel Search
POPULAR TOPICS
Contributed
News
sponsored-post-contributed
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
    • 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
      • Machine Learning
      • DevOps
      • Serverless
      • Microservices
      • Observability
      • Kubernetes Ecosystem
      • Docker Ecosystem
      • 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
 

Cloud Native Ecosystem

▾ 4 MINUTE READ — CLOSE

Cloud native computing allows teams to build and manage services using container architectures and stringing them into applications without worrying about servers. Containers connecting services, microservices, immutable infrastructure, and declarative APIs exemplify this approach, all working together in a loosely-coupled approach for maximum flexibility and development agility.

Initially, architectures required tightly bound clients and servers. Virtual machines were an abstraction that allowed the operating system to be disconnected from the underlying server. This approach allowed for hypervisors to emerge as platforms to run virtual machines on hosted environments.

The container runs as a process on a host, independent of the operating system. Virtualization technology is below the operating system and virtualizes the server, not the application. The operating system has to go wherever the virtual machine goes. Operators need to shut it down, then boot it back up and configure it to run with the database and the rest of the stack that it depends on.

Container-based architectures for developers and operations teams have modified the previous approach. Containers are symbolic of the cloud-native ecosystem and will be core to modern application architectures.
What Are Cloud Services?
Cloud services are software, infrastructure, or platforms facilitated by third-party providers and accessible to end-users through the web.

Cloud services advance the flow of user data between front-end clients —desktops, tablets, laptops, and users’ servers— and provider systems through the internet. Cloud services are accessible to users with a computer, internet connection, and operating system.
Benefits of Cloud Native Technologies
Cloud-native technologies enable teams to build and run scalable applications in unique and dynamic environments. These environments may be hybrid, private, or public clouds.

“Cloud-native technologies are used to develop applications built with services packaged in containers, deployed as microservices and managed on elastic infrastructure through agile DevOps processes and continuous delivery workflows,” writes Janakiram MSV, principal analyst at Janakiram & Associates and an adjunct faculty member at the International Institute of Information Technology.

Some of the benefits of cloud-native technologies include:

Reliability. Through microservices and Kubernetes, developers can build flexible applications and quickly isolate the impact of a failure to prevent a total crash.

Scalability. The ability to scale automatically is one of the main features of cloud-native technologies. Future needs are anticipated and handled by default, and payment is made only for resources in use.

Faster releases. With DevOps, cloud-native technologies allow teams to ideate, build, and ship applications faster, resulting in satisfied users and a successful organization.

Reduced cost. Kubernetes is an open-source platform used by many cloud-native technologies for managing containers. Containers provide standardization of tools and infrastructure, ensuring the effective use of resources and minimizing costs.

No vendor lock-in. Cloud technologies allow hybrid and multi-cloud use. Enterprises can run applications on any platform, such as public or private clouds, without making lots of modifications. This way, enterprises do not need to choose one infrastructure and face legacy vendor issues.

Cloud Native Apps Are a Step up from Cloud-Based Applications
Cloud native applications are architected to run entirely from and in the cloud. These solutions allow developers to update features quickly and easily. Cloud-based architectures are not created in the cloud but are migrated to the cloud and leverage some cloud functions like higher availability and scalability. Cloud native apps are considered an improvement in architecture because of their capabilities.

Here are some significant differences between cloud-native and cloud-based apps:

Price. Cloud native apps are cheaper than cloud-based applications because you pay for storage costs and licensing where applicable. With the latter, you have to own the entire infrastructure and purchase hardware, cooling, and power before teams can deploy applications.
Maintenance. Cloud native apps run on a microservices architecture reducing interruptions, unlike cloud-based applications, which may experience frequent interruptions due to specialized software configurations and hardware migrations.
Ease of use. Cloud native apps are flexible. Developers can build to scale and carry out app upgrades without disturbance. However, cloud-based apps experience downtime as they are tightly integrated, and any enhancements made may be required for the entire stack, resulting in downtime.
Implementation. Cloud native apps are faster to deploy since they require no hardware or software, unlike cloud-based applications requiring hardware provisioning and software setup.

How Does Cloud-Native Computing Work?
In cloud-native computing, the base computing unit is the service, which can communicate with other services via APIs. Ideally, each service should be encapsulated within a container and offer a single function — hence the name “microservice.” Containerizing the microservice makes it easy to develop. It can be moved along a single workflow of development and testing to production through a process called continuous integration and continuous deployment (CI/CD).

Building on the Kubernetes open-source container orchestration engine, first developed by Google, the Cloud Native Computing Foundation ensures a stack of open-source software to run cloud-native applications without being locked into a proprietary software vendor or commercial software.

Cloud-native software is witnessing remarkable improvements. Bookmark this page to get the latest articles about the latest developments in this industry.


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 / Sponsored
Sharded Deployments with MongoDB and Brooklyn, a Framework for Scaling
28 Apr 2015 6:33am, by Robert Moss
https://cdn.thenewstack.io/media/2016/01/PodcastBrandingOverlay_TNS_Analysts.svg
CI/CD / Cloud Native Ecosystem / Cloud Services / Containers / DevOps / Kubernetes
Containers and Continuous Delivery for the Enterprise
23 Apr 2015 5:00am, by Luke Lefler
Cloud Native Ecosystem / Containers / Security
VMware Responds to Container Movement with Lightweight Linux OS and Cloud-Native Tools
20 Apr 2015 5:01am, by Susan Hall
Cloud Native Ecosystem / Open Source / Software Development
Project Orleans: Different Than Erlang, Designed for a Broad Group of Developers
19 Apr 2015 2:01pm, by Mary Branscombe and Simon Bisson
Cloud Native Ecosystem / Containers
It’s a Hipster Thing, Don’t Worry About It — Software Defined Talk #29
19 Apr 2015 8:25am, by Michael Coté
Cloud Native Ecosystem
The Open Road to Galene, LinkedIn’s Search Architecture
16 Apr 2015 10:04am, by Kimberley Mok and Alex Williams
https://cdn.thenewstack.io/media/2016/01/PodcastBrandingOverlay_TNS_Makers.svg
Cloud Native Ecosystem / Containers
TNS Makers Sam Ramji: Cloud Foundry and the Flipside of Portability
16 Apr 2015 7:00am, by Luke Lefler
Cloud Native Ecosystem / Sponsored
Uber, Netflix and the Dreams of DevOps and Microservices
14 Apr 2015 8:36am, by Michael Coté
Cloud Native Ecosystem
Pivotal Makes In-Memory Database GemFire Open Source
13 Apr 2015 9:15am, by Susan Hall
https://cdn.thenewstack.io/media/2016/01/PodcastBrandingOverlay_TNS_Makers.svg
Cloud Native Ecosystem
TNS Makers: Sam Ramji on Giving Briefings to Bill Gates About Open Source
8 Apr 2015 8:00am, by Luke Lefler
CI/CD / Cloud Native Ecosystem
Do Not be Fooled by the Allure of Costco Levi’s — Software Defined Talk #28
7 Apr 2015 5:00am, by Michael Coté
Cloud Native Ecosystem / Data Science / Kubernetes
Piston Cloud’s Smart Move to Build a Fungible Platform
6 Apr 2015 7:57am, by Susan Hall
Cloud Native Ecosystem / Containers / Data Science / Serverless
Containers and Hosts in the Age of Compute
5 Apr 2015 11:09am, by Alex Williams
Cloud Native Ecosystem / Culture / Open Source / Software Development
WASP: 3D Printing Affordable Housing Out of Mud
4 Apr 2015 5:00am, by Kimberley Mok
https://cdn.thenewstack.io/media/2016/01/PodcastBrandingOverlay_TNS_Makers.svg
Cloud Native Ecosystem
TNS Makers: Sam Ramji, Commodore PET and the Strange Road to Microsoft
2 Apr 2015 8:00am, by Luke Lefler
Cloud Native Ecosystem / Data Science
HP Courts Developers with Tools for Monitoring Mobile Apps
30 Mar 2015 9:07am, by Susan Hall
Cloud Native Ecosystem / Containers / Data Science
Pivotal Cloud Foundry Extends Distributed Architecture with Added AWS Support
24 Mar 2015 7:01am, by Susan Hall
Cloud Native Ecosystem / Sponsored
The Apache Brooklyn Plugin for Cloud Foundry to Add Services Such as MongoDB
23 Mar 2015 8:03am, by Robert Moss
Cloud Native Ecosystem / Open Source / Software Development
The First Cloud Foundry ‘Dojo’ to Foster a Paired Programming Model
20 Mar 2015 12:17pm, by Susan Hall
Cloud Native Ecosystem / Microservices / Sponsored
Best Practices for Developing Cloud-Native Applications and Microservice Architectures
17 Mar 2015 8:48am, by Amy Feldman and Colin Henry
Cloud Native Ecosystem
Anne Gentle: One Stacker’s Journey
12 Mar 2015 7:07pm, by anne gentle
https://cdn.thenewstack.io/media/2016/01/PodcastBrandingOverlay_TNS_Analysts.svg
Cloud Native Ecosystem / Observability
Monitoring Distributed Architectures
12 Mar 2015 9:46am, by Luke Lefler
Cloud Native Ecosystem / Sponsored
Cloud Foundry and Apache Brooklyn for Automating PaaS with a Service Broker
11 Mar 2015 8:00am, by Alex Williams
Software Defined Talk Podcast
Cloud Native Ecosystem
Burn the Boats Because We’re Inventing Self-Driving Cars — Software Defined Talk #025
7 Mar 2015 8:00am, by Michael Coté
Cloud Native Ecosystem / Open Source
Open Cloud Helps Boost Market for Linux Talent
4 Mar 2015 9:59am, by Susan Hall
Cloud Native Ecosystem / Microservices
How Twitter’s Aurora Replaces Operating Systems with Stateless Services (Part 2)
25 Feb 2015 2:57pm, by Scott M. Fulton III
Pagination Previous Button
55 56 57 58 59 60 61 62 63 64
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.