ラベル vendor list の投稿を表示しています。 すべての投稿を表示
ラベル vendor list の投稿を表示しています。 すべての投稿を表示

2008年7月22日火曜日

Cloud Computingを提供するベンダー一覧

現在顕著なCloud Computing ベンダーのリスト

List Of Cloud Computing Service Providers

By Daya Baran at July 16, 2008 0 Comments

  • 3Tera - AppLogic grid OS used as cloud computing platform by service providers and enterprises
  • Agathon Group - Cloud provider. Services include highly available VPS, virtual private datacenters and ready-to-use LAMP stacks. Self-service ordering. Custom development and managed services available.
  • Amazon Web Services - Amazon EC2/S3 (Hardware-a-a-S & Cloud Storage)
  • Appistry - Cloud computing middleware - Enables easily scalable cloud computing in the enterprise.
  • Bungee Connect - Provides end to end tools and systems required to develop, deploy and host web applications (Platform as a Service)
  • Cassatt - Cassatt Active Response platform for enterprise clouds (using existing data center resources)
  • CloudScale Networks - Cloud enabler. Currently in private ALPHA only
  • CloudStatus- CloudEnabler. Real-time performance trending of cloud infrastructure (currently AWS).
  • Coherence - Oracle Coherence Data Grid for EC2 and other cloud platforms
  • CohesiveFT - CohesiveFT Elastic Server On-Demand
  • ElasticHosts - UK-based instant, on-demand servers in the cloud
  • Enomaly Inc - Service Provider & Cloud Enabler - Developer of the Enomalism Elastic Computing Platform & Elastic Drive
  • Flexiscale - Another instant provisioner of web servers with some advanced features like auto-scaling coming soon.
  • Force.com - Salesforce.com's application development platform (PaaS)
  • GigaSpaces - middleware for the cloud, "cloudware"
  • GoGrid - instant, on-demand servers offering "control in the cloud". Deploy Windows/Linux servers via web-interface in minutes
  • Google AppEngine - (PaaS)
  • GridLayer - Cloud Provider. A service by Layered Technologies that delivers Virtual Private Datacenters and virtual private servers from grids of commodity servers.
  • Heroku - Ruby on Rails in their Cloud
  • LayeredTechnologies - Cloud Provider. provider of on-demand hosting and cloud and utility computing solutions through its brand GridLayer.
  • Kaavo's IMOD is an easy to use online application. Cloud Computing Made Easy.
  • Microsoft Mesh - (PaaS)
  • Mosso - Rackspace's cloud hosting service
  • Nasstar - SaaS provider. Business grade Hosted Desktop service, UK market leaders.
  • Newservers - Instant provisioning of web servers either Windows or Linux
  • Nirvanix - Cloud Storage
  • Opsource - Enter SaaS Enabler
  • Qrimp - An AJAX based PaaS
  • RightScale - Cloud Enabler. The RightScripts Launch Platform and Dashboard.

Labels: ,

2008年7月19日土曜日

金融アプリケーションとしてSaaSを採用

金融業界でSaaSが採用される話しはあまり登場しないが、下記記事はいくつか登場したベンダーを紹介している。
Geezo
Jwaaka
Mint
Wesabe
の4社はそれぞれ、複数のオンラインバンキングアプリケーションを統合してサービス化しようとするもの。 まだいづれも立ち上がりでしかないが、今後どのように成長/発展するか、注目する必要がある。

Banking as a Platform 2

Last week in Banking as a Platform, I discussed how banks might use the platform concept (for example as discussed by Tom Steinthal in a post called Some Thoughts on Platforms in Financial Services) to support radical improvements in customer experience and service.

Tom has now replied. In a post called Platforms - Are They Coming, he mentions a banking product called PNC Virtual Wallet. [PNC Bank Takes on Mint & Quicken with PNC Virtual Wallet, NetBanker, July 14th 2008]

The NetBanker article mentions several companies offering financial management platforms that apparently sit on top of (and aggregate) online services from regular banks. These financial management platforms include Geezeo, Jwaala, Mint, Wesabe. I haven't studied these in detail, but from a quick review of the material on their respective websites they look fairly similar, and a lot more like real platforms (according to the criteria stated in Tom's earlier post) than PNC Virtual Wallet. Although PNC deserves some praise for innovating at all, I can't see anything very radical in the PNC innovation.

Among the comments to the NetBanker article, I note contributions from Aaron Patzer (CEO of Mint) and Andrew Taylor (CTO of Jwaala). This is not the first time these two have clashed in public: in September, Andrew put a post onto the Jwaala blog called Hi I'm Mint. Ugg., which prompted a robust reply from Aaron.

Behind the rivalry between Mint and Jwaala is a fundamentally important difference in platform strategy. Mint appears to be selling to customers - "use our platform to get a better service over and above your existing bank accounts and other financial service providers". Whereas Jwaala appears to be selling to banks - "use our platform to provide better services to your customers". (Back in 2005, I noted a similar dilemma for software billing specialist LaCayla - whether to market its services upwards or downwards. There are some complex questions of platform strategy here, as I indicated in my post on two-sided markets over on the Asymmetric Design blog. There are also questions of trust.)

I really hope that innovations like these are successful, but there is a lot of work to do. Big banks like PNC may offer a watered-down and "safe" version of the innovation, but they might possibly have mixed feelings about the outcome. Meanwhile we can expect a lot of exciting stuff to be produced by small energetic companies with disputatious senior management; but it will be interesting to see how far they get with or without the active collaboration of any of the big banks.

