We're starting to play around with Kinesis[1] to get a sense of
performance, reliability, and cost. The Clojure api provides access to all
functionality[2] and handles most of the plumbing details[3] associated
with the client lib. Note: You will need the client library to test drive
it.
CRUD against an SQL database is not imo the sweet spot for Clojure, at
least not if you're comparing it against things like Rails or Django. With
most of the NoSql stores out there, there's a Clojure client that let's you
basically say, Here's a map, upsert it, which is essentially what you can
I get a typical clojure-y set of data fairly deeply nested data
structures that I have yet to master with respect to traversing using
basic clojure operations
You get an arbitrarily nested Clojure, not Clojure-y, data structure
precisely because those maps, lists, and sets suffice in 99% of
time ec2-describe-images -a ec2-cli-images.txt
real 1m26.401s
user 0m6.551s
sys 0m1.159s
and writes a 7.5MB file to disk. Note the -a flag, to list all of the
available public images.
in a repl,
(time (spit clj-awz-images.txt (describe-images)))
Elapsed time: 90258.47 msecs
and writes an
Curious to hear opinions on this:
https://github.com/mcohen01/amazonica
--
--
You received this message because you are subscribed to the Google
Groups Clojure group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderated - please be
Thanks for the comments. I've made the suggested changes such that the AWS
functions take an optional first parameter map of credentials. But I'm left
wondering if it should not be required, and just do away with the stateful
defcredential convenience. Thots?
On Monday, March 25, 2013
performance it seems like this library would cause
me some problems.
Besides that, I love the idea of an auto generated lib.
Timothy Baldridge
On Tue, Mar 26, 2013 at 12:18 PM, Michael Cohen
mcoh...@gmail.comjavascript:
wrote:
Thanks for the comments. I've made the suggested changes
I ran a quick and dirty benchmark comparing Amazonica with James' rotary
library, which uses no explicit reflection. This was run from an EC2
instance in East, hitting a Dynamo table in the East region. tl;dr
Amazonica averaged 9ms for gets, rotary averaged 6ms, both averaged 13ms
for puts.
probably not. amazonica delegates to the official java sdk.
On Tue, Oct 21, 2014 at 4:12 AM, Yehonathan Sharvit vie...@gmail.com
wrote:
Do you plan to have a cljs version of America
It would ne nice if you could support s3 api.
On Monday, 25 March 2013 23:51:42 UTC+2, Michael Cohen wrote
for future libraries.
-Greg Mitchell
On Monday, March 25, 2013 2:51:42 PM UTC-7, Michael Cohen wrote:
Curious to hear opinions on this:
https://github.com/mcohen01/amazonica
--
You received this message because you are subscribed to the Google
Groups Clojure group.
To post to this group
Awesome!
Every time - every single time - I've ever pulled up the api docs in a
browser, for a split second I feel a tinge of embarrassment to be part of a
community that has a language this good but a docs site that *#@&$#!& bad.
The new site is a quantum leap forward. Everyone involved take
11 matches
Mail list logo
