Mailing List Archive: Cherokee: users

MySQL asynchronous balancing with HTTP+JSON

Index | Next | Previous | View Threaded

alvaro at gnu

Aug 17, 2008, 2:24 PM

Post #1 of 6 (415 views)
Permalink

MySQL asynchronous balancing with HTTP+JSON

Hi guys,

Check this out:
http://www.alobbs.com/1344/MySQL_asynchronous_balancing_with_HTTP_JSON.html

Now Cherokee can also work as balancer and bridge for MySQL.
How cool is that?! ;-)

--
Greetings, alo.
http://www.alobbs.com/

_______________________________________________
Cherokee mailing list
Cherokee[at]lists.octality.com
http://lists.octality.com/listinfo/cherokee

skinkie at xs4all

Aug 17, 2008, 2:32 PM

Post #2 of 6 (390 views)
Permalink

Re: MySQL asynchronous balancing with HTTP+JSON [In reply to]

Alvaro Lopez Ortega schreef:
> Check this out:
> http://www.alobbs.com/1344/MySQL_asynchronous_balancing_with_HTTP_JSON.html
>
> Now Cherokee can also work as balancer and bridge for MySQL.
> How cool is that?! ;-)

Your graphics skills are outstanding :D

Would it be possible to divide the SQL vendor specific part in different
modules? So we could apply this on MonetDB, PostgreSQL, etc.?

Could you elaborate on the performance on this thing versus more native
solutions?

Stefan
_______________________________________________
Cherokee mailing list
Cherokee[at]lists.octality.com
http://lists.octality.com/listinfo/cherokee

alvaro at gnu

Aug 17, 2008, 2:44 PM

Post #3 of 6 (391 views)
Permalink

Re: MySQL asynchronous balancing with HTTP+JSON [In reply to]

On 17 Aug 2008, at 23:32, Stefan de Konink wrote:
> Alvaro Lopez Ortega schreef:
>> Check this out:
>> http://www.alobbs.com/1344/MySQL_asynchronous_balancing_with_HTTP_JSON.html
>>
>> Now Cherokee can also work as balancer and bridge for MySQL.
>> How cool is that?! ;-)
>
> Your graphics skills are outstanding :D
>
> Would it be possible to divide the SQL vendor specific part in
> different
> modules? So we could apply this on MonetDB, PostgreSQL, etc.?

Even if the initial code implements it just for MySQL, it should be
possible. However, I don't think I will implement any other if there
is not enough target audience for it.

> Could you elaborate on the performance on this thing versus more
> native
> solutions?

Native solutions.. like..?

Just to clarify things. The most important point here is that the
communication between your application logic and the data base is
performed asynchronously, over a well known and easy to trace
protocol. And of course, being able to use Cherokee's balancing
modules (policies) to split your SQL load among a bunch of servers is
also very interesting.

--
Greetings, alo.
http://www.alobbs.com/

_______________________________________________
Cherokee mailing list
Cherokee[at]lists.octality.com
http://lists.octality.com/listinfo/cherokee

skinkie at xs4all

Aug 17, 2008, 2:52 PM

Post #4 of 6 (390 views)
Permalink

Re: MySQL asynchronous balancing with HTTP+JSON [In reply to]

Alvaro Lopez Ortega schreef:
> On 17 Aug 2008, at 23:32, Stefan de Konink wrote:
>> Alvaro Lopez Ortega schreef:
>>> Check this out:
>>> http://www.alobbs.com/1344/MySQL_asynchronous_balancing_with_HTTP_JSON.html
>>>
>>>
>>> Now Cherokee can also work as balancer and bridge for MySQL.
>>> How cool is that?! ;-)
>>
>> Your graphics skills are outstanding :D
>>
>> Would it be possible to divide the SQL vendor specific part in different
>> modules? So we could apply this on MonetDB, PostgreSQL, etc.?
>
> Even if the initial code implements it just for MySQL, it should be
> possible. However, I don't think I will implement any other if there is
> not enough target audience for it.

I'll do the MonetDB and PostgreSQL thing for it then :)

>> Could you elaborate on the performance on this thing versus more native
>> solutions?
>
> Native solutions.. like..?

MySQL Loadbalancer, Proxy, et al.?

> Just to clarify things. The most important point here is that the
> communication between your application logic and the data base is
> performed asynchronously, over a well known and easy to trace protocol.
> And of course, being able to use Cherokee's balancing modules (policies)
> to split your SQL load among a bunch of servers is also very interesting.

I'm not ignoring this :) But what about authentication? Is only one view
possible or would it be possible to have multiple sessions for different
users?

Stefan
_______________________________________________
Cherokee mailing list
Cherokee[at]lists.octality.com
http://lists.octality.com/listinfo/cherokee

alvaro at gnu

Aug 17, 2008, 3:18 PM

Post #5 of 6 (390 views)
Permalink

Re: MySQL asynchronous balancing with HTTP+JSON [In reply to]

On 17 Aug 2008, at 23:52, Stefan de Konink wrote:

>> Just to clarify things. The most important point here is that the
>> communication between your application logic and the data base is
>> performed asynchronously, over a well known and easy to trace
>> protocol.
>> And of course, being able to use Cherokee's balancing modules
>> (policies)
>> to split your SQL load among a bunch of servers is also very
>> interesting.
>
> I'm not ignoring this :) But what about authentication? Is only one
> view
> possible or would it be possible to have multiple sessions for
> different
> users?

From the Cherokee side, it is just another handler. You can configure
it exactly as any other. All the general functionality remains in
place: authentication, encoding, access restrictions, etc.

Now, from the MySQL side, there will be a single user authenticating
against it. I can not really see the case in which it wouldn't be
enough though. Think that you can configure as many dbslayer handlers
as you wish (with different user, password, data bases and even MySQL
hosts) inside the same Cherokee server.

--
Greetings, alo.
http://www.alobbs.com/

_______________________________________________
Cherokee mailing list
Cherokee[at]lists.octality.com
http://lists.octality.com/listinfo/cherokee

skinkie at xs4all

Aug 17, 2008, 3:25 PM

Post #6 of 6 (391 views)
Permalink

Re: MySQL asynchronous balancing with HTTP+JSON [In reply to]

Alvaro Lopez Ortega schreef:
> From the Cherokee side, it is just another handler. You can configure
> it exactly as any other. All the general functionality remains in place:
> authentication, encoding, access restrictions, etc.
>
> Now, from the MySQL side, there will be a single user authenticating
> against it. I can not really see the case in which it wouldn't be enough
> though. Think that you can configure as many dbslayer handlers as you
> wish (with different user, password, data bases and even MySQL hosts)
> inside the same Cherokee server.

Yes, this makes a lot of sense and basically 'fixes' the connection pool
problems of many database servers :) Since this would generate one
single persistent connection to each server. It would be interesting to
also distribute updates and insert statements to all database as online
replication mechanism.

I'll soon talk about this approach with the MonetDB development team :)

Stefan
_______________________________________________
Cherokee mailing list
Cherokee[at]lists.octality.com
http://lists.octality.com/listinfo/cherokee

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact lists@gossamer-threads.com