Aggregated enterprise architecture wisdom
• Evolution rather than replacement.
The private cloud can evolve from existing virtualized infrastructure, enabling the transition to cloud computing without a complete and disruptive infrastructure overhaul.
• Security and compliance.
With a private…
• Evolution rather than replacement.
The private cloud can evolve from existing virtualized infrastructure, enabling the transition to cloud computing without a complete and disruptive infrastructure overhaul.
• Security and compliance.
With a private cloud, data is retained within the enterprise, behind the corporate firewall, where IT can exercise full control over security, privacy, and regulatory compliance. With public clouds, enterprise data is housed in external data centers—and may move from location to location, without IT’s knowledge or consent. The dynamic movement of data in a public cloud may also present compliance challenges with local regulations.
• Service level agreements (SLAs).
Keeping applications in-house can help IT continue to meet SLAs deining performance, availability, and other critical business requirements. Some external providers may not be able to furnish the same level of service.
• Cost.
A large enterprise private cloud can provide economies of scale, resulting in total cost of ownership (TCO) that is competitive with or lower than public clouds. Intel IT, for example, found that services can be hosted internally at equal or lower TCO than hosting them externally.
• Building expertise.
Architecting a private cloud enables IT organizations to develop a knowledge base that can be applied to public clouds in the future. When creating the private cloud, IT will need to develop detailed application and data inventories, and gain key skills such as managing cloud SLAs. This experience will help build effective relationships with public cloud providers, enabling IT organizations to assess whether they meet enterprise requirements
(excerpt from http://www.readwriteweb.com/cloud/cio-agenda-paper-vmware.pdf)
Posted via email from Jeffrey Blake – The Enterprise Architect | Comment »
Enhance branding and awareness Protect reputation Extend public relations Build community or loyalty Extend customer service Facilitate research and development Drive sales or leads via briansolis.com connect with me Posted via em…
- Enhance branding and awareness
- Protect reputation
- Extend public relations
- Build community or loyalty
- Extend customer service
- Facilitate research and development
- Drive sales or leads
Posted via email from Jeffrey Blake – The Enterprise Architect | Comment »
1.Honesty: We will honor our privacy policy and terms of service.
2. Clarity: We will make sure that our policies, terms of service, and settings are easy to find and understand.
3. Freedom of speech: We will not delete or modify user data without a cl…
1.Honesty: We will honor our privacy policy and terms of service.
2. Clarity: We will make sure that our policies, terms of service, and settings are easy to find and understand.
3. Freedom of speech: We will not delete or modify user data without a clear policy and justification.
4. Empowerment : We will support assistive technologies and universal accessibility.
5. Self-protection: We will support privacy-enhancing technologies.
6. Data minimization: We will minimize the information users are required to provide and share with others.
7. Control: We will work toward enabling users to own and control their data and won’t facilitate sharing their data unless they agree first.
8. Predictability: We will obtain the prior consent of users before significantly changing who can see their data.
9. Data portability: We will make it easy for users to obtain a copy of their data.
10. Protection: We will treat user data as securely as our own confidential data unless they choose to share these data, and notify them if these data are compromised.
11. Right to know: We will show users how we are using their data and allow them to see who and what has access to their data.
12. Right to self-define: We will allow users to create more than one identity and use pseudonyms. We will not link them without their permission.
13. Right to appeal: We will allow users to appeal punitive actions.
14. Right to withdraw: We will allow users to delete their accounts and remove their data.
via blog.diasporafoundation.org
Posted via email from Jeffrey Blake – The Enterprise Architect | Comment »
Law 1: We seek comfort in relationships: Surround us with community, which we’ve seen success with like Facebook, Twitter and 4chan. Most interestingly is PostSecret, an ongoing community art project where people mail in their secrets anonymously o…
Law 1: We seek comfort in relationships: Surround us with community, which we’ve seen success with like Facebook, Twitter and 4chan. Most interestingly is PostSecret, an ongoing community art project where people mail in their secrets anonymously on one side of a homemade postcard.
Law 2: We all have something to say. So give us tools to express ourselves. Tools include comments, notes, and all the fun things Facebook has given us with Timeline, etc.
Law 3: We need to feel important. Use rewards to make us feel special. How do you make people feel special? One way is through exclusivity like Gilt Group. One way is through badges on Foursquare.
Law 4: We are hypnotized by beauty. Give us something beautiful to look out. Flipboard puts the image first. Instagram is a series of beautiful images within a community.
Law 5: We are captivated by the unknown. So target our curiosity. Foursquare does this with points! Pinterest does with page after page of constant intrigue.
Posted via email from Jeffrey Blake – The Enterprise Architect | Comment »
What are the different types of assets that we need to deal with in an enterprise-architecture? What implications arise across the architecture from the differences between these types? [I know I usually write too long, so as a kind of trial-run, I’m splitting up this original long-post into four smaller ones: please let me know […]
This post has been updated, and all updated text should be highlighted blue. I was asked the question I love to get the other day, “what do you mean by capability?”. I usually try to be brief when I explain my point of view and so I was this time to. However in this post […]
“…once more, or fill up the wall with our English dead” – to quote Shakespeare’s Henry V… Because, yes, it’s Himself the Welsh Dragon that’s at it again, in yet another public attempt to denigrate me, my work, and, of course, my professional credibility, competence, integrity, and the rest. Of course. Oh no, not again… […]
I’ve been involved in a number of meetings recently as our IT teams try to come to consensus on answering this question: What is a Roadmap? It’s been a fascinating series of discussions. One thing that strikes me is that most of the int…
.jpg)