Remove Architecture Remove Database Remove Definition Remove Software Architecture
article thumbnail

The Relationship Between Software Architecture And Business Models (and more)

Strategic Tech

If every significant architecture decision has business consequences, then knowing the business model and which trade-offs to choose is maybe the most important skill of architects. But what is the actual relationship between a business model and a software architecture? A software system is a model of a domain.

article thumbnail

How architecture evolves into strategy

O'Reilly Software

I should start by saying this section does not offer a treatise on how to do architecture. This is my tailored view of it; others will have different definitions. Vitruvius and the principles of architecture. Architecture begins when someone has a nontrivial problem to be solved. Solid doesn't mean inflexible.

Strategy 100
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

5 tips for architecting fast data applications

O'Reilly Software

Considerations for setting the architectural foundations for a fast data platform. Google was among the pioneers that created “web scale” architectures to analyze the massive data sets that resulted from “crawling” the web that gave birth to Apache Hadoop, MapReduce, and NoSQL databases. Back in the days of Web 1.0,

article thumbnail

ABAC on SpiceDB: Enabling Netflix’s Complex Identity Types

The Netflix TechBlog

A cleanup process to prune stale relationships from the database. SpiceDB is then responsible for figuring out which relations map back to the autoscaling group, e.g. name, environment, region, etc. What was problematic about this design? Aside from being complicated, there were a few specific things that made Netflix uncomfortable.

Cache 249
article thumbnail

Domain Services: The Next (small) Evolution of Microservices

Strategic Tech

The microservices era has been good for software architecture. I remember when the idea of multiple databases was punishable by death. A domain service builds on the basic definition of a microservice: it’s a loosely-coupled, independently deployable element of software architecture which is owned by a single team.

article thumbnail

MLOps and DevOps: Why Data Makes It Different

O'Reilly

This is both frustrating for companies that would prefer making ML an ordinary, fuss-free value-generating function like software engineering, as well as exciting for vendors who see the opportunity to create buzz around a new category of enterprise software. Software Architecture. The new category is often called MLOps.

DevOps 138
article thumbnail

Consumer-driven Coupling: Patterns and Anti-patterns

Strategic Tech

Layers start to emerge and as a result, shipping new customer-facing features require changes that cut through multiple layers of the architecture. Being aware of the patterns inherent to layered sociotechnical architectures can save you a lot of pain and politics in the long-term. As a consequence, we also have subservient teams?—?teams