Re: Web Service

It seemed like you had already chosen the Joyent as your platform which
makes a lot of choices for you.

Summers Pittman
>>Phone:404 941 4698
>>Java is my crack.



On Wed, Jul 3, 2013 at 3:47 PM, Sudhir Kamatkar <[email protected]>wrote:

> Thanks Summers. Yes, we do have to write to the database.
> Vert.x looks interesting. Will certainly do more research on this.
> Didn't understand what you meant by ' And actually reading up on Joyent
> shows me why I may be quite off for my suggestions...'
>
> Best Regards,
>
> Sudhir
> -----Original Message-----
> From: Summers Pittman [mailto:[email protected]]
> Sent: Wednesday, July 03, 2013 9:08 AM
> To: [email protected]
> Subject: Re: [ajug-members] Web Service
>
> On Wed 03 Jul 2013 09:06:55 AM EDT, Summers Pittman wrote:
> > On 07/03/2013 08:35 AM, Sudhir Kamatkar wrote:
> >>
> >> Friends,
> >>
> >> We are working on a web service to be built. Key is there could be
> >> bursts of up to 10,000 concurrent requests/transactions during
> >> certain times of the day. Web service itself is relatively straight
> >> forward which involves getting 4-5 fields of information (text &
> >> numbers) from the requesters (mobile and other devices) and then
> >> fetching data from the database and performing simple calculations
> >> and sending results back.
> >>
> >> What technologies would you suggest for better performance,
> >> scalability, ease of writing code/rning curve (for Java developer)
> >> and stability?  Which cloud provider would you recommend?
> >>
> >> One thought was to use  node.js, akka for Java, Redisl, ngnix and
> >> deploy in Joyent. Does anyone have experience with these
> >> technologies? Our concerns are - Is this stack too bleeding edge,
> >> stability of code (since they have sub 0.x versions), learning curve
> >> for Java developer, too many moving parts for administration,
> >> troubleshooting and testing?
> >>
> >> Thank you in advance for your help.
> >>
> >> Sudhir
> >>
> > If you don't have to write to the database and can predict when
> > traffic bursts happen why not use EC2 to host the project and spin up
> > more instances?
> >
> > If you are worried about learning curves for Java you might want to
> > research vert.x instead of node.js.
> >
> > I can't actually speak to any of the other techs.
> And actually reading up on Joyent shows me why I may be quite off for my
> suggestions...
> >>
> >>
> >>
> >> _______________________________________________
> >> ajug-members mailing list
> >> [email protected]
> >> http://www.ajug.org/mailman/listinfo/ajug-members
> >
>
>
>
> _______________________________________________
> ajug-members mailing list
> [email protected]
> http://www.ajug.org/mailman/listinfo/ajug-members
>
>
> _______________________________________________
> ajug-members mailing list
> [email protected]
> http://www.ajug.org/mailman/listinfo/ajug-members
>

_______________________________________________
ajug-members mailing list
[email protected]
http://www.ajug.org/mailman/listinfo/ajug-members