# Enterprise Architecture A strategic information asset base defining an enterprise's mission, needed information and technologies, and transition to new technologies; it includes baseline and target architectures and a sequencing plan. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Something New Has to Sit Between Agents and Databases DevFeed: [Something New Has to Sit Between Agents and Databases]() Original publisher: [Read original article]() Author: flashdba Published: 2026-06-15T12:46:59Z Content type: opinion Language: en Sources: [flashdba]() Topics: [Architecture & Design](), [Enterprise Architecture](), [Artificial Intelligence](), [Databases]() Tags: [agentic](), [agentic-ai](), [ai](), [architecture](), [cloud](), [credentials](), [databases](), [databases-and-agentic-ai](), [enterprise-architecture](), [inferencing](), [performance]() ### AI overview This article argues that agentic AI removes human dependencies that enterprise architectures and systems of record have implicitly relied on. It proposes a deliberate intermediary layer between agents and databases to provide identity, intent recovery, rate control, behavioural reasoning, and accountability requirements that existing infrastructure does not address. ### Source excerpt Enterprise architecture depended on humans in ways nobody designed - and agentic AI is removing those dependencies. Something new has to sit between agents and databases, and it needs to be built deliberately. ## Enterprise Architecture Quietly Depended on Humans in Far More Places Than We Realised DevFeed: [Enterprise Architecture Quietly Depended on Humans in Far More Places Than We Realised]() Original publisher: [Read original article]() Author: flashdba Published: 2026-06-08T14:19:07Z Content type: opinion Language: en Sources: [flashdba]() Topics: [Enterprise Architecture](), [Architecture & Design](), [Artificial Intelligence](), [Actor](), [properties]() Tags: [actor](), [agentic](), [agentic-ai](), [ai](), [architecture](), [cloud](), [databases](), [databases-and-agentic-ai](), [enterprise-architecture](), [inferencing](), [performance](), [properties]() ### AI overview This article argues that enterprise architecture depended on implicit properties supplied by human participants, including predictable workload, intent, accountability, feedback, and limited capacity. It concludes that agentic AI exposes pressure across multiple technical and organisational domains by removing those assumptions simultaneously. ### Source excerpt Enterprise architecture was built around a human actor whose presence provided properties nobody designed and nobody priced. Agentic AI is the first technology to remove those properties simultaneously - and the absence is now visible across every domain. ## Agentic AI Exposes Gaps Between Deployment Teams and System Owners DevFeed: [Agentic AI Exposes Gaps Between Deployment Teams and System Owners]() Original publisher: [Read original article]() Author: flashdba Published: 2026-05-25T10:47:43Z Content type: opinion Language: en Sources: [flashdba]() Topics: [deploying agentic AI](), [Enterprise Architecture](), [Architecture & Design](), [audit]() Tags: [agentic](), [agentic-ai](), [agents](), [ai](), [ai-agents](), [architecture](), [audit](), [cloud](), [databases](), [databases-and-agentic-ai](), [enterprise-architecture](), [governance](), [inferencing](), [infrastructure](), [performance](), [systems]() ### AI overview The article argues that agentic AI is eroding the technical boundary between application and infrastructure teams while leaving organizational accountability and governance structures inadequate. It highlights impacts on workloads, identities, audit trails, and capacity costs. ### Source excerpt The people deploying AI agents are not the people responsible for the systems they stress - and the governance structures that might close that gap don't yet exist. ## Drop Books DevFeed: [Drop Books]() Original publisher: [Read original article]() Author: Jay (noreply@blogger.com) Published: 2015-06-25T13:47:00Z Content type: opinion Language: en Sources: [Jay Fields]() Topics: [Refactoring](), [legacy](), [Architecture & Design](), [Enterprise Architecture]() Tags: [books](), [enterprise-architecture](), [legacy-code](), [patterns](), [refactoring](), [technical]() ### AI overview The author describes "Drop Books," technical books repeatedly purchased and given to friends and colleagues to spread useful programming ideas. The recommended books include Refactoring, Working Effectively with Legacy Code, Passionate Programmer, and Patterns of Enterprise Architecture. ### Source excerpt The vast majority of books I purchase are for my own enjoyment, but not all of them. There are a few books that I buy over and over, and drop on the desks of friends and colleagues. These books, all technical, are books that I think most programmers will benefit from reading. I call these books "Drop Books"; I drop them and never expect them to be returned. My main motivation for dropping books is to spread what I think are great ideas. Specifically, I'm always happy to spread the ideas found in the following books: Refactoring Working Effectively with Legacy Code Passionate Programmer Patterns of Enterprise Architecture I know a few of my friends buy Drop Books as well. Spreading solid ideas and supporting authors seems like a win/win to me; hopefully more and more people will begin to do the same. © Jay Fields - www.jayfields.com ## Eric Evans in the house DevFeed: [Eric Evans in the house]() Original publisher: [Read original article]() Author: Nicolai Høge Published: 2015-03-10T14:37:49Z Content type: article Language: en Sources: [Finn.no]() Topics: [Domain-driven design (DDD)](), [Architecture & Design](), [Enterprise Architecture]() Tags: [architecture](), [course](), [ddd](), [domain-driven-design](), [enterprise-architecture](), [workshop]() ### AI overview FINN.no invited Eric Evans for a week of strategic Domain-Driven Design courses, workshops, and a presentation. The article describes the organization's effort to move from a monolith toward a more flexible and scalable architecture. ### Source excerpt In our continuing quest to break up our old monolith and create a more flexible and scalable architecture, we have realized that we need to look at some new tools and methods. One of the more promising approaches was Domain Driven Design, a term coined by Eric Evans in his Big Blue Book Quite a few people in FINN has read (at least parts of) the Domain-Driven Design book, and we did some preliminary efforts to map our domains and look at our bounded contexts. We quickly realized that this was a very complex exercise, even with highly motivated tech and product people present. We figured we needed some help to get us on the right track. If you need help and information about DDD, why not get it straight from the horse's mouth? So we got Eric Evans to visit us for a week at the end of February. We needed to make the most of our time with Eric, so we set up a rather extensive agenda: Day Subject Attending Monday Strategic Domain Driven Design Course FINNs CTO, our functional product directors, the members of our enterprise architecture group including our Chief Enterprise Architect, several key developers and a couple of our international friends from Schibsted Classified Media Tuesday Strategic Domain Driven Design Course cont'd Same as Monday Wednesday Workshop: Ad concept and our miscellaneous vertical Chief Enterprise architect, EA group, Functional Product Director, Product Owner, Lead Developers Thursday Workshop: Job vertical and company profile Chief Enterprise architect, EA group, Functional Product Director, Product Owner, Lead Developers Friday Presentation for everyone in FINN.no, plus workshop: Communications Chief Enterprise architect, EA group, Functional Product Director, Product Owner, Lead Developers The course on Monday and Tuesday was extremely helpful in getting everyone up to speed on the terms and method of strategic domain driven design. The workshops the rest of the week focused on understanding the challenges involved in each area, and trying