The tech stack we use to build Lago (YC S21), the open source billing API

Back to stories Open in a window
Article news.ycombinator.com

The tech stack we use to build Lago (YC S21), the open source billing API

Our users and peers often ask us what language and tools we use to build Lago (getlago.com), the open source billing API, and why. Here are our answers.

As part of our selection process, we focus on (1) robustness and (2) engineering speed. This means that once we’ve identified a few suitable tools, we aim to make our decision quickly to get back to building asap.

Our engineering stack is a living organism, so it will keep evolving, but here is what we use at the moment:

Language: Ruby on Rails We developed Lago in Ruby. There are many technical reasons for that and our team, which has worked on billing for 3 years, has 10 years of experience with this language.

Every year for the past 10 years, people ask whether Ruby is dead.

Ruby is not going anywhere: it’s popular, offers a fast learning curve and what we find attractive is the vast community of Rubyists we can hire as we grow.

In the future, we might develop other services in Python, Rust or Go.

NB: There are several clients available for Lago’s API: Curl, Go, Python, Node.js and Ruby (as of August 2022), see our API documentation here.

Hosting: Amazon Web Services (AWS) It’s ‘AWS robust’, we used it before and let’s be honest, AWS offers generous perks to YC companies.

Container orchestration: Kubernetes No brainer for microservices.

Abstraction layer for Kubernetes: Porter ‘Heroku in your cloud’

Porter is a YC company as well. The team is genuinely nice, super reactive and precise. But that’s not why we chose them: they were recommended by one of our advisors, who led big data infrastructure projects for incumbent banks and telecom companies in Europe. So we chose them on the spot.

A solid alternative is Qovery, their team is brilliant too. The team only ran into their product once we had already implemented Porter, but it’s a great product as well!

Error alerting system: Sentry We used it before. It gets s** done consistently, is easy to use and reliable. Their company philosophy is interesting too, check it out here.

Cloud monitoring: New Relic We tried Datadog and New Relic, and opted for New Relic: the onboarding was simpler and their entry level plan was much cheaper.

VPN: Tailscale We started with NordVPN. It’s a great VPN, but we only needed an internal VPN. Tailscale does exactly that, and it’s really ‘zero-config’. Tailscale will link to your domain name, so that every team member can easily connect to it. It makes onboarding new team members easier and allows us to save a lot of time on the configuration.

Backoffice: Active Admin It ticks all the boxes:

Not a third-party app; In the Ruby ecosystem; and Quick set-up. Our code repository: GitHub GitLab could have been an option but GitHub is the standard for self-hosted code.

Documentation: Docusaurus We looked at GitBook, Theneo and GitHub pages. We wanted to have both the product documentation and API reference in the same place, while having enough flexibility on the presentation and design. We view our documentation as a part of our product so it needs to reflect the UX and brand we’re building.

We’re very happy with Docusaurus! The only thing to be aware of is that it’s a self-hosted solution, so it requires some configuration.

Product analytics: Metabase We used it extensively before. It’s flexible in terms of queries and can also be used by non-tech users. We opted for the self-hosted version.

Search bar in our documentation: Algolia It was one of our users’ requests. Most people use Algolia without knowing it (e.g. on Hacker News and many other websites). Love the product and the team!

If you’re hesitating between different tools, we’ll be happy to share our experience with you!

Discussion 1 comments · 5 points · Rafsark · 2022-08-12
Open on HN
Loading the discussion…

Domain filters

Stories from these domains are hidden from every list. Subdomains match too: blocking substack.com also hides danluu.substack.com.

    About YAVCHN

    YAVCHN is a reader for Hacker News and Lobsters, with articles and discussions in separate windows or Classic pages.

    Created by Paul Parks and built with PUDL.

    YAVCHN source code on GitHub

    Help

    Keyboard

    j / k
    Move down and up the story list. The arrow keys scroll whatever has focus.
    Enter
    Read the marked story in the article reader.
    ]
    Read the next story in the same article-reader applet. Back returns to the previous story.
    p
    Pin or unpin the marked story, which keeps it in Pinned.
    n / N
    Move to the next or previous top-level comment in the window in front.
    c
    Collapse or expand that comment.
    f
    Hide or show the story list.
    Esc
    Close a menu or this help.
    Access key m
    Go to the menu bar. Most browsers take it with Alt on Windows and Linux, and Safari with Control and Option.
    ?
    Show this help.

    Windows

    Each story opens in a window holding its article above its discussion; drag the bar between them to share the room differently. A window can be moved by its title bar, resized from any edge, snapped to a half or a corner by dragging it there, maximised, or minimised to the bar at the foot of the page. Use Window > New reader window to open an empty reader, or Story > Open in new reader window to open another reader for the current article. Docked readers keep their articles when you select another story from the sidebar. Minimized readers can be restored and reused for their site. A window's Next story link reads on down the list in the same window.

    A link in a comment or an article to another Hacker News or Lobsters thread opens that thread in a window too. A link to a single HN comment opens the comment above its replies.

    While a story's window is in front, the Story and Discussion menus in the menu bar hold its commands: pinning, Next story, sorting, collapsing every thread, jumping to the first new comment. Each window also remembers where you were in its article and discussion, so a reload, or Back to a story that Next took you past, finds your place again. Closing a window forgets it.

    The whole arrangement lives in the address, so a bookmark or a shared link brings it back, and Back undoes the last change. Moving between Hacker News, Lobsters, their lists, Pinned and Find changes only the list, and leaves the windows open.

    The list

    The pin at the start of a row keeps the story in Pinned, and the cross at its end hides it. Pinned can be narrowed by words in the title, site or author, by source, and to the stories you haven't opened yet, and ordered by when you pinned them, by points or by comments; the filters are part of the address, so a filtered view can be bookmarked. Scroll past the end of the list to load more. Domain filters, in the View menu, hide every story from a site.

    Browsing view

    View > Windowed and View > Classic select the browsing view and save your default in this browser. Window view reuses a reader for each feed. Classic view opens stories and applets as pages. Open as a page and Open in a window are one-off actions that do not change your saved default. Direct page links always open as pages.

    Applets

    The Applets menu in the menu bar holds three tools, each a window of its own. Replies to me takes your Hacker News user name and lists the replies to your last thirty comments and stories, checking again every three minutes while it is open, and marking what is new since you last marked them read. Look up a user opens a profile on Hacker News or Lobsters, with their submissions and recent comments, as a commenter's name in any discussion does; the bar at the top of a profile looks up someone else in the same window, and Back returns to the one before. Who is hiring? filters the posts of HN's monthly hiring threads by the words you type.

    They read only what the sites publish to everyone, so none of them asks for a login, and your user name stays in this browser.

    Find

    Find takes any link and lists every time it was submitted to Hacker News and Lobsters, so you can read each discussion of it.

    About

    YAVCHN never sees your Hacker News or Lobsters login. The discussion is fetched from each site's public API; to vote or reply, follow the link above the discussion, or the arrow beside a comment, to the source's own site. Pins, hidden stories, filters and layout are kept in this browser only.

    Open source: github.com/paulmooreparks/yavchn. Built with PUDL.