Slack LaTeX

#1

Post by c0nrad » Tue, Oct 12, 2021, 3:10 AM UTC

Re: Slack LaTeX

#2

Post by paxys » Tue, Oct 12, 2021, 11:48 PM UTC

I have had a lot of trouble in the past with Lambda cold starts timing out Slack slash command requests, so you may actually be better off without it.

Re: Slack LaTeX

#3

Post by collegeburner » Tue, Oct 12, 2021, 11:48 PM UTC

Interesting article. How much requests can you support for 20/month before losing money with this stack?

Also, I am curious though, what does his partner do usually if not frontend stuff? Unusual to go into business with a frontend engineer who then does 0 frontend work, no?

Re: Slack LaTeX

#4

Post by orf » Tue, Oct 12, 2021, 11:54 PM UTC

Given the fairly stateless nature of slack apps like this, what does mongodb give you that dynamodb doesn’t? Seems like you could fit into the free tier quite easily.

Re: Slack LaTeX

#5

Post by steve_adams_86 » Wed, Oct 13, 2021, 1:04 AM UTC

collegeburner wrote: post #3

Interesting article. How much requests can you support for 20/month before losing money with this stack? Also, I am curious though, what does his partner do usually if not frontend stuff? Unusual to go into business with a frontend engineer who then does 0 frontend work, no?

I think he says the partner created the front end using React, doesn't he?

> My partner built the frontend. It’s very nice having someone to help with the frontend work!

> She built it using React, no special libraries.

> We setup a makefile so she can one command deploy to s3 and invalidate the cache. Developing at lightspeed.

Re: Slack LaTeX

#6

Post by freedomben » Wed, Oct 13, 2021, 1:35 AM UTC

orf wrote: post #4

Given the fairly stateless nature of slack apps like this, what does mongodb give you that dynamodb doesn’t? Seems like you could fit into the free tier quite easily.

Not OP, but being open source and platform agnostic is a huge value to me of Mongo over Dynamo.

Re: Slack LaTeX

#7

Post by c0nrad » Wed, Oct 13, 2021, 1:52 AM UTC

orf wrote: post #4

Given the fairly stateless nature of slack apps like this, what does mongodb give you that dynamodb doesn’t? Seems like you could fit into the free tier quite easily.

Disclosure: I used to work at MongoDB, left 2 years ago.

True, it probably would have made sense to stay completely within AWS. If I didn't know MongoDB very well, I would have used DynamoDB.

But I know MongoDB well, and MongoDB Atlas (the hosted platform) also has a free tier, and it's hosted in ec2, and you can setup VPC peering (so network speed _should_ be comparable to dynamo, but not sure).

Also, Atlas (MongoDB's Cloud Platform) has a really nice "charts" product (sort of like a built in web based tableau) which I use for my internal dashboards (it takes But yeah, if I wasn't already biased, I would have used DynamoDB.

Re: Slack LaTeX

#8

Post by c0nrad » Wed, Oct 13, 2021, 2:20 AM UTC

collegeburner wrote: post #3

Interesting article. How much requests can you support for 20/month before losing money with this stack? Also, I am curious though, what does his partner do usually if not frontend stuff? Unusual to go into business with a frontend engineer who then does 0 frontend work, no?

> Interesting article. How much requests can you support for 20/month before losing money with this stack?

Ha, I haven't profiled it yet. I'm not too sure. But, I think a decent amount. If a slack team with 10000+ physicists signs up, I may need to talk to them offline.

I do plan on doing some stress testing in the future for fun, I'll try to remember to reply here.

> partner frontend

Yep, to repeat what steve_adams_86 said, she did the frontend completely. Usually I'm forced to do the frontend, it was very nice having someone else just do the whole thing without me.

Re: Slack LaTeX

#9

Post by doppp » Wed, Oct 13, 2021, 4:02 AM UTC

This is awesome, thanks for sharing. I'm currently building a Slack app myself and this is very useful information.

Re: Slack LaTeX

#10

Post by NmAmDa » Wed, Oct 13, 2021, 5:00 AM UTC

c0nrad wrote: post #8

collegeburner wrote: post #3

Interesting article. How much requests can you support for 20/month before losing money with this stack? Also, I am curious though, what does his partner do usually if not frontend stuff? Unusual to go into business with a frontend engineer who then does 0 frontend work, no?

> Interesting article. How much requests can you support for 20/month before losing money with this stack? Ha, I haven't profiled it yet. I'm not too sure. But, I think a decent amount. If a slack team with 10000+ physicists signs up, I may need to talk to them offline. I do plan on doing some stress testing in the future for fun, I'll try to remember to reply here. > partner frontend Yep, to repeat what steve_adams_…

Teams with this number of physicists exists only in CERN which uses self-hosted mattermost. Don't worry from that for now.