On Oct 27, 2011, at 10:20 PM, Bryan Taylor wrote:
> Just to be clear we are talking about APIs fit for customer consumption here,
> not internal integrations where both ends are under our control.
>
> On 10/27/2011 11:38 AM, George Reese wrote:
>>> I disagree. The web was designed specifically
Huh? I didn't write that. George did.
On Oct 28, 2011, at 11:35 AM, Caitlin Bestler wrote:
> Jorge Williams wrote:
>
>> Push notifications don't make your core system any more complex. You push
>> the change to a message queue and rely on another system to do the work.
>
> That is only true
On Oct 28, 2011, at 10:33 AM, George Reese wrote:
> You are describing an all-purpose system, not one that supports the narrow
> needs of IaaS state notifications.
>
> There's no reason in this scenario to guarantee message delivery.
Like I said, there are a lot of factors to consider. And
There are ways around that without guaranteed message delivery.
Sent from my iPhone
On Oct 28, 2011, at 11:41, Bryan Taylor wrote:
> On 10/28/2011 10:33 AM, George Reese wrote:
>
>> There's no reason in this scenario to guarantee message delivery.
>
> Usage, billing, support all require guarant
Jorge Williams wrote:
> Push notifications don't make your core system any more complex. You push
> the change to a message queue and rely on another system to do the work.
That is only true if the messaging system and the core system are largely
independent, which could have some implications
On 10/28/2011 10:33 AM, George Reese wrote:
There's no reason in this scenario to guarantee message delivery.
Usage, billing, support all require guaranteed message delivery. "Oops,
sorry, we don't bill sometimes because we lose messages" just doesn't
fly with executives, shareholders, and t
You are describing an all-purpose system, not one that supports the narrow
needs of IaaS state notifications.
There's no reason in this scenario to guarantee message delivery.
Sent from my iPhone
On Oct 28, 2011, at 10:09, Jorge Williams
wrote:
On Oct 28, 2011, at 8:11 AM, George Reese wrote
On Oct 28, 2011, at 8:11 AM, George Reese wrote:
Push notifications don't make your core system any more complex. You push the
change to a message queue and rely on another system to do the work.
The other system is scalable. It has no need to be stateless and can be run in
an on-demand format
When you look at the scalability issue solely from the perspective of the cloud
provider, requiring polling is the lazier, but not really more scalable
solution. Especially if you go nuts with caching. Then it might be even a bit
more scalable.
But when you look at the distributed systems use c
On 10/27/2011 02:14 PM, Monsyne Dragon wrote:
The web was not designed to deal with a bunch of clients needing to
know about infrastructure changes the instant they happen.
True. This whole issue is the reason Nova's existing notification system is
designed as a push system. Currently it's
Just to be clear we are talking about APIs fit for customer consumption
here, not internal integrations where both ends are under our control.
On 10/27/2011 11:38 AM, George Reese wrote:
I disagree. The web was designed specifically to solve the distributed scaling
problem and it's based on HT
Reese
Cc:
Subject: Re: [Openstack] Push vs Polling (from Versioning Thread)
On Oct 27, 2011, at 11:38 AM, George Reese wrote:
> Sent from my iPhone
>
> On Oct 27, 2011, at 11:26, Bryan Taylor wrote:
>
>> On 10/27/2011 10:36 AM, George Reese wrote:
>>
>>> #3 Push s
On Oct 27, 2011, at 11:38 AM, George Reese wrote:
> Sent from my iPhone
>
> On Oct 27, 2011, at 11:26, Bryan Taylor wrote:
>
>> On 10/27/2011 10:36 AM, George Reese wrote:
>>
>>> #3 Push scales a hell of a lot better than having tools polling a cloud
>>> constantly. It doesn't matter whether
Sent from my iPhone
On Oct 27, 2011, at 11:26, Bryan Taylor wrote:
> On 10/27/2011 10:36 AM, George Reese wrote:
>
>> #3 Push scales a hell of a lot better than having tools polling a cloud
>> constantly. It doesn't matter whether it is polling the API, polling a
>> feed, or polling a message qu
On 10/27/2011 10:36 AM, George Reese wrote:
#3 Push scales a hell of a lot better than having tools polling a cloud
constantly. It doesn't matter whether it is polling the API, polling a
feed, or polling a message queue. Polling is one of the most unscalable
things you can do in any distributed
15 matches
Mail list logo