2008年7月16日水曜日

Cloud Computing業界のキーベンダーを整理した一覧表。

Cloud Vendors A to Z (Revised)

By John | April 13, 2008

This list contains most of the vendors that have a presence in the cloud:

Cloud Vendor Level Type Status Cloud Provider Notes
3Tera 3 Server Provider Backbone 3Teras host solutions and provides software for other host providers
Adobe Air 1 Application Not a Provider Backbone Desktop play
Akamai 0 Server Not a Provider Software Based CDN
Amazon EC2 2 Server Provider Backbone
Amazon S3 2 Storage Provider Backbone
Amazon SimpleDB 2 Database Provider Backbone
Apache CouchDB 2 Database Not a Provider Software Based IBM is involved
Apache Hadoop 2 Database Not a Provider Software Based Hadoop is white-hot OSS enterprise search technology.
Areti Internet 0 Application Provider 3Tera
Box-Net 1 Storage Provider Backbone
Cassatt 0 Server Not a Provider Software Based Utility based computing. Provides a very strong provisioning play along with robust power management. Utility providers can worth within clouds or outside of clouds (e.g., enterprise infrastructures).
Citrix (XenSource) 0 Utility Not a Provider Software Based
CohesiveFT/ESOD 1 Utility Not a Provider Amazon EC2 Sort of like of like a cloud factory. ESOD is Elastic Server on Demand that can be used to create EC2 running images along with other platform images (e.g., Zen, VMWare, Parallels).
Dell DCS 2 Server Provider Backbone
EC2onRails 1 Utility Not a Provider Amazon EC2 A project offering that claims to allow deployment of a Ruby on Rails app on EC2 in five minutes
Elastra 1 Server Provider Amazon EC2 Primarily a MySQL/PostGreSQL play right now.
EMC Mozy 1 Storage Provider Backbone Cloud Services Play
Enki 1 Server Not a Provider 3Tera Heavier as a services player
Enomaly 1 Server Not a Provider Amazon EC2 Heavier as a services player. Also creates other platform images (e.g., Xen,KVM,Qemu,OpenVZ,VMware, EC2 and Hyper-v)
Enomoly ElastcDrive 1 Storage Not a Provider Amazon EC2
EnterpriseDB 1 Database Not a Provider Amazon EC2 Have a cloud offering
Flexiscale 2 Server Provider Backbone UK Based cloud provider
Fortress ITX 1 Server Not a Provider 3Tera
Google App Engine 2 Server Provider Backbone Closed framework cloud. Is based on Python, Django and others. The primary point is that it does not support frameworks based on PHP or Rails.
Google Apps 1 Application Provider Backbone Desktop play
Heroku 1 Utility Not a Provider Amazon EC2 Ruby on Rails cloud
HP AiaaS 2 Server Provider Backbone
IBM Blue Cloud 0 Server Provider Backbone Provisioning play
iCloud 1 Application Provider Backbone Desktop Cloud
Intridea/Scalr 1 Utility Not a Provider Amazon EC2 Scalr is an open source project designed to offer true elasticity and recovery for EC2.
Joyent 2 Server Provider Backbone Solaris based cloud
JungleDisk 1 Storage Not a Provider Amazon EC2 Low cost utility for S3
Layered Technology 1 Server Provider 3Tera A 3Tera mega partner
LongJump 1 Database Not a Provider Amazon EC2
Microsoft SSDS 1 Database Provider Backbone Competes w/Amazon SimpleDB
MorphExchange 1 Utility Not a Provider Amazon EC2 Ruby on Rails cloud
Mosso 2 Server Provider Rackspace Owned by by Rackspce
Nirvanix 1 Storage Provider Backbone Interesting hybrid of Cloud and CDN
Rackspace 0 Server Provider Amazon EC2
Rightscale 1 Server Provider Amazon EC2
Rpath/Rbuilder 1 Utility Not a Provider Amazon EC2 Similar to ESOD and Enomoly. Creates stack images.
Salesforce.com 0 Application Provider SaaS
Sun Caroline 2 Server Provider Backbone
Sun MySQL 1 Database Provider Backbone Not sure of plans
Terremark 0 Server Provider Backbone
VMWare 0 Utility Not a Provider Software Based
Weoceo 1 Utility Not a Provider Amazon EC2

————————————-

Level Description
0 Cloud Look-Alike
1 Cloud Guests
2 Cloud Hosts
3 Cloud Disruptor

Notes:
  1. All vendor solutions based on Amazon's AWS are classified as Beta because EC2, S3, and SimpleDB are all in Beta.
  2. RightScale has the potential to be a Level 3 provider due to their architecture

Also See … Demystifying Clouds

2008年7月15日火曜日

On PremiseソフトウェアとSaaSアプリケーションとを接続するツールを提供するベンダー

従来ののOn-Premiseソフトウェアアプリケーションと、SaaSアプリケーションとを統合する製品を提供するスタートアップが何社か搭乗している。
Boomi:
On-Premiseのアプリケーションを Boomi On Demandというサービスに接続すると、Boomiと契約しているSaaSアプリケーションと連携できる、というサービス。 既にSalesforce.com、NetSuite、Intacct、Taleo、OpSource、Zuoraがサポートされている。
SnapLogic:
社内のアプリケーションのデータと外部のSaaSアプリケーションとの間のデータ統合ツールを提供し、統合されたWebを構築できる製品を提供。 Salesforce.comやSugarCRMなどのCRM製品に加え、Amazon Web Services EC2との連携の最近発表した。
Cast Iron Systems:
社内のOn-Premiseアプリケーションと外部のSaaSアプリケーションを統合するアプライアンス製品を開発。 現在外部のSaaSアプリケーションとしてSalesforce.comとRightNowをサポートしている。

