This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-05-15
Channels
- # announcements (2)
- # aws (52)
- # beginners (326)
- # cider (24)
- # clara (7)
- # clj-kondo (14)
- # cljs-dev (175)
- # clojure (183)
- # clojure-ecuador (2)
- # clojure-europe (4)
- # clojure-italy (11)
- # clojure-nl (1)
- # clojure-norway (1)
- # clojure-spec (5)
- # clojure-sweden (5)
- # clojure-uk (103)
- # clojurescript (49)
- # cursive (29)
- # data-science (9)
- # datascript (17)
- # datomic (23)
- # emacs (6)
- # events (4)
- # fulcro (19)
- # graalvm (8)
- # graphql (2)
- # hoplon (36)
- # jobs (1)
- # jobs-discuss (92)
- # juxt (3)
- # luminus (10)
- # off-topic (4)
- # pedestal (8)
- # planck (1)
- # re-frame (59)
- # reagent (1)
- # reitit (22)
- # rewrite-clj (8)
- # ring-swagger (3)
- # shadow-cljs (101)
- # spacemacs (15)
- # tools-deps (36)
- # vim (68)
I’d like to use SQS for a low-traffic mail-sending queue (say less than 5k emails/day), but both the producers and the consumers would not be running on AWS (yet, they will in 6 months time). Is this a crazy idea or pretty normal?
Cool! I see that they say latency is at most low hundred ms so for an email queue that sounds acceptable.
(s/form :cognitect.aws.s3.PutObjectRequest/Body)
=>
(clojure.spec.alpha/or
:byte-array
clojure.core/bytes?
:input-stream
(clojure.core/fn [%] (clojure.core/instance? java.io.InputStream %)))
i.e. right now I need to do this:
(s/def ::s3-client #(satisfies? aws-client/ClientSPI %))
Out of curiosity, does anyone know if Azure or GCP expose their APIs via data files like AWS does?
If you could transform the AWS API JSONs into the OpenAPI format, it seems like the aws-api concept could work for multiple cloud providers.
Looks like someone has already done this: https://github.com/APIs-guru/openapi-directory/tree/master/APIs/amazonaws.com
it's not in the amazon descriptors, so it wouldn't be in any translation of those descriptors
It seems like you'd be able to handle that in a similar manner to how aws-api handles "special" apis
Interesting. My company is adding support for additional cloud providers and we really enjoy working with aws-api. Any thoughts on how difficult it'd be to change aws-api to take in OpenAPI JSON instead of the aws-specific JSON files?
personally I wouldn't try to modify, but I'd take the same approach.
input = descriptors ->
output = functions that can assemble and disassemble request/response maps
but mainly I wouldn't try to modify the client because it's conceptually a simple thing
something that takes .proto
files and builds functions from maps -> bytes and bytes -> maps