Dzone - DevOps
MAY 4, 2020
With the adoption of Kubernetes and microservices, the edge has evolved from simple hardware load balancers to a full stack of hardware and software proxies that comprise API Gateways, content delivery networks, and load balancers. In the mid-1990s, web application architecture was in its infancy. The Early Internet and Load Balancers.
LeanEssays
JANUARY 19, 2019
Every large agile framework that I know of is an excuse to avoid the difficult and challenging work of sorting out the organization’s system architecture so that small agile teams can work independently. How do you approach the challenge of scaling this way of working? Over time, Amazon learned how to recognize friction and eliminate it.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Honeycomb
JANUARY 3, 2022
It’s harder to understand and operate production systems in 2021 than it was in 2001. There are valid reasons why it’s harder: The architecture of our systems has gotten a lot more sophisticated and complex over the past 20 years. The move to these modern architectures is for good reason. Why is that?
Confluent
MAY 21, 2019
When you build microservices architectures, one of the concerns you need to address is that of communication between the microservices. An example can be the backend architecture for an insurance product. This leads us to event streaming microservices patterns.
O'Reilly Media - Ideas
JANUARY 25, 2024
While we like to talk about how fast technology moves, internet time, and all that, in reality the last major new idea in software architecture was microservices, which dates to roughly 2015. Who wants to learn about design patterns or software architecture when some AI application may eventually do your high-level design?
James Shore
JUNE 7, 2021
Kerth 2001] (ch. For example, if you discover that none of your database wrappers fail fast, you could create an Architecture Decision Record (see “Architecture Decision Records” on p.XX) to incrementally add them. Or, “we have microservices, not a monolith.” This is called distancing through differencing.
James Shore
AUGUST 19, 2020
In fact, programming was considered such a mechanical activity that, for a while, there was a movement called CASE—Computer Aided Software Engineering—to automatically convert architectural diagrams into code. In 2001, 17 of the lightweight methodology proponents met at a ski resort in Utah to discuss unifying their efforts.
Expert insights. Personalized for you.
54 
Let's personalize your content