HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
keithwhor
nodal
JavaScript2015–2020
keithwhor / nodal

nodal

API Services Made Easy With Node.js

Explore on GitHubRead Hacker News discussions
4Distinct people
11Mentions
0Explicit recommenders
4.5KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

API Services Made Easy With Node.js

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year11 dated mentions

Observed mentions: 2015-05-20 00:16:27 UTC to 2020-03-10 20:00:37 UTC.

02462015-01-01 00:00:00 UTC to 2016-01-01 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments20152016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 7 mentions; 2 submissions, 5 comments2017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments20172018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2020

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20152015-01-01 00:00:00 UTC2016-01-01 00:00:00 UTC211
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC725
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC000
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC000
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC000
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC202

What Hacker News says

11 sources
keithwhor·Mar 10, 2020
If you're interested in setting up easy scheduled functions, I can recommend checking out Autocode: https://autocode.stdlib.com/new/?event=scheduler.daily&event... This link will set up an automatically scheduled script / endpoint you can deploy in a click. Disclaimer; I built a lot of it. (Founder.) Warning is that there's a signup wall right now but it is free to use. Based on feedback we might be removing the signup wall at some point just so more people can check it out. I'm previously the author of Nodal [1], a Node.js API framework that had quite a bit of early popularity -- we transitioned to building Standard Library [2] to focus on easily building APIs and combining them for simple backend workflows / integrations. Fits with JAMStack pretty well, generally, and our users aren't just developers; it's accessible to business users a
Read the rest
s well, provided they don't mind learning a little code. :) [1] https://github.com/keithwhor/nodal [2] https://stdlib.com/
In Redwood: An integrated, full-stack, JavaScript web framework for the JAMstack
keithwhor·Feb 13, 2020
Congrats on all your hard work! Those are some impressive libraries. I come from an OSS background, it’s what started all of this, so I appreciate the hustle and contributions! The project that spawned all of this was a Node.js framework for easily building APIs that went viral here four years ago [0]. If it helps clarify, Autocode is for people looking to solve integration problems (A to B) for businesses easily. We can talk all day about which specification we use, but that argument is adjacent to the fact that the combination of tools we offer are faster by one — if not two — orders of magnitude at just delivering business value — a finished software product that connects A to B (to C to D). We’ve spent years of work developing this tooling and thousands of hours talking directly to both API companies and end-users about what they need
Read the rest
. This is the result, and we’ve worked at making sure the tools we use — even if bespoke — are open source for others to learn from [1]. P.S. If this is your jam, reach out! We are hiring :) [0] https://github.com/keithwhor/nodal [1.0] https://github.com/FunctionScript [1.1] https://github.com/stdlib
In Show HN: Autocode – Automatically generate API code for SaaS apps
rajington·Dec 11, 2016
I forgive him but this is what I received if you're curious (about 15 emails across 2 accounts within a couple of days): On Mon, Jul 25, 2016 at 8:19 PM, Keith Horwood <k____@p______.com> wrote: one last attempt... let me know if you'd like those extra credits and if I can help in any way. thanks again, so much, for joining and I hope you get a lot of mileage out of our software and services! - Keith On 2016-07-23 00:19:59 UTC, Keith Horwood <k____@p______.com> wrote: guess I caught you at a bad time, would love to talk more if you do get the chance! it's just a few questions and it means a lot to us. :) - Keith On 2016-07-20 00:19:59 UTC, Keith Horwood <k____@p______.com> wrote: hey! didn't hear back from you, would still love to know all about you and hook you up with some more credits. Aside from the free credits, feel free to reach ou
Read the rest
t to me any time --- this is my personal e-mail. :) Cheers, - Keith On 2016-07-17 00:19:59 UTC, Keith Horwood <k____@p______.com> wrote: Hey, Thanks so much for signing up for Polybit and checking it out, and happy Saturday! I'm Keith Horwood, author of Nodal (https://github.com/keithwhor/nodal) and founder of Polybit. The response we've seen to Polybit so far has been nothing short of amazing, and you're part of that. Thank you. No, really, it's been a lot of hard work to get to where we are today and your support makes everything worthwhile. We're trying to learn as much as possible about our users and community --- it's important we can support everyone --- so I'd like to offer you some free platform credits. Would just like to know a couple things, a short e-mail response will go a long way. :) 1. Did you know about Nodal before checking out Polybit? 2. Do you plan on using Polybit for personal purposes, work projects, or both? 3. Where do you work? 4. Is there anything you'd like to know about us? Let me know and I'm happy to add 1,000 credits to your account. By the way - if you sign up for our community Slack with the slack command on polybit.com, you'll get an additional 500 credits. Cheers, - Keith
In Polybit makes mistake. Owns up.
keithwhor·Jun 6, 2016
Biggest point to hammer home home here is use MVC folder organization. Use a framework that already exists, if possible. Standardize your process for creating webapps so you (and your team) can get to writing the code that actually matters as quickly as possible. Ideally you want to decide on; A) Your code style, file organization B) Your HTTP routing C) Your views or data format (JSON responses only?) D) Your database E) How you interface with your database F) How you maintain your database (migrations, etc.) G) Testing Pick these for yourself. Use the same processes repeatedly. Document the processes. This is where opinionated frameworks save huge amounts of time. You'll find the process that works best for you, but if every developer you meet has a process that is somewhat orthogonal at one level, you'll have to create a new one when y
Read the rest
ou work together. This is a waste of time. One of the reasons Rails is so outstandingly popular is because it gave a common set of tools to backend developers and a set of patterns everybody could share. These sorts of questions about organization are the ones I had when I first built Nodal [1], and I was frustrated to find the best MVC solutions in the Node space didn't give me anything close to what I was working with coming from Django and Rails. That said - use what works for you. Bonus points if it also works for the other developers you're working with. ;) [1] https://github.com/keithwhor/nodal
In Ask HN: How do you maintain and organize JavaScript?
keithwhor·May 22, 2016
Interesting you bring up the point about API backends. I'm the author of Nodal [1], with the goal of bringing the best design patterns and practices from Rails and Django to the world of Node, focused completely on building a decoupled API layer. There is no view / template logic at all. The project is very lightweight right now (benefits of being a young project with a sole full-time contributor), but I'd be interested to hear your feedback as to what you think is or isn't necessary for continued development. :) [1] http://github.com/keithwhor/nodal
In My time with Rails is up
keithwhor·Apr 23, 2016
Hey! I'm the author of Nodal [1] and I think this could be a really neat platform for open source communities. Gitter / Slack tend to be the default for live, realtime chat and GitHub is central for issues and contributions, but I'm looking for something fun to direct developers towards where we can organize community events and the like. I'm a startup founder myself and would love to connect with the founding team, is there an ideal way to reach out? [1] http://github.com/keithwhor/nodal
In Ex-Reddit exec launches 'Imzy,' a warmer, fuzzier Reddit
keithwhor·May 20, 2015
Well, you can start using JS for your API server, at least. Nodal [1], a full-featured API server and framework for iojs was just released yesterday with full PostgreSQL integration. (Migration and schema support, to boot.) :) I'm not a huge fan of isomorphic JavaScript. While it seems great for prototyping, I have doubts on its stability, security, and ability to scale. It seems to be a knee-jerk reaction to just having the technology to write web-client and web-server code in the same language and the emergence of SPAs. The thing is, we've had working client-server application architecture (which is what an SPA is) for decades. Every multiplayer game you've ever played. Chat programs. Etc. Nobody would risk the headache of tightly-coupling your data layer, presentation layer, and business layer just to save a few lines of code. We separ
Read the rest
ate our concerns in our code itself with MVC frameworks, why are isomorphic frameworks trying to tightly-couple our actual application layers? It's a little bit contradictory to me. While Meteor seems like a great tool for a couple of newbie developers to rapidly prototype an idea, I'm still not convinced it has the potential to grow into a reasonable architecture. [1] https://github.com/keithwhor/nodal
In Meteor Raises $20M

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.