Three Startups To Solve SaaS Integration Problems


Boomi, SnapLogic, and Cast Iron are rolling out new offerings designed to help companies integrate software running in the cloud with onsite software.

While interest in SaaS continues to grow, CIOs are often tripped up by this question: How can I integrate a software service with my on-premises software?

Three startup companies this week announced how they are trying to solve this problem.

Boomi, which offers a SaaS integration service, announced Tuesday it had raised $4 million in its first round of venture capital funding from FirstMark Capital. Boomi says it has a patent-pending technology that lets it integrate customers' SaaS and on-premises software via the Web.

Once an application is connected to Boomi On Demand, it can operate with "hundreds of other" SaaS and on-premises apps that Boomi supports. Clearly, Boomi's success relies on its ability to get other software companies to play ball. It'll try to build momentum this fall with the offering of a software development kit that will let software vendors create connections to Boomi, with the sales pitch that vendors can focus less time on building SaaS integration layers for their software and more time on enhancing features.

Boomi says it already has a customer base of companies using SaaS from Salesforce.com, NetSuite, Intacct, Taleo, OpSource, and Zuora.

SnapLogic offers open source data-integration tools that map data from one source to another, letting companies create new types of Web applications and mashups, and also provides connectors to some SaaS sources, including Salesforce and SugarCRM. This week the company announced SnapLogic for EC2, a version of its technology that's designed to work for companies using Amazon.com's hosted computer processing service, called Amazon Elastic Compute Cloud.

Cast Iron Systems offers appliances (yes, hardware boxes) that are specifically programmed to let companies integrate onsite applications with a SaaS service. For example, one of its entry-level appliances will let a company integrate one of its applications with NetSuite; a higher-end, pricier appliance will let them integrate multiple apps with NetSuite.

Cast Iron also supports Salesforce and RightNow among SaaS vendors, and supports integration with the onsite software of a number of vendors, including Oracle, SAP, and Lawson. On July 21, Cast Iron is announcing its next generation of appliances, called Cast Iron iA4000. The series of appliances will include new data tools, online templates, configuration wizards, and improvements to usability.

2008年6月27日金曜日

IaaS(Infrastructure as a Service)を提供する Skytap社

IaaS(Infrastructure as a Service) と称する新たなクラウドコンピューティング環境を提供するベンダーとして登場したSkytap社のCEOとのインタビュー。  On Demandでハードウェア、ネットワーク、ストレージなど、システムのコンポーネントを仮想的に提供するサービスとしてIaaSは定義しているが、短時間で各種コンポーネントのConfigurationを変更できる点が特長、との事。
 
 

Cloud Computing and Virtualization

Jonathan Erickson
Infrastructure as a service

Joining us today is Scott Roza, CEO of Skytap, a company that provides cloud-based virtualization solutions as on-demand services over the Web.

DDJ: Scott, it seems there's something new every day in the virtualization and cloud computing arena. Where is it headed?

SR: The concept of cloud computing and how virtualization enables it offers so many innovation opportunities that it is not surprising there are new announcements every day. I think what customers need to do, however, is to not take announcements at face value, but instead dig into new product offerings to understand if something is really utilizing the full potential of virtualization and cloud computing. In many cases the collaboration, efficiency, high utilization, and productivity enabled by a combination of virtualization and cloud computing is not available because many firms are using fancy rebranding to create the appearance of innovation. I have seen many traditional providers make announcements over the last six months when in reality they are repackaging without the necessary innovation. In the end, innovation will win the hearts and minds of the customer, but today they need to work hard to separate the wheat from the chaff.

DDJ: What is "Infrastructure as a Service" (IaaS)?

SR: IaaS is the ability to provide computing resources -- processing power, network bandwidth, storage -- as a service. Some traditional hosting providers claim to have IaaS, but in reality they provision dedicated hardware to customers, put virtualization on top and call it IaaS. True IaaS offerings, however, are truly pay-as-you-go services that can be turned on and off at any time with almost no notice. When a provider has the ability to serve truly transient burst requirements, then they are capable of claiming they offer cloud-based, pay as you go IaaS.

DDJ A big trend in software development these days is collaboration. Does this overlap in any way with virtualization and cloud computing?

SR: Absolutely. At Skytap, we view a number of trends as creating a perfect storm for building and testing applications in the cloud. The trends include: 1) distributed development; 2) outsourced testing; 3) global test teams; 4) adoption of virtualization; 5) acceptance of SaaS delivery models; and 6) virtual machine sprawl. While these trends lend themselves to 24 hour development and rapid test feedback, they also lead to collaboration challenges, difficulty reproducing bugs in test environments, difficulty sharing virtual machine images, and slow VPN access to test labs. By using a cloud-based virtual test lab, browser-enabled role-based access creates seamless collaboration from anywhere in the world. All test and development teams share a common view of test platforms, test results, machine state at the instance of bug capture, and the ability to create simultaneous identical test stacks on demand.

DDJ: What are the challenge ahead for virtualization and cloud computing?

