Tips for thrift

简介: Introduction I have designed and developed game servers successfully with thrift (http://thrift.apache.

Introduction

I have designed and developed game servers successfully with thrift (http://thrift.apache.org/). I am writing here some tips to share my experience. I hope that this will help someone who is just trying to solve the same problems that I have met.

Background

Thrift is mainly for scalable cross-language services development ( what it's website has written).Someone may mention Google ProtocolBuff. I have used ProtocolBuff some projects. However, I like thrift more than Google protocolbuff. There are two reasons:

  • Thrift support array and map. That is so nice.
  • The Codes that thrift framework generated are much more readable just like which I writes them myself.

When developing MMO Server, I use messages to communicate with client which is may implemented by different language e.g., as3. So thrift is very suitable for interchange messages. But there is another circumstance to use thrift.As you know the part of the logic of game server, is modified frequently. Along with project progressing, More property will be added to player object or sub structure. So we will add more fields or rows to db for storing extra data. With version issues being considered, that's much more annoying. I create a blob field to db table that stores a thrift object. With advantages of version supporting, It's easy to add more property to player.

Flash AS3 Wrap

Thrift is originally designed for RPC. How it works for RPC is easy to find if you Google it. I will not write more for this part. But there is less articles to introduce how thrift can be used to communicate message in real time system. Thrift support as3 but just for RPC. So I add some files for supporting message communicating. That another reason why I like thrift that the codes are so readable that it's so easy to extend thrift. Though I am not a professional as3 engineer (I am professional in C++), I implement that easily. I implement two functions to wrap serialization and deserialization.

public class FFUtil  {
        
    public static function EncodeMsg(msg:TBase, ba:ByteArray):void
    {
        var tran:FFMemoryTransport = new FFMemoryTransport(ba);
        var proto:TBinaryProtocol  = new TBinaryProtocol(tran);
        msg.write(proto);
    }
    public static function DecodeMsg(msg:TBase, ba:ByteArray):Boolean
    {
        var tran:FFMemoryTransport = new FFMemoryTransport(ba);
        var proto:TBinaryProtocol  = new TBinaryProtocol(tran);
        msg.read(proto);
        return true;
    }
}

 

I have uploaded flash_example.zip file which includes my extending as3 lib files and a exampl.as file. Actually it's a chat tutorial application using thrift.

C++ Wrap

There are some dissatisfied aspects in thrift C++ implement codes that they depend boost library. Generally it's not a big problem as most of C++ projects have been using boost. But someone who just want to integrate thrift easily finds it annoying. In some mobile app project with C++, they will not want to depend boost too. Actually I don't find good enough reason to must implement thrift of C++ version with boost. Most of use of boost in thrift are for assert test and smart pointer. Thanks to readable codes, I find it easy to wipe dependency of boost. Actually I still recommend you to use official version. But if you just want try thrift as soon as possible you can try this version of no boost. By the way, this C++ version of no boost supports binary encoding only.

int main(int argc, char **argv)
{
    shared::SharedStruct msg, dest;
    msg.value = "nihao";
    std::string data;
    ffthrift_t::EncodeToString(msg,  data);
    printf("data size=%u\n", data.size());
    ffthrift_t::DecodeFromString(dest, data);
    printf("dest value=%s\n", dest.value.c_str());
    return 0;
}

 

I have uploaded ffthrif_cpp_example.zip file which includes my extending C++ files and a example file.

For Storing

I use MySQL. There I show the model of game structure as an example. For storing players' data I design a table named player_info for players' base property such as level, gold, exp...

The field of Extra_Data is special and important. It is a blob type for storing thrift. For example, I design a such thrif file:

namespace cpp ff
namespace as3 ff
namespace py ff
struct extra_data_t {
  1: list<i32> val1
  2: string    val2
  3: map<i32, string> val3
}

 

thrift-0.9.0.exe -gen cpp msg_def.thrift

I will store  extra_data_t to field of Extra_Data. There are such features:

  • Because of supporting of version, we can add more field to  extra_data_t but not to modify MySQL table structure. We have hundreds of game server so that we always update some of server first, if anything is ok, we make all servers updated to newest version. Thrift and blob make us agile enough to handle these situations. We don't need to modify db frequently and the part of db operations is stable.
  • Thrift supports list and map which it's convenient for us and it‘s codes are very readable, we can use extra_data_t as base structure of player_t class.

But we must use thrift properly. If you chose to store thrift object to db blob, you will give up query this field by SQL. So my tips are:

  • store those field as base type of db that needs to be queried by SQL. Such as level, exp, gold, socre...
  • store those field in thrift object that don't needs to queried by SQL. Though thrift object in db blob can't be queried by SQL, not mean it can be queried no way. Thanks to thrift supporting for lots of languages, thrift objects can be queried by scripts. We developed some web pages with PHP to show data from db.

Summary

  • Actually here thrift is a serialization and deserialization framework other than RPC framework.
  • RPC mechanism doesn't fit for me. I just use thrift to gen message that supports version.
  • With supporting version, thrift can be used in db storing data. We will get more agile by storing thrift object in db blob.
  • file download: http://www.codeproject.com/Articles/660671/Tips-for-thrift-Message-and-store
目录
相关文章
|
缓存 NoSQL 关系型数据库
从0开始回顾Redis---系列一
基础 1、Redis是什么?简述它的优缺点? Redis是用 C 语言开发的一个开源的高性能键值对(key-value)内存数据库。经常被用来做缓存,消息队列,分布式锁。 Redis 提供了多种数据类型来支持不同的业务场景,如 字符串(strings),散列(hashes), 列表(lists), 集合(sets), 有序集合(sorted sets)与范围查询。 Redis 还支持事务 、持久化、Lua 脚本、多种集群方案。 优点: ● 读写性能极高, Redis能读的速度是110000次/s,写的速度是81000次/s。 ● 支持数据持久化,支持AOF和RDB两种持久化方式。 ●
|
JSON 前端开发 数据格式
react中请求接口的封装
1. 新建一个dva项目。使用antd 或者antd-mobile组件库。 $ npm install dva-cli -g $ dva -v $ dva new dva-quickstart $ npm start $ npm install ...
2101 0
|
5天前
|
数据采集 人工智能 安全
|
15天前
|
云安全 监控 安全
|
1天前
|
存储 SQL 大数据
删库跑路?别慌!Time Travel 带你穿回昨天的数据世界
删库跑路?别慌!Time Travel 带你穿回昨天的数据世界
236 156
|
8天前
|
SQL 自然语言处理 调度
Agent Skills 的一次工程实践
**本文采用 Agent Skills 实现整体智能体**,开发框架采用 AgentScope,模型使用 **qwen3-max**。Agent Skills 是 Anthropic 新推出的一种有别于mcp server的一种开发方式,用于为 AI **引入可共享的专业技能**。经验封装到**可发现、可复用的能力单元**中,每个技能以文件夹形式存在,包含特定任务的指导性说明(SKILL.md 文件)、脚本代码和资源等 。大模型可以根据需要动态加载这些技能,从而扩展自身的功能。目前不少国内外的一些框架也开始支持此种的开发方式,详细介绍如下。
599 5
|
11天前
|
人工智能 自然语言处理 API
一句话生成拓扑图!AI+Draw.io 封神开源组合,工具让你的效率爆炸
一句话生成拓扑图!next-ai-draw-io 结合 AI 与 Draw.io,通过自然语言秒出架构图,支持私有部署、免费大模型接口,彻底解放生产力,绘图效率直接爆炸。
773 152