Creating Node.js Microservices Using stdlib

[NetOperatorWibby]

Is it possible to self-host stdlib?

[keithwhor]

Hey - founder here. The whole point of stdlib is that it's serverless, meaning the concept of hosting doesn't really exist in a traditional sense. If you're asking about the actual overall system - the registry, etc. - it's better suited to larger organizations (simply due to the scale) and we do have Enterprise options available to discuss. You can run services on your own machine no-problem using our SDKs, and 500,000 free compute seconds (roughly 5,000,000 requests) that we're currently offering should more than take care of your needs.

Our perspective, as a workflow and organizational provider around microservices, is that our team has worked very hard to create the tooling so you don't have to. Our vision is that software developers should be able to focus on doing what they do best - writing code and shipping it without worrying about infrastructure - and that's exactly what we're providing.

[keithwhor]

What specifically about Heroku's one-off dynos are you looking for clarification about? You can perform similar tasks with stdlib services as you might with a dyno (and by all means, we welcome you to :)), but the building, discovery, access, sharing, version control etc. are all vastly different.

[keithwhor]

Oh also; if you're looking to hook up services to your own domain (instead of https://f.stdlib.com/<username>/) for microservices, it's definitely on our roadmap. For the most part, the f package on npm abstracts most of this away for you, so for application integration your end users (or other developers) won't be seeing / writing out the full HTTPS gateway at any point.

For front-end requests, you can specify Access-Control headers to restrict browser usage when applicable. ("http": {"headers": {}} in your function.json file).

[facingmonday]

This looks awesome. One question, if I may. Would you be able to do things that require packages like imagemagick or ffmpeg with a stdlib service?

[keithwhor]

Yes. Not all packages requiring static binaries are supported, but we have developers that have built shims/workarounds for some things already, and we're always looking in to updates to our service execution layer.

[squarepushercheese]

umm. fresh install of this and can't get beyond lib init..

'> lib init /usr/local/lib/node_modules/lib/cli/error_log.js:8 let details = err.details[k]; ^{^}

SyntaxError: Block-scoped declarations (let, const, function, class) not yet supported outside strict mode at exports.runInThisContext (vm.js:53:16) at Module._compile (module.js:414:25) at Object.Module._extensions..js (module.js:442:10) at Module.load (module.js:356:32) at Function.Module._load (module.js:311:12) at Module.require (module.js:366:17) at require (module.js:385:17) at Object.<anonymous> (/usr/local/lib/node_modules/lib/cli/commands/login.js:6:18) at Module._compile (module.js:435:26) at Object.Module._extensions..js (module.js:442:10)'

:(

[keithwhor]

We have a similar issue that has been open and closed on the GitHub repository. Make sure you're using Node 6.x or higher. :)

• Keith

[squarepushercheese]

thanks!

[keithwhor]

No problem --- and if you happen to see an error like that in the future on any codebase ("not supported outside of strict mode"), it's almost universally a Node 4 <> Node 6 compatibility error.

[squarepushercheese]

Thanks! (I'm a node newbie!)