Hi Jerry, I'm still reading about Rodeo and trying to evaluate whether to
take the plunge. there are a couple of things I don't quite get:
1. The web apps being served by On-Rev: Rodeo server is a
highly-scaleable, secure, n-tier architected cloud solution. So there is no
way to author
Of course it's still early days, but we are very serious about having a
scaleable backend service.
Since one of us is in Australia, we also want geographic coverage. Every day
this sector of our industry gets better.
Massively shared servers? No. Deals for dedicated servers? Yes.
We want
On 20 May 2010 14:27, Jerry Daniels jerry.dani...@me.com wrote:
Of course it's still early days, but we are very serious about having a
scaleable backend service.
Since one of us is in Australia, we also want geographic coverage. Every
day this sector of our industry gets better.
Massively
I've worked on several projects with massive numbers of simultaneous
users and hits against data. Did this for Nortel, a broadband wireless
company and another small telecom.
The trick is to know where to scale the hardware and where to put the
data and where to put the logic.
Look at it
On 20 May 2010 16:55, Jerry Daniels jerry.dani...@me.com wrote:
The cheapest, most scalable and fastest performing are all the same
solution:
1. Client: thin
2. Web server: thin, but round-robin'd the IP addresses to 1 of the 13 app
servers
3. Web app server: hefty, almost fat
4. Data:
David,
I don't think you'll reach problems of scalability that easily. Twitter and
Facebook have scalability issues, you'll probably be fine for months before
reaching scaling issues even if you're really successful.
Don't think a single server with a single database is no good for your
needs.
Years ago, i did test an XServe G4 running a Sybase ASE 12.5 and went able to
get 1500 web served requests / secs without any server's stress at all. And as
anyone should know, OS X Server is lots less responsive than Linux or BSD.
2 cents,
Best, Pierre
Le 20 mai 2010 à 18:49, Andre Garzia a
I think you miss understand what I'm saying or your experiences don't match my
own.
What I suggest is not expensive and is, in effect, what most n-tier architected
solutions do. I learned from a couple guys who invented data access via a
stateless browser. But what do they know?
You might be
Absolutely.
Best,
Jerry Daniels
Create iPad web apps with Rodeo:
http://rodeoapps.com
On May 20, 2010, at 11:49 AM, Andre Garzia an...@andregarzia.com wrote:
You're probably safe on On-Rev or Rodeo or whatever is invented soon
___
use-revolution
David,
Not sure if there was a Rodeo question or something in there, but I
will try to clarify, etc.
Rodeo is not a hosting package. We host your LIST code and translate
it into iPad web app pages. You don't get an ftp addess or anything
like that, so, no it's not a standard On-Rev
Andre-
Thursday, May 20, 2010, 9:49:57 AM, you wrote:
David,
I don't think you'll reach problems of scalability that easily. Twitter and
Facebook have scalability issues, you'll probably be fine for months before
reaching scaling issues even if you're really successful.
Twitter, Digg,
On 20 May 2010 21:52, Mark Wieder mwie...@ahsoftware.net wrote:
Twitter, Digg, Reddit, etc are indeed reaching the scalability limits
of their databases, and are moving into the NOSQL world of Cassandra,
Hadoop, CouchDB... but you need to up at the level of shoveling around
petabytes of data
12 matches
Mail list logo
