This article is translated from Unbundling: The Natural Evolution of Tech Stacks by Bilgin Lbryam . There are inevitably some omissions in the translation. Please give us feedback if you have any suggestions.
I'm a bit confused about how to translate "unbundling". I once translated it as "decoupling", but decoupling is the translation of "decoupling". Here I translate it into splits. If you have a better translation, please let me know.
Translator's note
The author should have left Red Hat in July last year to join Diagrid, a startup based on Dapr. He once wrote about Multi-Runtime Microservices Architecture to introduce multi-runtime. Multi-runtime is actually a manifestation of spin-off.
The author triggers from a variety of technologies and teams to introduce the manifestation of spin-off in evolution. In addition to what is mentioned in the article, I think what can be split is computing resources. Split computing resources: virtual machines, multi-tenants, multi-clusters, multi-clouds, hybrid clouds to reduce costs, avoid vendor lock-in, and improve performance and reliability. In the process of splitting computing resources, supporting technologies have also been derived to solve the inconvenience caused by the split.
With the continuous development of the IT field, new software architectures, development technologies and tools are emerging one after another. Include and mesh microservices, microfrontends, zero trust, service meshes, and data meshes. Although there are clear differences between these technologies and approaches, they are all connected by a common trend: the unbundling of technology stacks and teams. This trend includes breaking down systems into smaller, independent components and organizing work into smaller, more focused teams to achieve greater flexibility and modularity.
How do they all embody spin-offs?
- Microservices emerged in response to the limitations of a monolithic architecture. As applications grow, the monolithic architecture lacks flexibility and is difficult to expand and maintain. By decomposing a monolithic application into smaller, independent services, each part of the application can be developed, deployed, and scaled independently, shortening development cycles and increasing agility.
- Hexagonal architecture emerged to improve the flexibility and maintainability of 3-tier applications by decoupling components and providing standard interfaces for interacting with them.
- Domain-driven design (DDD) is a software development methodology that helps break down a monolithic application into smaller, loosely coupled modules that represent different business domains or contexts.
- Microfrontend architecture is a design approach that breaks down large monolithic frontend applications into smaller, independent modules that can be developed and deployed independently.
- JAMstack decouples the front-end and back-end of an application by separating the HTML, CSS, and JavaScript that make up the user interface from the server-side code and database that power the application. Applications can be maintained more easily since changes to one part of the system do not require changes to other parts.
- Service mesh separates the network responsibilities of a distributed application (such as routing, load balancing, and service discovery) from the application itself, allowing developers to focus on building business logic and functionality without worrying about the underlying network infrastructure.
- Similar to microservices, data grids break large, complex systems into smaller independent components. It breaks down data governance and management practices into smaller, independent components that can be implemented and executed consistently across disparate data sources and systems.
- The 2 Pizza Teams model is a strategy for organizing teams and work in an organization that promotes smaller teams that can respond to change more quickly, communicate and collaborate, and can make decisions faster and solve problems more effectively.
The end result of every technology trend is unbundling. Break down the technology stack into independent components and teams into smaller, more focused teams that may be expanded to all other areas. After front-end, data, network, and security, what do you think will be the next split area? Join me as I work on Dapr and spinoff integrations. Also follow me at @bibryam and shout out any thoughts and comments you have on the topic of spinoffs .
The web version of Windows 12 deepin-IDE compiled by junior high school students was officially unveiled. It is known as "truly independently developed" QQ has achieved "three-terminal simultaneous updates", and the underlying NT architecture is based on Electron QQ for Linux officially released 3.2.0 "Father of Hongmeng" Wang Chenglu : Hongmeng PC version system will be launched next year to challenge ChatGPT, these 8 domestic AI large model products GitUI v0.24.0 are released, the default wallpaper of Ubuntu 23.10, a Git terminal written in Rust, is revealed, the "Tauren" in the maze JetBrains announces the WebStorm 2023.3 roadmap China Human Java Ecosystem, Solon v2.5.3 releasedArticles are published uniformly on the public account
云原生指北
