一些基于Web的IM技术和产品
几个开源的支持Comet的Library:
Orbited :一种开源的分布式Comet服务器
AjaxMessaging :Ruby on Rails的Comet插件
Pushlets :一个开源框架,可以让服务器端java对象推送事件到浏览器端javascript,java applet,或者flash应用程序
Lightstreamer :提供基于AJAX-COMET模式的HTTP流的商业实现
Pjax :Ajax的推送技术
几款在线IM软件:
1、Meebo–支持AIM、ICQ、Yahoo! Messenger、Jabber、Gtalk和MSN多种IM平台。提供中文界面,速度较快。注册后可以同时添加多个不同类型的IM帐户,支持IE和FireFox。另外,如果你使用的是Flock的话,通过一个插件可以让Meebo与Flock相结合(见这里),使用更加方便。
2、Mabber–提供的IM平台与Meebo差不多,同样都支持AIM、ICQ、Yahoo! Messenger、Jabber、Gtalk和MSN等。Mabber目前还没有中文界面,而且速度也比较慢,它必须注册一个帐号后才能使用,不像Meebo那样在前台提供独立的IM登录口。同样支持IE和FireFox,目前还处于Beta阶段。
3、Ebuddy–目前只提供MSN、Yahoo和AIM三种IM平台,而且它无需注册,直接在前台提供每个IM的登录口,它的特色在于提供了与IM软件相类似的使用界面,操作方便、支持IE和FireFox。另外一个特色在于,它还提供WAP登录界面、也就是说可以通手机来登录到IM平台,这样无论走到哪都能与网友进行沟通。

4、AIM Express–这是AIM提供的独立在线客户端,也就是说它只支持AIM的即时通软件。
5、MSN Web Messenger–与AIM Express相类似,由微软提供的一款MSN独立在线客户端。

6、ICQ2GO–ICQ公司提供的ICQ独立在线客户端,使用JAVA技术。

7、JWChat–一个基于web的Jabber客户端。它其实是一个开源软件,你可以下载后在自已的服务器上安装,提供在线IM应用服务,当然它也提供了一个在线DEMO,你可以试用它的功能。
8、KoolIM–最新发现的一个,与Meebo类似,提供AIM、ICQ、Yahoo! Messenger、Jabber、Gtalk和MSN多种IM平台,并且在前台就可以多帐号同时登录。你也可以注册一个帐号后把多个IM帐号集成在一起。支持IE和Firefox。(via Web2.0Fan.net)
9、Imhaha–也是与Meebo非常相似的一个在线IM服务,不过关键在于它支持QQ,详细介绍见PARK17的QQ也web-based。
10、RadiusIM–又是一个与Meebo相类似的基于web的IM客户端,它支持AIM、Yahoo messager!、MSN和Gtalk四种IM,使用Ajax技术构建。
MySQL数据库Sharding存在的一些解决方案
MySQL数据库Sharding存在的一些解决方案-MySQL Database Sharding Existing solutions
At the moment Netlog is the 67th most visited website in the world, according to Alexa's ranking. This means that there's at least 66 other websites out there probably facing similar problems as we do. 16 of the 20 most popular websites are powered by MySQL so, we are definitely not alone, are we?
Let's have a look at some of the existing technologies that implement or are somehow related to sharding and scaling database sysems, and let's see which ones could be interesting for Netlog.
MySQL Cluster is one of the technologies you could think would solve similar problems. The truth is that a database cluster is helpful when it comes to high availability and performance, but it's not designed for the distribution of writes.
MySQL Partitioning is another relatively new feature in MySQL that allows for horizontal splitting of large tables into smaller and more performant pieces. The physical storage of these partitions are limited to a single database server though, making it not relevant for when a single table grows out of the capacities of a single database server.
HSCALE and Spock Proxy, that both build on MySQL Proxy, are two other projects that help in sharding your data. MySQL Proxy introduces LUA, as an extra programming language to instruct the proxy (for eg. finding the right shard for this query). At the time we needed a solution for sharding neither of these projects seemed to support directory based sharding the way we'd wanted it to.
HiveDB is a sharding framework for MySQL in Java, that requires the Java Virtual Machine, with a php interface currently being in an infancy state. Being a Java solution makes it less interesting for us, since we prefer the technologies we are experts in and our application is written in: php.
Other technologies that aren't MySQL or php related include HyperTable (HQL), HBase, BigTable, Hibernate Shards (*shivers*), SQLAlchemy (for Python), Oracle RAC, etc ... The memcached SQL-functions or storage engine for MySQL is also a related project that we could mention here.
None of these projects really seemed to come in line with our requirements. But what exactly are they?
- Flexible for the hardware department.
We project growth and want the sharding system to be flexible. Knowing that our traffic will increase, we need to be able to add more shards quickly. With a growing amount of data, a proportional growth in hardware is requested. For this reason we opt for a directory based partitioning scheme. - No massive rewrite.
We can't introduce a whole new database layer or incompatible abstraction layer. We want to keep on using our database class as we are doing now and only implement sharding for those features that really require that amount of scaling. That's why we've opted for a solution that builds on what we have and allows for incremental implementation. We also wanted to use the sharding API, without having the data to be physically sharded, so the development and IT departments can independently decide when to do their part of the job. - Support for multiple sharding keys.
Most of our data will probably be sharded on $userID, but we want the system to be flexible so we can implement other keys and/or sharding schemes too. - Easy to understand.
We can't expect each and every of our developers to know everything about scalability and performance. Even if this was the case, the API to access and store data in a sharded environment should make it transparent to them so they shouldn't care about performance and can focus on what's really fun to do: developing and improving on features.
So, it's best if the API is a php API which makes it easy for them to use in the rest of our application.
