SmoothSpan Blog

For Executives, Entrepreneurs, and other Digerati who need to know about SaaS and Web 2.0.

Archive for September 2nd, 2007

Links: September 3, 2007

Posted by Bob Warfield on September 2, 2007

Awesome Context Aware Image SizingLots of people are talking about this Truly Great Innovation for photo editors!  Hope for it in PhotoShop soon!

An Introduction to Erlang for Curly Brace Programmers:  Good intro to massively parallel language Erlang for Java and C++ types.

Building Your Own Social Network

Business Collaboration Requires Collaboration Technology

Elephant Math:  Seth Godin gives us another excellent look at how to trigger real viral growth in marketing.  See my piece on Web 2.0 Persuasion for more on this.

Seth Also Talks About Audio Books:  Interesting how fewer audio books can still lead to more effective results.

Dion says Mainstream Business is Ready for Web 2.0

A couple of blogs on whether IT or Business is buying SaaS and whether SaaS lets the Business bypass IT

Seven Steps to Successful SaaS Adoption:  Including some new ideas on what can be done self-service (Localization).

Top 15 Mistakes in OpenMP:  aka Why parallel programming in Curly Braced Languages is Hard.

Jeremy Zawodny on Why There is No Web OS:  He is wrong (see the comments on his note), but then again, maybe there is no spoon.

A Staggering Reading List for Search Engine Afficionados

The Manifesto of the Futurist Programmers:  They’re right!

The Era of DSL’s:  Polyglot Programming is Here to Stay

What SOA Needs to Learn from Ruby On Rails:  Convetion over Configuration.  Many other things would benefit from these observations!

Posted in saas | Leave a Comment »

Persistent mySQL Now Available for Amazon EC2/S3 Junkies

Posted by Bob Warfield on September 2, 2007

There are now two companies, Elastra and RightScale, who are offering solutions for Persistent mySQL on Amazon EC2/S3.  This is a significant development in utility computing because most companies wishing to use Amazon’s platform would have to solve this thorny problem before they could get on with doing something interesting.   Having an off-the-shelf solution makes it that much easier to adopt the platform.

Some are concerned about the price or about getting locked into Amazon, but I think these are relatively safe bets.  First, we already have 2 players, and Amazon will likely offer a solution of its own.  Hence the price will stabilize to a lower point in a competitive marketplace.  Second, mySQL is the API here, not Amazon.  Any utility computing service that wants to make a go will have to support mySQL in some form or fashion, so rehosting may not even be that bad.  Hence the lock-in is minimal.

Thanks to High Scalability for the heads up!

Posted in amazon, data center, ec2, grid, multicore, platforms, saas, Web 2.0 | 1 Comment »

Why Can’t I Search My Enterprise Data As Well As Google Searches the Internet?

Posted by Bob Warfield on September 2, 2007

I read with some interest Andrew McAfee’s dual articles on a phenomenon he calls emergence:  The Mechanisms of Online Emergence and Sharp Responses to Flat Communities.

Emergence is a property of the web that allows it to create high order pattern out of seeming chaos and thereby improve everybody’s experience.  He introduces the concept by asking why you can’t search data within your own company as easily or as well as Google searches the web?  Why indeed.  Putting aside the issue that for every company I’ve been at the information is heavily siloed and therefore not searchable by any single tool, McAfee blames a lack of emergence.  In this case, it is emergence related to Google’s PageRank algorithm.

Let’s take a brief aside to talk about PageRank, because McAfee has it exactly right when he says:

Google’s founders realized that even though the Internet is extremely decentralized the Web still has a huge amount of structure thanks to links.  This structure can be exploited not just for navigation (i.e. hopping from page to page via links) but also for search.  Links provide so much structure, in fact, that the Web appears to us to be a very orderly place; we can find what we want on it.  

He goes on to liken this emergent web behavior to that of an ant colony which is highly decentralized but has emergent social behavior.  Think of the pathways that get worn through the web as links are created as being like the pheromone trails that govern how ants navigate out in the world away from their colony.  By using these trails the ants eventually identify for their brethren exatly where the good stuff (i.e. food) is as well as how to avoid the bad stuff (i.e. obstacles and enemies).  Likewise, the link structure of the web helps us to find the good stuff too, and using links to modify what is learned from keywords alone is exactly the insight provided by the Page Ranking algorithm that all major search engines employ today.

With this insight about Page Ranking (and ant doings) in mind, let’s consider the Business Web or the so-called Intranet.  In particular, let’s ask what business has to do to take advantage of the emergence phenomenon. 

