Beyond held the 7th study session "Game development's [Great feeling] - 'Game API development' that can be used in social game development"!

I'm Ito, an infrastructure engineer and member of the web marketing team.
We held our first study session of 2017!

Announcement: [7th] Beyond Study Session to be held! | Beyond Co., Ltd.

Doorkeeper: Game Development's "Super Cool" ~ "Game API Development" for Social Game Development ~ Beyond Study Group #7 - Beyond Study Group | Doorkeeper

This time, we borrowed the venue from Aiming Co., Ltd. , the company well known for Logres, the sword and magic game

As always, I'd like to share a little bit about what's inside!

First, here is a list of today's sessions

<tｒ>Company name Speaker name Session title

API development and usage with Go

A session by Mr. Hatanaka of Clover Lab.
To be honest, the part he explained this time is actually up on Github lol

GitHub - hatajoe/kug2

The materials for this article are here:
API development and usage using Go

Wonder Crown is written entirely in Go.

Social game development is shifting from small-scale development to large-scale development, and
this is where the Go language comes in handy.

• Static Tidying Language
• simple
• Multi-platform

There are other reasons as well, but that's it

Static Tidying Language

The Go language is a statically organized language with fixed types,
making it ideal for large-scale development where many people use it.

simple

The Go language is simple, so it's easy to learn and
anyone can write similar code.

Multi-platform

It's a multi-platform environment where you can see the same thing
whether you're using Windows, Mac, or Linux It's an era where Windows users and Mac users can get along.

Even though I'm explaining this, there is a source document, so please refer to it!
API development and usage with Go

The execution results were displayed on the terminal immediately,
making it a very easy-to-understand presentation!

API Development with Phalcon

A session by Bandai from our company Beyond

This was an introduction to Phalcon, a PHP framework that is extremely fast

First, he introduced a list of popular PHP frameworks and their speeds, and
here are the top three.

1. High Performance PHP Framework - Phalcon Framework
2. Fast PHP framework | Ice framework
3. Tipsy, an MVW PHP micro framework

The commonly used (probably) Laravel and FuelPHP are ranked low in terms of speed, and
there was even a famous saying that "Those who use Laravel are spoiled."

The installation method is different from other frameworks, and
instead of installing from GitHub, you can install it using yum.
It uses a technique where PHP loads a shared library file.

It's written in C binary, so it's incredibly fast

ORM is also fast in internal processing, but it seems to be a little weak when it comes to communicating with the database, but it
seems to have the speed to make up for that.

It is possible to have a multi-module structure,

Although each installation is different, the directory structure is similar to other MVC frameworks, so
the learning curve for switching from other frameworks is not that high.

He also said that if the learning cost would result in an extremely fast framework, it would be worth the cost

So, let's all switch to Phalcon!

Phalcon articles are gradually appearing on our blog, so please take a look!
Phalcon | Beyond Inc.

Rails-API Way in Aiming

The final session will be by Aiming's Uemori

This is a story about "Aiming's style."

At Aiming, the language is decided for each project

The client side is developed almost entirely in Unity.
Incidentally, the hit game Logres: Ancient Goddess was developed using cocos-2dx,
because it was started when Unity had almost no 2D support.

Also, parts that require real-time performance tend to use C++ or C#, while
WebAPI parts tend to use Ruby (Rails) or Python.
Incidentally, Logres uses Python.

Aiming prefers to use RPC rather than REST APIs.
This is because there aren't many benefits to being resource-oriented, and the communication from the client to the Web API is wrapped and abstracted,
so there's no need to be aware of the endpoint.

Define the protocol

The communication protocol between the WebAPI and the real-time server/client is created in-house to
prevent each environment (client side, real-time server side, API server side) from implementing it independently.
If we had created it ourselves, we would have had to share various things.

This not only makes development easier, but also makes it easier to generate documentation and test clients, which is great!

Using Rails

Rails itself is an ecosystem, so even if the implementation is difficult,
it can be made easier by using existing gems or by referring to them.
The architecture is written and there are many best practices, so
Rails is easy to deal with even if various issues arise.

However, performance may be inferior, so that's the trade-off

summary

It's obvious, but it really brought home to me that different companies use different methods for development.
By looking at the different methods used by different companies, you can choose what you should adopt and what you shouldn't. We sometimes
have students come to our study sessions, so I wonder what they think about it.

By the way, Aiming's office is really clean..

See you in the 8th installment!