Remove AWS Remove Database Remove Infrastructure Remove Software Architecture
article thumbnail

5 key areas for tech leaders to watch in 2020

O'Reilly

Software architecture, infrastructure, and operations are each changing rapidly. The shift to cloud native design is transforming both software architecture and infrastructure and operations. Also: infrastructure and operations is trending up, while DevOps is trending down. Coincidence?

article thumbnail

MLOps and DevOps: Why Data Makes It Different

O'Reilly

As with many burgeoning fields and disciplines, we don’t yet have a shared canonical infrastructure stack or best practices for developing and deploying data-intensive applications. What: The Modern Stack of ML Infrastructure. Adapted from the book Effective Data Science Infrastructure. Foundational Infrastructure Layers.

DevOps 137
Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

Trending Sources

article thumbnail

Legacy Architecture Modernisation With Strategic Domain-Driven Design

Strategic Tech

Architecture modernisation tools and techniques for each phase (these lists are not exhaustive) Business Strategy Alignment Software architecture is the significant technical decisions that have business consequences. This means a software architecture should be purposely designed for the most favourable business consequences.

article thumbnail

Amazon EC2 Cluster GPU Instances - All Things Distributed

All Things Distributed

These trade-offs have even impacted the way the lowest level building blocks in our computer architectures have been designed. Modern CPUs strongly favor lower latency of operations with clock cycles in the nanoseconds and we have built general purpose software architectures that can exploit these low latencies very well.Ă‚

AWS 136
article thumbnail

The Challenges and Traps of Architecting Sociotechnical Systems

Strategic Tech

Loosely-coupled teams enabled by loosely-coupled software architecture is one of the strongest predictors of continuous delivery performance and organizational scaling. Whenever a team starts on a piece of work they should own all of the code and infrastructure that needs to change in order to deliver the work.

Systems 40