sendob

"In deployment, a routing layer handles routing requests from a public-facing hostname to the port-bound web processes."

I think the response from amazon was fine and they are clearly not amateurs technically, communication was very poor.

Even a perfect database, should such a thing ever exist, is not sufficient to protect us from a determined disaster

With postgres and mysql you can find many companies competing to offer great service, and who can contribute their fixes and improvements directly should they so choose. The stronger the output of these communities and the organizations that support them, the more pressure for even the companies like Oracle to improve ( or perish :))

I prefer to work with Postgres when I can, but I also have found instances where MySQL better fit my needs, a heap table, even with more recently added index only scans ( and even reordering the table with cluster may not be desirable) you may want an index organized table (oracle term ) (mysql would say clustered index )

I am curious why even in the context of freely available engines we focus on competition, which I think can lead to great things, but I don't understand the animosity the communities feel towards one another, isn't it just a matter of horses for courses? Are we really interested in competitive kills or improving both the tools we use and our understanding thereof ?

I don't mean to single your comment out gbog, and I know this is certainly not exclusive to databases either ( witness almost any discussion of various programming languages on HN )

The lack of limit sucks, but the thing that annoys me most regularly is that Oracle refuses to make the 0 length string / null behavior configurable to allow for ANSI compliance ( MySQL null handling is worse IMO, makes me insane.... )

There was a time when vision correcting glasses were considered very strange I would imagine, but they proved to be very useful and we become accustomed to seeing them. What will be fun, I think, is as others have postulated wearable tech becoming less apparent to the naked eye, so much so that the plastic brick will be considered odd, and that one would WEAR vision correcting lenses mounted in metal or plastic frames right on the face?!

RE: circumventing the blacklist, I think immediately of accessing a function with postgresql aka select my_destructive_function();

Adoption was good especially for simple queries, people were less focused on the language, and more focused on exploring/modifying examples.

For people who are already familiar with SQL and as you said, less interested in the query language, it may be almost immediately frustrating.

I can absolutely see circumstances where it would be overkill, I have never tried to use it as a performance critical tool, just as more an easy thing to slap on to ease access, two aspects that I have found useful on more than one occasion:

1. HTRAF toolkit is convenient for very basic visualization (depending upon the audience this can be very useful to have at hand quickly)

2. multiple output formats (json in particular) has been helpful in terms of quickly hacking together prototypes in the past

Another tool, different, but also great for sharing, you may enjoy: http://htsql.org/

One phrase I remember from Cantrill re: Oracle & Solaris was that "People Innovate, not companies". Commits contribute, blog posts rarely do.

http://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/MySQL....

On Postgres, you could use arrays: http://www.postgresql.org/docs/9.3/static/arrays.html also has some great contrib modules as well like: http://www.postgresql.org/docs/9.3/static/intarray.html

Mongodb documents their multikey indexes for a similar approach: http://docs.mongodb.org/manual/core/index-multikey/

not to take away from rethinkdb, awesome to see a project move rapidly!

