Clojurians Log v2

gentlemen, we have been spared from the great clojurians slack purge of 2017, but have been asked to 'advertise the channel more'

thus, please invite your friends, invite your enemies, even invite the uncoverted from AWS -- we need to grow this community!

I posted a note on #admin-announcements to draw attention to this channel. I suggest adding a “topic” and expanding the “purpose” description a bit.

It’s been some years since I last tried to do battle with GAE — as I recall it had some “interesting” restrictions on JVM programs. Have those been lifted, at least partially?

@seancorfield : it's doable but not pleasant yet; http://qqq-demos.appspot.com/ is hosted on GAE -- there's some work arounds involved in getting clojure to run on the JVM GAE restrictions

should probably be #gcp? I dunno if you can change slack channel names though

yeah, it should be #gcp

good call

we should change it now while there's only 9 ppl; is standard to use #gcp or #google-cloud-platform?

Given #aws I’d stick to just the acronym.

Want me to rename it (and update my #admin-announcements post)?

@seancorfield : that'd be amazing! I was about to create a new chnanel + invite everyone; but renaming it would be infinitely better!

And good ol’ Slack automatically updated my admin post for me!

google-cloud would be more understandable and searchable 🙂

maybe one of these days the slack channel search will consider the description of the channel important :eyerolly:

@seancorfield : if you don't mind, could you rename it to #google-cloud ? I do realize this breaks protocol with #aws, but I do agree with serioga that it's more searcahble (i.e. when I first searched for channels< I typed in "google ... ", not "gae" or "gcp"

Remember that the purpose is what shows up in the list of channels so that should be updated.

@seancorfield : how do we update the purpose? I just updated the topic

In the side-bar, expand Channel Details and mouse over it — there will be an edit link.

So this is what a rant turns into 😄

Never underestimate the power of a good rant!

I've been thinking about: "What is the single best thing that would make this channel popular?" And I think the answer is: If our glorious founder, @sveri , did regular live casting of Clojure/GCP tech, and only answered questions posted to this channel. 🙂

That would probably single handedly attract people to #google-cloud .

@qqq That sounds like a nice idea, the problem is, I am not even closely interested in #google-cloud as it is much more expensive than my server -.-

let alone the 3 TB storage will cost me 60$ / month, thats without the i3770 and 16 GB RAM I have on my server

@sveri: doh; what hosting provider is this?

whaaaaaaat? 8 vCPUS and 30 GB RAM + 3 TB storage = 260 $ -.-

@qqq Not sure where you live, but here in germany we have hetzner: https://robot.your-server.de/order/market#623733

Something similar will cost 31€

And these are real root servers, no virtualization

I could setup like 6 of those for the same price 😄

with virtualisation comes HA

that said a managed service is always going to be significantly more expensive than diy, no doubt

Thats true, given I have my server for playing around and backup I dont need managed stuff myself 🙂

The main reason I'm using GAE is: (1) until the service gets big, it doesn't matter (2) my server side is not CPU/RAM intensive (3) when it does get big, I'd rather pay Google to host my distributed database -- rather than running distributed riak on a cluster myself

that said: https://robot.your-server.de/order/market#626672 is really fucking amazing

Yep, these are "used" machines. Still they will switch hardware for you if something breaks

On the dataside, this also means there's no 99.99% guarantee and it's your job to backup in case hd dies?

Exactly

I'd be happy to pay for used machines + gcp/aws storage

Almost all come with a raid, but if both hard drives fail, well, you better have a backup 😄

I think the machine /bandwidth is highway robbery; but I'm willing to pay for a multi-region distributed database

Yea, it all depends on the use case 🙂