Re: Web Service

Thank you Kerry. Pre calculating some of the results is a good possibility.
Looks like legacy database read access (which is DB2 / SQL Server) could be
slowest link.

Do you know of Java EE 7 servlet benchmarks  - what app server? 

 

Best Regards,

 

Sudhir 

From: Kerry Wilson [mailto:[email protected]] 
Sent: Wednesday, July 03, 2013 11:54 AM
To: [email protected]
Subject: Re: [ajug-members] Web Service

 

If you only have one http endpoint and a team of java developers, regular
old servlets perform pretty well in most benchmarks I have seen. Plus java
ee 7 has asynchronous servlets. Personally, I would probably use the Play
framework. It's well documented, performs well, and the learning curve
should be very low (though the asynchronous api can be ugly in Java).

 

The caching / persistence strategy is the more interesting question to me.
It sounds like you may want to go with a more polyglot solution. These types
of things are usually highly specialized for the situation. But the solution
may look something like loading redis with the minimum amount of data to
serve the requests in an optimized format. You may even be able to
precalculate the results. Again, it all really depends on the data.

 

kw

 

 

On Wed, Jul 3, 2013 at 8:08 AM, Summers Pittman <[email protected]> wrote:

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





 

-- 

http://www.allthingswilson.com

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