Fork me on GitHub
#aws
<
2015-09-18
>
alandipert13:09:56

@luposlip: ah, no, haven't looked at ECS in very much detail. scaling on beanstalk is very easy... but being able to leave AWS is not a goal for us

luposlip13:09:26

@alandipert: it’s not a goal in itself for me, but having the possibility is really valuable, and it seems to me it’s easier if using docker as compared to plain Beanstalk?

luposlip13:09:01

right simple_smile Also considering trying out Lambda, just for the heck of it (to begin with just for some time scheduled jobs)

alandipert13:09:13

we're also using that lol

alandipert13:09:07

after we went over the aws tipping point we're in a place where the best thing to do is leverage all their services maximally, even if it means we can never leave

alandipert13:09:46

speaking of, time to go to work, bbl simple_smile

luposlip13:09:22

😉 Later!

upgradingdave14:09:13

Howdy aws clojure peeps

upgradingdave14:09:55

Thought this article was a pretty good overview … although be careful because if you’re like me, you’ll have to read all about the aws services you didn’t know about: https://www.expeditedssl.com/aws-in-plain-english

jgdavey18:09:30

Has anyone deployed immutant to AWS? Wondering if elasticbeanstalk is an option or not

alandipert18:09:57

hm, last i looked into it, the way to do immutant in AWS was to cluster in EC2

jgdavey18:09:10

👍 Thanks. Doing that now.

alandipert19:09:04

altho @tcrawley might know better, and #C085AR8RE on freenode is usually hoppin'

statonjr20:09:45

We deploy Immutant to AWS without a cluster. We do not use Elastic Beanstalk.

jgdavey20:09:49

Thanks @statonjr. That’s the way I’m going

alandipert21:09:29

are you using immutant messaging and cache stuff, or just the web bits?