SR: The innovation will continue and there will be massive value created for customers over the next two to three years. However, the market may get overheated with hype and some customers will be over sold and become skeptical. The vision and potential of cloud-based virtualization is very real; but over the next 24 months there will be separation between those that truly deliver on the vision and those that just reposition the same way of doing business. As the separation occurs and leaders emerge, there will be consolidation and it will likely be lead by the biggest players such as Google, Amazon, VMWare, Citrix, Microsoft, HP, and IBM. Some of these big players will innovate -- Google, Amazon and VMWare are at the top of the list, some will quickly follow -- likely Citrix and Microsoft, and some will rely entirely on acquisition -- HP and IBM.

DDJIf readers want to find out more about these topics, is there a Web site you could point them to?

SR: Just as development and test organizations were the first to innovate with virtualization, we'll see those groups emerge as early adopters and leaders in cloud computing. For more information on how a truly on-demand, cloud-based virtual lab works readers can visit www.skytap.com.

2008年6月21日土曜日

VeriSign がデータセンタをヨーロッパに拡張

Verisign社が自社のデータセンターをヨーロッパに拡大し、上昇するDNSとSSL証明書のアクセスに対応する。  ちなみに2000年は一日に10億回のDNS Queryが現在は500億回を超えるとの事、特にヨーロッパでの成長がいちぢるしい。 

VeriSign Expands DNS Infrastructure in Europe

VeriSign, Inc. (VRSN) continues to invest in additional data center infrastructure to support the Internet domain name system (DNS). The company said today that it has deployed new data centers in Paris, France and Brussels, Belgium as part of Project Titan, its $100 million project to beef up its infrastructure.

VeriSign has continued its data center investment even as it refocuses its larger business by divesting non-core assets, including its Kontiki content delivery network. Domain names and SSL certificates will continue as the key business focus for the company, which also expanded heavily into mobile phone content (including the Crazy Frog ringtone).

In its latest move, VeriSign deployed new Regional Internet Resolutions Sites (RIRS) in Paris and Brussels. The company intends to have 100 RIRS locations around the globe by 2010 to support a 10-fold increase in the capacity of its global Internet infrastructure by 2010. VeriSign says the industrial-strength upgrades will provide better redundancy and reduced latency for DNS lookups that will improve the experience for users by reducing bottlenecks and increasing speed.

"VeriSign continues to roll out our infrastructure in key regions to meet the capacity, security and reliability demands of the future," said Ken Silva, chief technology officer, VeriSign. "By deploying a site in France, the more than 32 million Internet users will now have a faster and more reliable experience connecting to the .com and .net infrastructure. With our proven internal resources and our global network of providers in fast growing markets, VeriSign will continue to work to protect the .com and .net infrastructures against service disruptions, cyber attacks, and other vulnerabilities brought by massive growth."

Since 2000, the volume of Internet traffic on VeriSign's global infrastructure has increased from an average of 1 billion domain name system queries per day to a peak of more than 50 billion DNS queries per day under normal traffic conditions. Europe is the second largest region of DNS traffic and VeriSign is continually expanding its deployment of Regional Internet Resolution Sites in Europe and currently has several sites in Europe (in addition to France and Belgium) including: Germany, England, Sweden, Italy, Switzerland, Ireland and Poland.

Under Project Titan, VeriSign will increase its daily DNS query capacity from 400 billion queries a day to over 4 trillion queries a day and will increase the aggregate network bandwidth of its primary resolution centers around the world from more than 20 gigabits per second (Gbps) to greater than 200 Gbps per second.

2008年6月10日火曜日

Nirvanix社のオンラインストレージ事業

Nirvanix社がAmazon.comのS3(Simple Storage Sercice)に対抗してオンラインストレージ事業を展開。  Amazon社より200%データ転送速度が速い、と主張。
 

Nirvanix Takes Aim At Amazon.com Simple Storage Service (S3)

Nirvanix, an online storage provider, is making some interesting head-to-head claims against Amazon.com's Simple Storage Service (Amazon S3). Specifically, Nirvanix claims that its Storage Delivery Network offers downloads that are roughly 200 percent faster than S3. The data is based on testing done by 3Tera Inc.


Is Nirvanix really that much faster than Amazon S3? Perhaps it doesn't matter. By throwing some research out into the market and specifically mentioning Amazon.com S3, Nirvanix has search-engine optimized itself to compete more effectively against Amazon.com.

Anyone using Google Alerts for Amazon.com S3 will instantly discover Nirvanix's service now. Let's hope Nirvanix's technology is as good as the company's online marketing.

2008年6月6日金曜日

Oracle, IBM, SAP, Microsoft、Intuit社のSaaS戦略の整理

各社のSaaSに対する取り組み、戦略などを非常に簡潔に整理し、多数のリンクも整理した記事。  オフィスコンピュータで一時代を築いたDECがCompaqに買収されるまでにいたった経緯を例に新しい潮流に乗り遅れればどんなに大きい企業でも倒産の危機に陥るだろう、というのが作者のSaaSの位置づけ。 
 

How Oracle, IBM, SAP, Microsoft, and Intuit are Responding to the SaaS Revolution

In my previous blog entry, I discussed the possibility of a software giant failing to adapt to the SaaS revolution. I used the history of DEC as an example of how a highly successful company could miss a major shift in the market and capsize. This blog entry is a reference guide to what each of the major software vendors are doing in the SaaS space. I won't be sensational and predict the demise of any of these vendors. I think it's far too early to tell how the future will pan out.