I like to consider the problem, before I recommend a solution generally ( I don't mean to accuse you of pushing a solution, I think you are offering help which is always appreciated ), but I think a lot of people are used to having had the choice already made ( and indeed, in some circumstances it is!).

One thing I always try to remember about mysql, as it is is less than intuitive to me, at least that there is no way I am aware of to alter or restrict this behavior directly, is that in mysql the client is allowed to alter the sql-mode ( I do think I have used proxies to filter out this behavior as a sort of guardian, but that was not an ideal fix by any means ), generally if you don't have control of your clients ( or also hopefully some good layers in front ) in the RDBMS world you are already sunk, but this has been more as a guard against accidental breakage for instance.

http://dev.mysql.com/doc/refman/5.5/en/faqs-sql-modes.html

This can make it unsuitable for certain situations ( where you may not have control of the client ).

One thing that I think is both a strength, and a weakness ( again depending upon the situation ) is that mysql is very flexible and can be deployed in so many different configurations.

Generally I think it is best for people to carefully consider their situation and needs ( and be prepared to change when the situation does!).

I really enjoy working with Postgresql as well, and have long respected the code produced by that project.

In summary, I'd say there are many great databases ( both relational and otherwise!) which can be a real asset to solving problems. The best thing I think is to learn directly and continually :)

It may not have been something which you wanted to do, but I think it is a really interesting problem, and I bet it has been rewarding for both business, and in a pure engineering sense.

In some ways, I think about what it must have been like to create a fake identity in a less connected age, and I wonder at how it will continue to evolve.

I recall some Doctorow novel in which spam and its increasing sophistication was almost an escalating arms race between our ability to distinguish authentic interactions versus those that were staged or generated / general sock puppetry.

I am curious about additional signals and information, I would presume in addition to fingerprinting and collecting as much information about each of their implicit touch points, did you find yourselves increasingly relying on more traditional manifestations of identity/reputation, etc.

edit: Or I wonder about a discount for new sign ups with a one time facebook scan & score type mechanism :D

Thanks again for sharing more information, good food for thought!

http://mcavage.github.io/node-restify/

Both self describe as frameworks.

in a quick blurb on express v restify: "I get asked this more than anything else, so I'll just get it out of the way up front.

Express' use case is targeted at browser applications and contains a lot of functionality, such as templating and rendering, to support that. Restify does not."

FWIW I am a backend guy and have enjoyed prototyping and working with restify a great deal ( dtrace ftw :) ), just a user and YMMV of course.

Would be more curious to know about how effective they have observed this to be, or maybe more about what they learned a long the way, profiles are always interesting, how many false positives, customer complaints(& support time) etc. Maybe a future post?

I can say though that in persistent worlds there is always a history, usually fresh "meat" too though.

"System Requirements PC or Mac with USB port Windows® 8/ Windows® 7 / Windows Vista® / Windows® XP (32-bit)/ Mac OS X (v10.6-10.8)"

I enjoy the ability to fully utilize my right hand and minimize the amount of movement I do to and from the mouse, both for work and general computing.

Depending upon what you want from your mouse ( in the case of the naga, do you want custom binding of macros to buttons beyond a numeric keypad? => if so you need the driver support :( )

A good alternative that I use on my linux machines is: http://www.razerzone.com/gaming-mice/razer-lachesis/

Which has its own memory to retain macros(can be a pain to load, I have typically used windows VMs w/ drivers :/)

I am sorry, them confirming this fact, and even if I recall adding a smiley in the tweet they did it, just cemented that they do not understand their business.

They clearly wish to give the impression that they are "secure". They need more lock icons...they are almost as effective as the racing stickers on my car!

Nice, but has nothing to do with the issues they experienced recently: Still runs on cold fusion, still they do not understand PKI( more tweets about how awesome the passphrase is on your private key, you know the one in adversarial hands...confidence + 10!....)

^Interesting viewpoint.

I am familiar with pg storm which was using pg FDW with CUDA, it had some pretty severe limitations last I looked, I also remember someone doing a sort implementation on cuda on the mailing list which was pretty slick, Tim Child also did some presentations(I never saw code personally, would love a link if anyone has), that was doing opencl as a procedural option which I think would still be really cool, and potentially easier to deal with as an extension where applicable.

I am going to be very interested to see what is possible with postgres 9.3 writable fdw and potentially something like this. May be that postgis will find its way to similar performance given access to the same tech.

35k loc is compact, cannot wait to see the code!

Not to mention "database queries can be costly do to transaction over http" => Not gonna get into this too much, but couchdb has an optimistic concurrency model, yeah?

An implementation that uses a technology ( or like iriscouch is a db as a service) is not that technology. If heroku postgresdb's go down because they configure things incorrectly is that the fault of the project? Could be, could be documentation was lacking, or it was a real footgun. It is also possible to deploy technology within a budget where failures are the expected outcome, it is also very possible to deploy technology in a manner which does not support a use case, or may not even be something the technology can support, that does not make it 'bad' or 'great', and has nothing to do with "control vs ease" or http vs a yet to be named wire protocol...

I just don't see how this is helpful, accurate, or adds to the discussion, sorry if I am jumping down your throat about it.