Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Stripe: Open Source

stripe.com

Post reply on HN
Print view View original

31–40 of 74 posts

Re: Stripe: Open Source

#32

Post by sandGorgon »

why did you guys invent mosql [1] ? you are clearly loving postgres and cannot get rid of it... but potentially with jsonb in 9.5 [2] you can get rid of mongodb.

With the kind of resources you have, you could fix the few things about postgres that you dont like.

[1] https://github.com/stripe/mosql/blob/master/README.md

[2] https://wiki.postgresql.org/wiki/What's_new_in_PostgreSQL_9....

Re: Stripe: Open Source

#33

Post by jaryd »

ebroder wrote: post #17
ebroder wrote: post #9

Earlier quoted context omitted.

(I'm an infrastructure engineer at Stripe) This actually took a fair amount of digging! We've been using some version of unilog for over 4 years now (longer than I've been at Stripe), and we'd mostly forgotten why we switched. What follows is more the result of historical exploration and guesswork than authoritative statement of original truth. I'm fairly confident that the impetus for unilog was timestamp prefixes f…

And an update! I talked with the engineer that wrote unilog originally. The original headline feature of unilog was that it wouldn't block writes if the disk filled up. multilog does - if it can't write a line to disk, it stops ingesting data off of stdin, which eventually causes the application to hang writing to stdout. unilog sends you an email and starts dropping log lines, which we decided better matched the tra…

Wow--thanks for the update. Buffering to memory before writing to disk is definitely a great feature (especially when operating out of AWS) and could be enough for us to switch to unilog.

Regarding the timestamps. We've actually gotten quite used to TAI64N--it's definitely not human parseable but it is extremely specific :) We end up just piping logs through tai64nlocal or converting it at the logstash stage.

Re: Stripe: Open Source

#36

Post by fica »

Mashape is another startup that contributes a lot in the API space with mainstream OSS projects such as: OAuthBible [1], Unirest [2], HTTPsnippet [3], Guardian [4] and KONG [5].

[1] https://github.com/Mashape/mashape-oauth

[2] http://unirest.io/

[3] https://github.com/Mashape/httpsnippet

[4] https://github.com/Mashape/guardian

[5] https://github.com/Mashape/kong

Re: Stripe: Open Source

#37

Post by scotchio »

Love the logo! Did something similar here [1] for our blog's creative/digital arm [2] with actually a somewhat similar approach. Probably a few months ago. Their's is a little more elegant though :)

I just want to make a quick comment: Everything the Stripe's front-end guys touch is pure and magical perfection. They definitely have a killer front-end team - design, UI/UX, and more.

[1] http://codepen.io/ncerminara/pen/MYvELv

[2] https://digital.scotch.io

Re: Stripe: Open Source

#39

Post by mcorrand »

jordanlev wrote: post #27
mcorrand wrote: post #3

On the subject of the jquery.payment lib, I remember noticing that the validation functions it provides for various credit cards are not exactly the same as the ones in stripe.js, and actually better. I would have to look at my commit history to remember what exactly were the differences though. I think it could match the various credit card types with fewer digits entered or was better for cvv validation of amex car…

I get the impression that stripe has abandoned jquery.payment (or at least it's a side project and not part of their core offering?). Because it does not actually work out of the box with the stripe.js library (see https://github.com/stripe/jquery.payment/issues/160 , which has a lot of "+1's" from other people but no response from stripe or whoever it is that maintains this library).

I never noticed because I'm actually using stripe.js to do the payment, and was only using the various validations from jquery.payment in a couple angular directives.

I realized stripe.js had validation functions built in one day looking into the source, and that's where I remember those validations acting differently from.

Post reply on HN