I can say subjectively that I am impressed with Larry Ellison's pioneering efforts in the space. I can also say that SAP is currently the media whipping boy in the space, with delays in their Business ByDesign program costing them credibility. But this revolution is far from done, so let's not waste time trying to speculate the distant future.

Note: I am now an employee of Oracle, via the BEA acquisition

 

Oracle

Strategy

Larry Ellison, Oracle's CEO, has be talking about on demand software for a long time (10 years I believe), so it is clearly on his radar. In fact, he was an investor in both Salesforce and Netsuite, showing his belief in the business. Charles Phillips, Oracle President, has also spoken to the topic.

Larry and Charles Phillips have articulated a strategy on how Oracle can deliver SaaS and retain its focus on its core market (large enterprise). Larry does not intend to make a major push into the lower end of the SMB market.

Current SaaS Initiatives:

Oracle supports the following SaaS initiatives:

Weaknesses

Critics have primarily focused on the lack of end-to-end multitenancy in the On Demand business. The argument is that Oracle will not be able to provide a cost efficient solution unless the entire stack is multi-tenant.

Further reading:

 

Microsoft

Strategy

At an architectural level, Microsoft is promoting an S+S model, instead of a pure SaaS model. S+S stands for Software+Services. The idea with this is that Software as a Service is most useful when pared with local software (like Office). Microsoft obviously has a major incentive to make sure desktop software is not left behind in the SaaS world, so this makes for good strategy. Whether consumers will buy into it is another matter. See the weaknesses section below for more on this topic.

Current SaaS Initiatives

The following is a selection of  the SaaS offerings from MSFT:

  • SaaS On-Ramp Program - aids ISVs in building out SaaS solutions
  • Microsoft Online Services - its businesss applications ondemand offering
    • Hosted versions of Exchange, Sharepoint, and LiveMeeting
    • Dynamics CRM Live - hosted version of the Dynamics CRM offering
  • Windows Live - a family of hosted offerings for the small business/consumer
    • Live Mesh - touted as a SaaS solution, it currently is just a file synchronization service
    • Messenger (IM), Windows Live ID, Virtual Earth, Search, Spaces (blogs), and Gadgets
  • Architect Center - provides architectural guidance for ISVs
    • Lead by Gianpaolo Carraro and Fred Chong
    • Have produced a SaaS reference application, LitwareHR
    • While some of what they write is MSFT centric, most of the articles are generally applicable
    • As an architect myself, I admire the work that they do

There are more services listed here, but not all are really SaaS.

Weaknesses

Critics contend that Microsoft will struggle to succeed in the SaaS market while preserving its existing franchises. It already stumbled with its business model when a European partner began offering Office as a service:

Its Office franchise is already being eroded by service based offerings (Google Apps, Zoho, Adobe, etc). Somehow it has to prevent Office revenue from being decimated by pure SaaS players.

 

IBM

Strategy

Searching for interviews on SaaS with IBM's CEO Sam Palmisano or VP of Software Steve Mills does not bring up much of interest. This is a bit alarming, remembering the lessons from my previous DEC  post. Of the 5 major software giants covered here, IBM appears to have the least amount of executive mindshare for SaaS.

I am not the only one who sees this: Larry Barrett wrote an entire article analyzing IBM's apparent sluggishness when it comes to SaaS. While I don't see a high level business strategy, IBM has embarked on some SaaS initiatives, covered in the next section.

Current SaaS Initiatives:

IBM has these intiatives:

Weaknesses

As Larry Barrett noted, IBM doesn't appear to be aggressively pursuing the SaaS model. Sure, it has some initiatives going, but for the size of IBM those initiatives seem undersized.

Also, Jeff Nolan has pointed out that IBM lacks the business apps necessary to execute on an effective SaaS strategy.

Further reading:

 

SAP

Strategy

SAP CEO Henning Kagermann helped launch the major SAP SaaS initiative: Business ByDesign which is a hosted version of several of SAP's traditional heavy weight business applications. The intent was to target SMB, but due to problems in execution that strategy may be changing. It also plans to be a SaaS hybrid, with some on-premise software in the mix.

The bright spot for SAP and SaaS comes from its acquisition of Business Objects (BOBJ). BOBJ was already offering Crystal Reports at the time of the acquisition, and appears to be a healthy business.

Current SaaS Initiatives

SAP has three major initiatives:

Weaknesses

