[Pharo-project] Pharo/Seaside as back-end for a social media app
Hi all, I plan to build a social media app, initially targeted to iOS clients. I was wondering if pharo 1.4 and seaside 3.07/3.1 are enough for a back-end where at least these requirements are expected: + Rest communication (I can use Seaside-REST) + Media transmission, ie sending/retrieving Photos and Videos (What Seaside modules I can use for this?) + Database communication (I can use GlorpDBX) + Ouath2 authentification (??, I understand that CouldforkSSO is a client not a server) + Scalability, where I can easily grow from hundreds to thousands of clients. Do you think Pharo could meet that requirements or I must use something less cool :-(, such as ruby on rails. Thanks in advance. I'll really appreciate your comments. Cheers
Hi Oscar,
+ Media transmission, ie sending/retrieving Photos and Videos (What Seaside modules I can use for this?)
You probably don't want to serve medias with Pharo but use Apache/nginx/whatever. They serve static files really well and you don't want to put load on your Smalltalk for such a task.
+ Database communication (I can use GlorpDBX)
Never used it but it seems to work fine for many people.
+ Ouath2 authentification (??, I understand that CouldforkSSO is a client not a server)
I would be interested if you find a solution/package.
+ Scalability, where I can easily grow from hundreds to thousands of clients.
If you go stateless (you probably will if you go full REST) you can distribute load on as many images as you want.
Do you think Pharo could meet that requirements or I must use something less cool :-(, such as ruby on rails.
Ruby/Rails has probably a bigger ecosystem and conventions around it but Pharo is definitely cooler ;)
Hi, On Aug 29, 2012, at 6:39 AM, Francois Stephany <tulipe.moutarde@gmail.com> wrote:
Hi Oscar,
+ Media transmission, ie sending/retrieving Photos and Videos (What Seaside modules I can use for this?)
You probably don't want to serve medias with Pharo but use Apache/nginx/whatever. They serve static files really well and you don't want to put load on your Smalltalk for such a task.
yeah... but thats an usual configuration. I don't think anyone in the world renders video by themselves.
+ Database communication (I can use GlorpDBX)
Never used it but it seems to work fine for many people.
you can use it (dbxtalk.org), but... why do you need a relational database? Why care about that now?
+ Ouath2 authentification (??, I understand that CouldforkSSO is a client not a server)
I would be interested if you find a solution/package.
no idea :)
+ Scalability, where I can easily grow from hundreds to thousands of clients.
If you go stateless (you probably will if you go full REST) you can distribute load on as many images as you want.
as in all solutions, it depends much in your application design. A regular Seaside application can handle more or less 30-50 simultaneous requests per image, which is not much but with some design you can improve a lot... and of course, you can scale by adding pharo boxes, and since a pharo box will consume around 100m (again if your design is ok...), with 1G RAM available you can run 10 pharo boxes which gives you 300-500 simultaneous requests... which most than good for most applications :)
Do you think Pharo could meet that requirements or I must use something less cool :-(, such as ruby on rails.
Ruby/Rails has probably a bigger ecosystem and conventions around it but Pharo is definitely cooler ;)
as a summary, I think you are going to be ok :) Esteban
Thanks a lot, for your comments.
+ Media transmission, ie sending/retrieving Photos and Videos (What Seaside modules I can use for this?)
You probably don't want to serve medias with Pharo but use Apache/nginx/whatever. They serve static files really well and you don't want to put load on your Smalltalk for such a task.
yeah... but thats an usual configuration. I don't think anyone in the world renders video by themselves.
Yes, I agree !
+ Database communication (I can use GlorpDBX)
Never used it but it seems to work fine for many people.
you can use it (dbxtalk.org), but... why do you need a relational database? Why care about that now?
Yeahp, I know that at the beginning it is a silly question. However, when the app grows, I will need something, may a Relational database (my first intuition) or may be I can use Magma/Goods, but I don't known how well these works.
+ Ouath2 authentification (??, I understand that CouldforkSSO is a client not a server)
I would be interested if you find a solution/package.
no idea :)
I couldn't find a package for this. May be some guy is trying to implement it or may be we can do it.
+ Scalability, where I can easily grow from hundreds to thousands of clients.
If you go stateless (you probably will if you go full REST) you can distribute load on as many images as you want.
as in all solutions, it depends much in your application design. A regular Seaside application can handle more or less 30-50 simultaneous requests per image, which is not much but with some design you can improve a lot... and of course, you can scale by adding pharo boxes, and since a pharo box will consume around 100m (again if your design is ok...), with 1G RAM available you can run 10 pharo boxes which gives you 300-500 simultaneous requests... which most than good for most applications :)
Nice!
Do you think Pharo could meet that requirements or I must use something less cool :-(, such as ruby on rails.
Ruby/Rails has probably a bigger ecosystem and conventions around it but Pharo is definitely cooler ;)
as a summary, I think you are going to be ok :)
Certainly, It will be a great project/opportunity to do it in Smalltalk and much much fun than using other approaches. Cheers.
participants (3)
-
Esteban Lorenzano -
Francois Stephany -
Oscar E A Callaú