Aggregated enterprise architecture wisdom
In a recent post I briefly discussed the changes in roles and emphasis when a development or transformation effort changes from a waterfall (Big Bang) effort to a short cycle-agile effort. This post will discuss the topic in more detail in terms …
Big data vs. traditional databases: Can you reproduce YouTube on Oracle’s Exadata? | ZDNet
“…Cowen & Co. analyst Peter Goldmacher. In a 75-page report, Goldmacher walks through the database landscape and concludes that the consensus view that the growth of data will boost traditional database vendors is dead wrong. Goldmacher said:
We believe the vast majority of data growth is coming in the form of data sets that are not well suited for traditional relational database vendors like Oracle. Not only is the data too unstructured and/or too voluminous for a traditional RDBMS, the software and hardware costs required to crunch through these new data sets using traditional RDBMS technology are prohibitive…”
tags: bigdata
Posted from Diigo. The rest of my favorite links are here.
Related posts:
Archimate aims to be the standard notation for enterprise-architectures. But has it become too IT-centric to be usable for that purpose? And is there any way we can get it to break out of the IT-centric box?
These questions came up for me whilst exploring the architectural processes we could use in expanding a business-model developed […]
Trust is the core of the enterprise in action. So why do so many businesses and other organisations seem to go out of their way to destroy that trust? And what can we as enterprise-architects do to make it work better?
This came up in a tweet yesterday from the Open Group Brazil’s Isabela Abreu, pointing a […]
That’s a bit of a mouthful – but it is the synthesis of a lot of material from the SITA technology conference held near Brussels in June this year.So, I’ll put in context and then see where it leads us. The context is that in the airline industry, cost…
That’s a bit of a mouthful – but it is the synthesis of a lot of material from the SITA technology conference held near Brussels in June this year.So, I’ll put in context and then see where it leads us. The context is that in the airline industry, cost…
The Open Group set up two informal Twitter polls this week during The Open Group Conference, Austin. If you wondered about the results, or just want to see what our Twitter followers think about some topline issues in the industry in very simple terms,…
1. User Control and Consent: Digital identity systems must only reveal information identifying a user with the user’s consent. 2. Limited Disclosure for Limited Use The solution which discloses the least identifying information and best limi…
1. User Control and Consent:
Digital identity systems must only reveal information identifying a user with the user’s consent.
2. Limited Disclosure for Limited Use
The solution which discloses the least identifying information and best limits its use is the most stable, long-term solutio.
The Law of Fewest Parties
Digital identity systems must limit disclosure of identifying information to parties having a necessary and justifiable place in a given identity relationship.
4. Directed Identity
A universal identity metasystem must support both “omnidirectional” identifiers for use by public entities and “unidirectional” identifiers for private entities, thus facilitating discovery while preventing unnecessary release of correlation handles.
5. Pluralism of Operators and Technologies:
A universal identity metasystem must channel and enable the interworking of multiple identity technologies run by multiple identity providers.
6. Human Integration:
A unifying identity metasystem must define the human user as a component integrated through protected and unambiguous human-machine communications.
7. Consistent Experience Across Contexts:
A unifying identity metasystem must provide a simple consistent experience while enabling separation of contexts through multiple operators and technologies.
Posted via email from Jeffrey Blake – The Brand Hammer | Comment »
1. User Control and Consent:
Digital identity systems must only reveal information identifying a user with the user’s consent.
2. Limited Disclosure for Limited Use
The solution which discloses the least identifying informat…
There is a clear distinction between Enterprise Architecture, as described by the architect, and Enterprise Architecture as implemented by the enterprise. I would like to posit the following as a fundamental principle that describes the differenc…
I ran across a document from the Dept. of Commerce that describes Enterprise Architecture as follows: “An Enterprise Architecture (EA) is a blueprint that explains how the results of Strategic Planning, Performance Planning, Budgeting, Capital Pl…
.jpg)