By far the biggest perceived weakness with SAP is its failure to execute on its much publicized SaaS release (BBD). Critics point to the major delays (possibly 24 months) as a sign that SAP's applications are a poor fit for the SaaS model. Worse, SAP validated the concept to its customers but failed to deliver, providing key advantage to competitors like NetSuite.

  • Loraine Lawson: SAP's SaaS Is Dead. Long Live SAP's SaaS.
  • Dennis Howlett: SAP Business By Design likely to be delayed
  •  

    Further reading:

     

    Intuit

    Strategy

    CEO Brad Smith isn't the most vocal about SaaS, but his company is doing the talking for him. Intuit is clearly pushing the SaaS model, with major product offerings already available. The strategy appears to be simple: offer online equivalents of their product suite:

    Current SaaS Initiatives

    Intuit offers the following products as SaaS offerings:

    Weaknesses

    I haven't seen any weaknesses other than stiff competition. The space Intuit plays in will become crowded, with Netsuite and Intacct already delivering SaaS, and Sage likely to become a contender as well.

    LinedIn社のアーキテクチャ

    企業向けのSNSとして米国の市場で一番登録者数の多いサイトで、最近日本にも展開を図っているLinkedIn社のバックエンドシステムの概要がJavaOne 2008で公開された。  Sun Solarisの大規模なシステムで、Javaをベースとしたプログラミング主体をなしている。  当初は一つのサーバだったものが順次分散化システムに展開していく様子が非常にわかりやすく説明されている。  SNSサイトとして重要なサーチエンジンがボリュームの増大とともに独立システムとして分化していく点が特徴である。 
     

    LinkedIn Architecture

    At JavaOne 2008, LinkedIn employees presented two sessions about the LinkedIn architecture. The slides are available online:

    These slides are hosted at SlideShare. If you register then you can download them as PDF's.

    This post summarizes the key parts of the LinkedIn architecture. It's based on the presentations above, and on additional comments made during the presentation at JavaOne.

    Site Statistics

    • 22 million members
    • 4+ million unique visitors/month
    • 40 million page views/day
    • 2 million searches/day
    • 250K invitations sent/day
    • 1 million answers posted
    • 2 million email messages/day

    Software

    • Solaris (running on Sun x86 platform and Sparc)
    • Tomcat and Jetty as application servers
    • Oracle and MySQL as DBs
    • No ORM (such as Hibernate); they use straight JDBC
    • ActiveMQ for JMS. (It's partitioned by type of messages. Backed by MySQL.)
    • Lucene as a foundation for search
    • Spring as glue

    Server Architecture

    2003-2005

    • One monolithic web application
    • One database: the Core Database
    • The network graph is cached in memory in The Cloud
    • Members Search implemented using Lucene. It runs on the same server as The Cloud, because member searches must be filtered according to the searching user's network, so it's convenient to have Lucene on the same machine as The Cloud.
    • WebApp updates the Core Database directly. The Core Database updates The Cloud.

    2006

    • Added Replica DB's, to reduce the load on the Core Database. They contain read-only data. A RepDB server manages updates of the Replica DB's.
    • Moved Search out of The Cloud and into its own server.
    • Changed the way updates are handled, by adding the Databus. This is a central component that distributes updates to any component that needs them. This is the new updates flow:
      • Changes originate in the WebApp
      • The WebApp updates the Core Database
      • The Core Database sends updates to the Databus
      • The Databus sends the updates to: the Replica DB's, The Cloud, and Search

    2008

    • The WebApp doesn't do everything itself anymore: they split parts of its business logic into Services.
      The WebApp still presents the GUI to the user, but now it calls Services to manipulate the Profile, Groups, etc.
    • Each Service has its own domain-specific database (i.e., vertical partitioning).
    • This architecture allows other applications (besides the main WebApp) to access LinkedIn. They've added applications for Recruiters, Ads, etc.

    The Cloud

    • The Cloud is a server that caches the entire LinkedIn network graph in memory.
    • Network size: 22M nodes, 120M edges.
    • Requires 12 GB RAM.
    • There are 40 instances in production
    • Rebuilding an instance of The Cloud from disk takes 8 hours.
    • The Cloud is updated in real-time using the Databus.
    • Persisted to disk on shutdown.
    • The cache is implemented in C++, accessed via JNI. They chose C++ instead of Java for two reasons:
      • To use as little RAM as possible.
      • Garbage Collection pauses were killing them. [LinkedIn said they were using advanced GC's, but GC's have improved since 2003; is this still a problem today?]
    • Having to keep everything in RAM is a limitation, but as LinkedIn have pointed out, partitioning graphs is hard.
    • [Sun offers servers with up to 2 TB of RAM (Sun SPARC Enterprise M9000 Server), so LinkedIn could support up to 1.1 billion users before they run out of memory. (This calculation is based only on the number of nodes, not edges). Price is another matter: Sun say only "contact us for price", which is ominous considering that the prices they do list go up to $30,000.]

    The Cloud caches the entire LinkedIn Network, but each user needs to see the network from his own point of view. It's computationally expensive to calculate that, so they do it just once when a user session begins, and keep it cached. That takes up to 2 MB of RAM per user. This cached network is not updated during the session. (It is updated if the user himself adds/removes a link, but not if any of the user's contacts make changes. LinkedIn says users won't notice this.)

    As an aside, they use Ehcache to cache members' profiles. They cache up to 2 million profiles (out of 22 million members). They tried caching using LFU algorithm (Least Frequently Used), but found that Ehcache would sometimes block for 30 seconds while recalculating LFU, so they switched to LRU (Least Recently Used).

    Communication Architecture

    Communication Service

    The Communication Service is responsible for permanent messages, e.g. InBox messages and emails.

    • The entire system is asynchronous and uses JMS heavily
    • Clients post messages via JMS
    • Messages are then routed via a routing service to the appropriate mailbox or directly for email processing
    • Message delivery: either Pull (clients request their messages), or Push (e.g., sending emails)
    • They use Spring, with proprietary LinkedIn Spring extensions. Use HTTP-RPC.

    Scaling Techniques

    • Functional partitioning: sent, received, archived, etc. [a.k.a. vertical partitioning]
    • Class partitioning: Member mailboxes, guest mailboxes, corporate mailboxes
    • Range partitioning: Member ID range; Email lexicographical range. [a.k.a. horizontal partitioning]
    • Everything is asynchronous

    Network Updates Service

    The Network Updates Service is responsible for short-lived notifications, e.g. status updates from your contacts.

    Initial Architecture (up to 2007)

    • There are many services that can contain updates.
    • Clients make separate requests to each service that can have updates: Questions, Profile Updates, etc.
    • It took a long time to gather all the data.

    In 2008 they created the Network Updates Service. The implementation went through several iterations:

    Iteration 1

    • Client makes just one request, to the NetworkUpdateService.
    • NetworkUpdateService makes multiple requests to gather the data from all the services. These requests are made in parallel.
    • The results are aggregated and returned to the client together.
    • Pull-based architecture.
    • They rolled out this new system to everyone at LinkedIn, which caused problems while the system was stabilizing. In hindsight, should have tried it out on a small subset of users first.

    Iteration 2

    • Push-based architecture: whenever events occur in the system, add them to the user's "mailbox". When a client asks for updates, return the data that's already waiting in the mailbox.
    • Pros: reads are much quicker since the data is already available.
    • Cons: might waste effort on moving around update data that will never be read. Requires more storage space.
    • There is still post-processing of updates before returning them to the user. E.g.: collapse 10 updates from a user to 1.
    • The updates are stored in CLOB's: 1 CLOB per update-type per user (for a total of 15 CLOB's per user).
    • Incoming updates must be added to the CLOB. Use optimistic locking to avoid lock contention.
    • They had set the CLOB size to 8 kb, which was too large and led to a lot of wasted space.
    • Design note: instead of CLOB's, LinkedIn could have created additional tables, one for each type of update. They said that they didn't do this because of what they would have to do when updates expire: Had they created additional tables then they would have had to delete rows, and that's very expensive.
    • The used JMX to monitor and change the configuration in real-time. This was very helpful.

    Iteration 3

    • Goal: improve speed by reducing the number of CLOB updates, because CLOB updates are expensive.
    • Added an overflow buffer: a VARCHAR(4000) column where data is added initially. When this column is full, dump it to the CLOB. This eliminated 90% of CLOB updates.
    • Reduced the size of the updates.

    [LinkedIn have had success in moving from a Pull architecture to a Push architecture. However, don't discount Pull architectures. Amazon, for example, use a Pull architecture. In A Conversation with Werner Vogels, Amazon's CTO, he said that when you visit the front page of Amazon they typically call more than 100 services in order to construct the page.]



    The presentation ends with some tips about scaling. These are oldies but goodies:

    • Can't use just one database. Use many databases, partitioned horizontally and vertically.
    • Because of partitioning, forget about referential integrity or cross-domain JOINs.
    • Forget about 100% data integrity.
    • At large scale, cost is a problem: hardware, databases, licenses, storage, power.
    • Once you're large, spammers and data-scrapers come a-knocking.
    • Cache!
    • Use asynchronous flows.
    • Reporting and analytics are challenging; consider them up-front when designing the system.
    • Expect the system to fail.
    • Don't underestimate your growth trajectory.

    2008年6月4日水曜日

    Virtual Iron社と 2X社が戦略的提携

    Thin Client技術を開発する 2X社と仮想化技術のVirtual Iron社が戦略的提携を組み、VDI
    (Virtual Desktop Infrastructure)とApplication Publishingソリューションを提供する事を表明。 
     
     

    Virtual Iron And 2X Hook Up For Strategic Alliance

    2X, provider of Thin Client and Server Based Computing Software, and Virtual Iron have announced a strategic alliance to provide a complete Virtual Desktop Infrastructure (VDI) and Application Publishing Solution.

    Virtual Iron

    2X

    The 2X / Virtual Iron virtual desktop infrastructure (VDI) solution hosts individual Windows desktop PCs inside virtual machines running on servers in the data center. According to the join press release, this thin-client architecture is significantly easier to secure, maintain and support and it enables an organization's complete Windows desktop environment to be securely accessed and serviced centrally.

    The joint solution enables a fully isolated, customizable and secure environment where users are able to work with standard desktop operating systems and applications. Virtual desktops can be user-customized and provisioned on demand instantly, providing performance and user experience that are comparable to a desktop personal computer. This allows enterprises to replace physical desktops with virtual desktops for many usage scenarios such as call centers, offshore development, and secure, remote access.

    2008年6月3日火曜日

    Sun Microsystems社の クラウドコンピューティングサービス、 Project Hydrazine

    Amazon社のEC2、S3や、Nirvanix社の提供するクラウドコンピューティングがデータセンタ事業の事業として広がっている。  Sunが同様のサービスで "Project Hydrazine" と呼ばれるサービスを発表し、提供し始めた。  自社のシステム技術、特に自社のハードウェア、仮想化技術、ディレクトリ技術、Java環境を組み合わせ、アプリケーションの開発、運用を容易にするサービスの提供であり、他社のように複数ベンダーの技術を集約したものと異なり、統合された環境であることが"売り" 担っている様子。

    Project Hydrazine to fuel Sun's computing cloud venture

    In the realm of cloud computing, Sun Microsystems is creating its own environment which will allow designers and developers to collaborate, create, and run products in Sun's infrastructure.  Code named  "Project Hydrazine" , the announcement was made at the JavaOne conference by Sun CTO Robert Brewin.  Brewin believes, much like the hydrazine that fuels the space shuttle into orbit, this new project will help to power user's applications to astronomical levels.

    Cloud-computing was first introduced in 2007.  Large companies like Microsoft, Amazon, Yahoo, Google, and IBM had vast hardware and network resources. They decided to rent out space that wasn't needed to small companies who lacked the money and/or resources to sustain a similar infrastructure.  Data could be stored over various servers or even virtual servers and retrieved quickly by business and consumer alike.  The major differences between cloud-computing and a data center lie in the remote location of the servers, the fact that the infrastructure itself is not owned by the company using it, and that the management tasks are are automated.

    Two of the current players in the cloud-computing market are Amazon and Nirvanix.  As Talkibie discussed last month, Amazon's EC2 and S3 services offer businesses an area to store, work, and host their information, and deploy programs and applications.  Nirvanix's cloud focuses more on storage and claims "businesses are guaranteed a shorter time-to-market, reduced costs, and also benefit from better flexibility and control for their operations." 

     

    So what makes Project Hydrazine so special?  Sun Microsystems is offering the hardware, the network environment, JavaFX rich Internet application technology, GlassFish application server, Sun enterprise service bus, Sun Directory server, MySQL, and "cheap storage".  It is also including a module called "Project Insight", an effort to implement JavaFX technology to enable two-way conversations with consumers, including providing advertising. Sun is also, wisely, staying out of the designer tools development realm and partnering with Adobe to bring trusted toolsets into their repertoire.  As a final touch, Project Hydrazine offers a mechanism which will help sync a person's devices with the applications and data stored on them, much like Microsoft Live Mesh.  Overall, Sun is promising one stop shopping for all your designing, storage, and programming needs with the added incentive of a monetization tool to make every customer interaction more profitable and highly accessible.

    Start up businesses often have a long battle ahead of them.  Each dollar spent has to be evaluated for the return it will get.  With the ability to rely on cloud computing, small businesses are able to operate at enterprise levels for a fraction of the cost.  No need to worry about the overhead costs in creating an IT infrastructure and hiring the personnel to maintain it.  If Project Hydrazine can deliver on its promises, the only thing separating a business from the Fortune 500 list is a good idea.

    2008年5月29日木曜日

    eBayのデータセンターのアーキテクチャ

    eBayのRandy Shoup氏がeBayのサーバアーキテクチャについて説明したプレゼンテーションが公開されている。  2.12億人のユーザ、2ペタバイトのデータ、1億以上の商品を扱うために一日に50億個のAPIコールを受けるシステムにとって、Scalabilityは深刻な用件となる。  また、新規機能を従来のシステムを止める事無くエンハンスを継続的に行う事も重要な課題となる。 
     
    リンクはここ

    2008年5月24日土曜日

    SaaSシステム向けの課金請求、回収システムのベンダー

    Zuora社とAria Systems社、という2社の紹介。
     

    Billing Enters the SaaS Era

    9:09 am New Tech, Tech Industry

    One of the things that I have been working on recently is research for billing systems for SaaS companies. One project I have been working on recently has the eventual need for billing for the SaaS offerings they will be releasing soon. The challenge has been the multi-tiered nature of the billing solution that is needed. Becuase of that, we came up with a naming system to minimize the confusion:

    • Patrons are the customers of the SaaS provider.
    • Customers are the customers of the Patrons

    Not only must the solution handle billing for the SaaS provider's patrons, but also handle billing pass through for the patron to charge their customers. And that pass through billing could be services or product based with each patron having a slightly different product offering.

    The initial thought was that this would have to built internally, maybe using a combination of Sugar CRM and osCommerce. The problem was that we realized we would need to do too much meatball surgery on these systems to really get what we wanted. Also, we don't need a full fledged CRM system, just a light customer database (at least initially, boiling the ocean was something we were fighting even though we could see the need for it down the road). Then on top of all this, we still needed to work with a payment system to run the transactions for us. We really didn't want to store credit card numbers on the system as we wanted to avoid all PCI headaches.

    What was needed was a service that would take care of all this for us!

    Enter two SaaS based billing solutions Zuora and Aria Systems. Both companies generally do the same thing: provide a SaaS based billing solution that can be used by SaaS, subscription based companies.

    Aria Systems has been around for a bit longer but been growing more organically and, I think due to their being based out of Philadelphia and not having expanded their sales force until just recently, not as well known. They have a much more mature billing service which can be co-branded or embedded via APIs into an existing SaaS service. The main downside that I see to their current business model is that they are only interested in doing business with companies that have an existing revenue stream. Primarily because of the high cost of configuring a client to use their system. They don't appear to have embraced the SaaS model internally from the fact of allowing a small early grown company to sign up on a small pay as you go model and then enable that company to learn from self help documentation on implementing the system. Thus, I feel they are likely to miss the rising tide of young companies being successfully and riding that success.

    Zuora recently came out of stealth mode to announce their offering. I know a number of talented people who have gone over to Zuora and from what I have learned pre-launch and since from their website, it looks like at the core they offer the same thing as Aria Systems. However, the company was founded by poeple who came from the SaaS space, they claim to understand the new and expanding needs that these companies have and will have. It appears that their system is designed to provide flexibility for the SaaS provider to adapt their service offerings as well as run analytics across it. Something that Aria Systems, doesn't talk up very much. Since they are still fresh out of the gate, I don't know if they suffer from the same problem as Aria: not focused on seeding the market with self service, pay as you consume offering that can be used by startups. Their "web 2.0″ feel definitely gives them an advantage from initial impression alone.

    I'm anxious to learn more about Zuora's capabilities and hope that it will be the silver bullet for the SaaS project I am working on. As I get more exposure to their offering, I will share my experience.