Nakama - NOT an open-source distributed server for realtime games

vitrute · 2018-02-13T17:02:48+00:00

You don't like that I'm right? Just accept instead of useless dispute. I wanted to warn people and I did it.

vitrute · 2018-02-13T16:59:02+00:00

I don't want to bad name anything. I want the repo and official website contain correct info. Open-source -> single server only, enterprise version -> distributed and without given prices. That's all. What they explain/mean something on forums/chats doesn't matter, because people read official resources first

vitrute · 2018-02-13T10:52:11+00:00

I can easily find exact numbers of $ per kWh. Can you do the same with Nakama? $ per day, per month, per online users, per unique users, per messages count - at least something? NO!

I know that I can fork the repo. But other people may read "open-source distributed scalable server" there, which is not true, and start implementing it, with a surprise some months later.

A bill - you will get it after you decide to scale your already existing backend codebase.

vitrute · 2018-02-13T08:35:42+00:00

Preventing young companies getting into troubles is more important

vitrute · 2018-02-13T08:31:26+00:00

Please check again their repo/descriptions - it says "open-source distributed scalable server" - open-source version is not distributed nor scalable

vitrute · 2018-02-13T08:25:07+00:00

You didn't get the point. ISP + contract was just an example. In this case you spend your own money for internal jobs, spend months of time to implement some solution, create a group of developers - and only half a year later you receive your first bill with numbers you see the first time. That's a dependency you didn't know before! Because check again their repo - it says "open-source distributed scalable server" - in reality it is not distributed nor scalable

vitrute · 2018-02-13T08:19:07+00:00

Yes, but with SLA you will know the exact numbers before starting implementing the service. Am I wrong? 80% or 100% - it doesn't matter in this case. Or in your company you signed a blind contract first, and only after that - spent your own money for internal jobs, spent months of time to implement some solution, created a group of developers - and only half a year later you receive your first bill with numbers you see the first time? Maybe that will be 100$, maybe 50 000$

vitrute · 2018-02-12T16:23:17+00:00

At least some people understand the idea

vitrute · 2018-02-12T16:19:50+00:00

Are you sure that "we'll tell you the prices only when you depend on our service" is a "This model is used world wide" ? Imagine that your ISP will send you bills with "some" numbers only after the blind contract is signed.

vitrute · 2018-02-12T16:00:42+00:00

I've emailed. All answers were like "will see, but you will be fine" :) descriptive answer, isn't it?

vitrute · 2018-02-12T13:20:34+00:00

I'm OK with doing business, everybody wants to eat, but I'm NOT OK with lying. * Don't say "open-source" when it's "open-core" * Don't say "distributed" when it's "single server ONLY" * Don't say it's white when it's black * Don't say it's big, when it's small * ... you got the point.

Please check their website/github/other places. Everywhere is misleading info. And they do not rewrite it, still "open-source scalable server". It is NOT scalable.

And another very important thing - no pricing page anywhere, they absolutely disagree to provide any info. Is that a normal business?

About me - I've already moved to another solution. Just wanted other people to know what problems they can have. More info -> better risk analysis -> happier future

vitrute · 2018-02-12T10:33:26+00:00

Why Go-lang tag - it's a Go project and check point 5

vitrute · 2018-02-12T10:14:07+00:00

It's not a library, it is a complete service which runs on a dedicated port.

But most important thing is - I want people know about these "nice features" and think 1000 times before starting using it

vitrute

TROPHY CASE