Here I discuss how can you use multiple languages in a single application. Also I show main dark spots you will have on your way.

1. 0

2. Apache Thrift
Ruby + Java + .Net = ♥

7. People are using different
languages
• Language-specific features
• Performance and stability
• Development speed
• You are bored

8. Developers are lazy
• Crossplatform
• Easy integration
• Low transmission
overhead
• Bindings

9. Protocol Buffers
Avro
Fast BuffersM
essagePack
ASN.1
REST API
RPC
SOAP/WSDL
ZeroC ICE
SDXF
Caucho's Hessian
IDL
BPC

11. REST API

12. REST is good, but slow and
sometimes it fails
• Easy to setup
• Crossplatform
• Serialization overhead
• No endpoint validation

13. APACHE THRIFT

14. Thrift is silver-bullet, but you
have to use your brain first
• Low serialization overhead
• Endpoint validation
• Generates bindings
• Takes some time to setup

15. Simple steps to ZEN
• Create .thift file
• thrift --gen
<language> <tfile>
• Include bindings
• You are ready to go!

16. calculator.thrift
service Calculator extends shared.SharedService {
void ping(),
i32 add(1:i32 num1, 2:i32 num2),
i32 calculate(1:i32 logid, 2:Work w) throws
(1:InvalidOperation ouch),
oneway void zip()
}

17. Podozritelnie Tipy
• bool
• byte
• i16, i32, i64
• double
• string
• list<t1>
• set<t1>
• map<t1,t2>

18. You should count
arguments carefully
namespace java msg
namespace rb msg
typedef i32 MyInt
service Messenger
{
MyInt createMessage {
1: required i32 userId;
2: required string userName;
3: required string text;
4: optional MessageType messageType =
MessageType.DEFAULT_TYPE
23: optional string language = "english"
}
}

19. Generate bindings
thrift -r --gen ruby messenger.thrift

23. It takes only 5 LOC to create
server

24. Thrift client is also easy to
use

26. Conclusion
• REST API vs Thrift
• Supported languages
• Endpoint validation
• Auto-generated bindings

27. • y.kaliada@rubyroidlabs.com
• Skype: y.koleda
• LinkedIn: linkd.in/1uQCnsq