Thank you all, I'll keep Your suggestions in mind :)
W dniu poniedziałek, 10 lutego 2014 06:55:39 UTC+1 użytkownik chadkouse napisał: > > The most difficult thing for us was having 3 beanstalkd servers and > worrying about the order these queries would be executed. > --chad > > > On Mon, Feb 10, 2014 at 12:47 AM, Isaac Foraker <[email protected]<javascript:> > > wrote: > >> Straight SQL is definitely simpler to implement on a first pass. It can >> be a bit more complicated to lock down once you start adding >> authentication and access control. It also moves business logic from >> the server to the client, so be cautious. >> >> IF >> >> On 02/09/2014 09:47 PM, Chad Kouse wrote: >> > Dead simple - stick SQL queries into the queue and then have a consumer >> actually run them. Gets a little more complex with multiple queues. --chad >> > >> > On Sun, Feb 9, 2014 at 11:21 PM, Isaac Foraker >> > <[email protected]<javascript:>> >> wrote: >> > >> >> I use beanstalk queues for database updates on one of my projects to >> >> avoid DDoS'ing my web server. >> >> I wrote a server side daemon that reads messages out of a queue that >> >> look like this: >> >> {'table': {'id': 123, 'field1', 'value', 'field2', 'value'}} >> >> It is pretty straight forward to use the YAML support built into the >> >> standard beanstalk clients to serialize your structures from your >> source >> >> language. I use a ruby reader on the server, and ruby and perl clients >> >> (one of my users may have implemented a java client recently as well). >> >> If you are using Rails on your server, it is really easy to convert >> the >> >> table name to model with code like: >> >> data = record-from-beanstalk-message-ybody >> >> table = 'users' >> >> model = table.singularize.classify.constantize >> >> record = model.find(data['id']) >> >> data.delete :id >> >> record.update_attributes(data) >> >> To help reduce client/server transactions, I also implemented support >> of >> >> nested, relational lookups so the clients do not need to look up the >> IDs >> >> of related tables. E.g., >> >> {'reports': >> >> {'id': 123, 'notes': 'some notes', 'users': {'name': 'fox'}}} >> >> In this example, the user record would be looked up, and user_id would >> >> be set in the report record. >> >> Good luck in your project. >> >> IF >> >> On 02/09/2014 01:29 PM, Piotr Koryśko wrote: >> >>> Hi all, >> >>> I just found out about beanstalkd. I got lot insert/update queries >> per >> >>> second in my database, which my PostgreSQL (with PgBouncer) can't >> handle >> >>> (statement timeouts). I can afford to have this data available to >> read with >> >>> some delay. >> >>> Can I use beanstalked to create queries queue, how can I achive that? >> The >> >>> documentation is quite poor. >> >>> >> >> -- >> >> You received this message because you are subscribed to the Google >> Groups "beanstalk-talk" group. >> >> To unsubscribe from this group and stop receiving emails from it, send >> an email to [email protected] <javascript:>. >> >> To post to this group, send email to >> >> [email protected]<javascript:>. >> >> >> Visit this group at http://groups.google.com/group/beanstalk-talk. >> >> For more options, visit https://groups.google.com/groups/opt_out. >> > >> >> -- >> You received this message because you are subscribed to the Google Groups >> "beanstalk-talk" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] <javascript:>. >> To post to this group, send email to >> [email protected]<javascript:>. >> >> Visit this group at http://groups.google.com/group/beanstalk-talk. >> For more options, visit https://groups.google.com/groups/opt_out. >> > > -- You received this message because you are subscribed to the Google Groups "beanstalk-talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/beanstalk-talk. For more options, visit https://groups.google.com/groups/opt_out.
