I'm not building Facebook/pinterest but I'm trying to work on a platform like "pinterest-like" but on a small scale. I want it to be easy to write, fast, ... you know. D is obviously that (IMO).

About scalability, would you recommend D(vibe.d initially) for long run (techically, generally, currently)? Why? (Brutal honesty).

On Monday, 2 January 2017 at 21:49:03 UTC, aberba wrote:
> I'm trying to work on a platform like "pinterest-like" but on a small scale.

I did something similar for work about five or six years ago. Used D, went well.

The company changed direction though while it was still small, so I'll never know if it would have scaled or not.

On Mon, 02 Jan 2017 21:49:03 +0000, aberba wrote:

> I'm not building Facebook/pinterest but I'm trying to work on a platform like "pinterest-like" but on a small scale. I want it to be easy to write, fast, ... you know. D is obviously that (IMO).
> 
> About scalability, would you recommend D(vibe.d initially) for long run
> (techically, generally, currently)? Why? (Brutal honesty).

I'd consider what languages future employees are likely to know and how much time it would take them to become proficient with D. I'd consider what dependencies I will likely have and whether there are existing D libraries for them. Then I'd put together a demo and see how it works. Use ab(1) (the Apache benchmark tool) to estimate scaling naively, and then implement a more application-specific benchmarking tool to see in more depth.

I'd do that iteratively, so I'm not spending weeks on a demo that can't handle two simultaneous database connections or falls over if you look at it funny.

I'm likely to want investors, so a functional demo is useful, even if I scrap it after seed funding or Series A.

I'd do the same with any toolkit or language at that stage. For instance, I'm at an early-stage startup right now, and I spent a bit of effort comparing several different frameworks we could use for services and RPCs.

This isn't so much an answer, but then, I don't know your usecase well enough, and I don't know what technologies you plan to use. For instance, you might want to use Hadoop for file storage. Or MongoDB + GridFS. Or MySQL with a limit on file sizes. Or a scale-out filesystem like Qumulo. These are quite different options with different levels of support in D.

On Tuesday, 3 January 2017 at 00:51:04 UTC, Chris Wright wrote:
> On Mon, 02 Jan 2017 21:49:03 +0000, aberba wrote:
>
>> I'm not building Facebook/pinterest but I'm trying to work on a platform like "pinterest-like" but on a small scale. I want it to be easy to write, fast, ... you know. D is obviously that (IMO).
>> 
>> About scalability, would you recommend D(vibe.d initially) for long run
>> (techically, generally, currently)? Why? (Brutal honesty).
>
> I'd consider what languages future employees are likely to know and how much time it would take them to become proficient with D.
Ha ha. That is a potential problem. But I will figure things out.

>I'd consider what dependencies I will likely have and
> whether there are existing D libraries for them.
That's my fear. I'm much into using already baked stuff.

> a more application-specific benchmarking tool to see in more depth.
>
Will look into that.

>
> I'm likely to want investors, so a functional demo is useful, even if I scrap it after seed funding or Series A.
>
> I'd do the same with any toolkit or language at that stage. For instance, I'm at an early-stage startup right now, and I spent a bit of effort comparing several different frameworks we could use for services and RPCs.

I'm currently planning on funding initially myself. And support in future with content promotion fees... mini mini ads :)

I feel getting investors will limit my ability to craft it ATM.



> This isn't so much an answer, but then, I don't know your usecase well enough, and I don't know what technologies you plan to use. For instance, you might want to use Hadoop for file storage. Or MongoDB + GridFS. Or MySQL with a limit on file sizes. Or a scale-out filesystem like Qumulo. These are quite different options with different levels of support in D.

Planning to use mysql and mongoDB(for the flexible part). I haven't research much about File Systems but I planning to use amazon s3. Basically I want to handle few burden as possible.

Could use some advice though. It will be based my my country alone (local audience). But local hosting services are not reliable (down time issues).

On Tuesday, 3 January 2017 at 00:04:33 UTC, Adam D. Ruppe wrote:
> On Monday, 2 January 2017 at 21:49:03 UTC, aberba wrote:
>> I'm trying to work on a platform like "pinterest-like" but on a small scale.
>
> I did something similar for work about five or six years ago. Used D, went well.
>
> The company changed direction though while it was still small, so I'll never know if it would have scaled or not.

Nice. How fast were you able to get it to a mature state?

I have been prototyping with vibe.d (dub) for sometime now.

This might be obvious but ... compilation and linking slows the process... its not much problem though.

On Tue, 03 Jan 2017 11:47:54 +0000, aberba wrote:
> Could use some advice though.

http://vibed.org/ is the framework you'll probably be using. It has mysql and mongodb support.

http://code.dlang.org/ says there's an s3 client that works with vibe: http://code.dlang.org/packages/vibe-s3 It's got some scary warnings about its alpha status, so try it out before committing.

On Tuesday, 3 January 2017 at 11:59:46 UTC, aberba wrote:
> Nice. How fast were you able to get it to a mature state?

About six months to get everything we wanted working well. The initial core was done in about two (including me writing necessary D libraries to support it, this was done before vibe.d was out so I wrote all my own), then we had to add features, styles, polish, etc. over the next several months.

> I have been prototyping with vibe.d (dub) for sometime now.
>
> This might be obvious but ... compilation and linking slows the process... its not much problem though.

My compile+link time at one point hit 15 seconds so I optimized some templates and got it down to 7. Still kinda slow but not *that* bad.

On Monday, 2 January 2017 at 21:49:03 UTC, aberba wrote:
> I'm not building Facebook/pinterest but I'm trying to work on a platform like "pinterest-like" but on a small scale. I want it to be easy to write, fast, ... you know. D is obviously that (IMO).
>
> About scalability, would you recommend D(vibe.d initially) for long run (techically, generally, currently)? Why? (Brutal honesty).

i'd suggest the language that you know the best, the language that will not block your way and build barriers so you can focus on building your product. maybe later you can port it to D or build some new services in D.

On Wednesday, 4 January 2017 at 04:10:30 UTC, Adam D. Ruppe wrote:

> About six months to get everything we wanted working well. The initial core was done in about two (including me writing necessary D libraries to support it, this was done before vibe.d was out so I wrote all my own), then we had to add features, styles, polish, etc. over the next several months.

Did you implement some form of clustering (session, storage, caching)?

On 1/3/17 11:10 PM, Adam D. Ruppe wrote:
> My compile+link time at one point hit 15 seconds so I optimized some
> templates and got it down to 7. Still kinda slow but not *that* bad.

How large was the codebase? Thx! -- Andrei