Book Image

Learning Apache Thrift

Book Image

Learning Apache Thrift

Overview of this book

With modern software systems being increasingly complex, providing a scalable communication architecture for applications in different languages is tedious. The Apache Thrift framework is the solution to this problem! It helps build efficient and easy-to-maintain services and offers a plethora of options matching your application type by supporting several popular programming languages, including C++, Java, Python, PHP, Ruby, Erlang, Perl, Haskell, C#, Cocoa, JavaScript, Node.js, Smalltalk, OCaml, and Delphi. This book will help you set aside the basics of service-oriented systems through your first Apache Thrift-powered app. Then, progressing to more complex examples, it will provide you with tips for running large-scale applications in production environments. You will learn how to assess when Apache Thrift is the best tool to be used. To start with, you will run a simple example application, learning the framework's structure along the way; you will quickly advance to more complex systems that will help you solve various real-life problems. Moreover, you will be able to add a communication layer to every application written in one of the popular programming languages, with support for various data types and error handling. Further, you will learn how pre-eminent companies use Apache Thrift in their popular applications. This book is a great starting point if you want to use one of the best tools available to develop cross-language applications in service-oriented architectures.
Table of Contents (15 chapters)
Learning Apache Thrift
Credits
About the Author
About the Reviewer
www.PacktPub.com
Preface
5
Generating and Running Code in Different Languages
Index

Planning out your work


As you now have a general idea of what we will be working on, let's plan our endeavor. This is not only necessary for this chapter to have a structure, but you may as well use it as a template for your work.

Planning is the most important part of every project—it is better to spend some extra time in the process of planning, rather than proceeding without a strategy and failing along the way. Due to this, we will spend some time planning before we actually implement our ideas.

The outline of our plan is as follows: first, we will formulate the general idea of our application. This means that we will describe what we want to achieve in normal human language and the tools we are going to use to do this. This may not only include a description of business needs, but also technical requirements or limitations. In real projects, this phase will be conducted with your client's representative, someone who's representing your users or business people. It is important to collect...