The first thing on the list has to be escaping from silos.  Nothing can be more destructive to emergence than breaking up the information habitat into small fiefdoms that are not connected.  Eliminating silos is much easier said than done because many times silos are there for sound business reasons.  Some information should not be broadly available.  For example, the company’s financial results cannot legally be made available far and wide within a company in advance of announcing those results to the public for companies whose shares trade in the public markets.  Because of this, Business Web 2.0 requires a different Trust Fabric than Social Web 2.0.  Until standards-based mechanisms exist to impose those Trust Fabrics, we will be stuck.  The second issue is performing the search indexing over disparate tools.  Here organizations have a little better leeway to plan for the future.  They can at least start out using the same tools used on the web, rather than opting for various proprietary tools.  In cases where proprietary tools are a requirement, it will be important that those tools provide access for search engines to catalog their results.  Perhaps a minimal subset capability would be a facility to deliver HTML views of the data.  Lastly, on the subject of silos, the organization will need to find a search engine that has the flexibility to navigate the disparate collection of information repositories and dispense the results of searches according to a Trust Fabric that’s compatible with the requirements of the business.

Put another way, Enterprise IT is often obsessed with providing users with Single Sign On (SSO), so that logging in once gives people access to all the online resources based on their permission levels.  Those interested in fostering better reuse of information need to be obsessed with Single Search Engines.  It should be possible to type a search query into a single type-in and get results from every system that is a repository.  Here’s a thought on that:  what about mashups for search?  Maybe you can’t get to a SSE.  No worries, the appearance of an SSE will suffice.  There have been metasearch engines around since there’s been more than one search engine, so why not here too?  If your organization has not reached the SSE ideal, and it is hard to do so, why not make creating an Enterprise-wide metasearch a major initiative?  It isn’t all that hard to do.  Of course this all assumes thin clients running in web browsers, so make sure you aren’t too dependent on some proprietary fat client for search or a key information repository!

The second requirement when enabling emergent behavior is a mechanism whereby the information consumers can provide the feedback needed to create the emergent pathways.  This is also not an especially easy requirement to satisfy because we need some universal mechanism for establishing the pathways that anyone can follow and that are later amenable to analysis by the search engine.  The two most popular mechanisms at large in the World Wide Web for this are links and tagging.  Marc Canter and others have recently bemoaned that tagging hasn’t really kept up, so perhaps links are a more preferable mechanism.  Tagging without links is possible, but one wonders how useful, anyway.  Tags don’t contribute to emergence unless we have a powerful search algorithm that harnesses them, so that’s a strong argument not to become too dependent on them anyway.

The upshot is that it has to be possible to link to every bit of information that will be searched, and it must be easy to create new links (new ant trails).  The links are not so bad if you have SSO and SSE (even via Metasearch).  You can hardly get back search results without getting back a list of links.

The last requirement has to do with encouraging a culture of emergence.  Does your organization foster behaviors that lead to emergence, or does it discourage them?  McAfee calls this Freeform Software, but I think it is just as important to apply these principles to your organization’s culture:

  • Optional:  McAfee wants this, but I would eliminate it.  Look for ways to insist on adding to the emergent web.  For example, require certain kinds of documents be committed, receive peer review, and make it easy for peers to mark up, comment on, and add links all over.  Keep certain kinds of documents living as this encourages more linkages to the documents.  Documents with lifespans that are too short aren’t worth linking to.
  • Free of up-front workflow:  Eliminate as much friction as possible to freely adding information and freely adding emergence structures such as links.
  • Egalitarian, or indifferent to formal organizational identities:  It is essential that your culture be accepting of information no matter where it comes from within the hierarchy.
  • Accepting of many types of data:  Being able to accept all types of data is key to encouraging all types of Web 2.0 Personality Types to play along.  For example, is there a video online that shows your best demoer giving a demo of your product?  Can people easily find that video?  How easy is it for someone to create a video in your organization? 
  • To sum it all up, here is my wish list for enabling emergent behavior inside the Enterprise:

    1.  Single Sign On

    2.  Single Search Engine, including Metasearch to get there

    3.  Thin clients throughout

    4.  Mechanisms to give back structure:  I want to embed links in every document type, or as many as I can.  Tags are an excellent follow-on, but they’re less important.

    5.  Cultural factors need to encourage creation of content and structure.

    In the next installment, we’ll look at Business Alternatives to Page Rank.

    Submit to Digg | Submit to Del.icio.us | Submit to StumbleUpon

    Posted in business, strategy, user interface, Web 2.0 | 3 Comments »

     
    Follow

    Get every new post delivered to your Inbox.

    Join 313 other followers

    %d bloggers like this: