One of the thing that sets OpenJS Architect apart from other serverless tools is its opinion that serverless apps work best when composed of many small, discrete Lambda cloud functions.
This approach offers the greatest coldstart performance, security isolation, deployment speed, and mean time to bug resolution. However, this approach also comes with a minor drawback: the need to manage many Lambdas’ dependencies.
Or at least it used to! Architect 8.4 introduces a new concept we call Lambda Node.js modules treeshaking.
If you’d like to take advantage of the nearly 1.5 million publicly published Node.js modules, your Architect app may have numerous individual
package.json files spread across its various Lambdae. …
By popular demand: OpenJS Architect 8.3 (El Chupacabra) now supports custom file paths, custom Lambda templates, a fresh new local (and global) preferences file, and lots more!
By default, like many frameworks, Architect relies on convention over configuration — meaning you can expect certain things, like the placement of function handlers, to appear in default, deterministic locations.
However, some projects and integrations necessitate more granular configurability. In Architect 8.3, you can express your project in a more verbose format that exposes additional settings, such as a custom handler source directory.
# simple - assumes src/http/get-foo/
OpenJSF Architect powers thousands of real production serverless applications all over the world. We continue to hear how valuable folks find its focused, direct, stable, lock-in-free approach to building blazing fast modern web apps without ever having to manage a single server.
Today we’re announcing Architect 8 (El Chupacabra), which adds the newest Architect pragma,
@proxy, and makes
@http routes even more powerful with three new additions!
Want to give it a go? Here’s the super quickstart, no AWS credentials required:
OpenJSF Architect now powers thousands of serverless applications all over the world. Folks continue to tell us they value its focused, direct, stable, lock-in-free approach to building blazing fast modern web apps without ever having to manage a single server.
Today we’re extremely excited to announce Architect 7 (Chupacabra), a major step forward in building serverless web apps and APIs with AWS.
Chupacabra now deploys AWS API Gateway v2.0 (aka
HTTP) APIs by default, and ships with a rewrite of Architect’s local development environment, Sandbox. …
master-slave carry powerful implications of racial supremacy and oppression, and have no place in our lexicon. Efforts across our industry are rightfully underway to retire such references to the dustbin of history, where they belong.
Although Git and GitHub still name branches
master by default (for now), moving your repos away from the
master branch name is relatively easy. In this guide we’ll rename it
main (or you can choose whatever you prefer). Some other ideas that have been bandied about include:
First, make sure you’ve gone over the following checklist to ensure you won’t be introducing any tricky…
Begin already gives you the most advanced set of serverless tools and application primitives in its class:
@http), enabling full server-side rendering
Hit this button to deploy an event functions example app to Begin in 30 seconds:
Since 2017, Architect has been the premiere foundation-backed open source serverless framework, with a clear focus on being the simplest, fastest way to build a modern web app.
The space has evolved rapidly, and we’re incredibly excited to announce Architect 6 (Ogopogo): a ground-up rewrite with first-class Ruby & Python support, that combines the speed and simplicity of which Architect users are accustomed, with the determinism of AWS’s infrastructure-as-code standard, CloudFormation.
Want to give it a go? Here’s the super quickstart, no AWS credentials required.
npm i -g @architect/architect
Architect treats local offline development of serverless apps as a first-class concern, and today we’re taking it to the next level.
Architect 4.3 (Yeti) includes an all-new version of sandbox (
npx sandbox) that starts up instantly, instantly loads your local code changes, and best of all, paves the way for multiple runtimes.
The new Architect sandbox now boots up instantly. In testing, >50 route projects start in under 300ms on a modern laptop. Whether your serverless app has 2 or 200 functions, you’ll never experience lag on account of simply continuing to build out your app.
In addition to locally mocking cloud functions, Architect sandbox now even more closely emulates the properties of a true serverless stack by loading your latest code with each new request. Yet another small but meaningful performance improvement to make you faster and keep you in flow. …
When we got started in 2015, we didn’t set out to build a serverless application platform.
We were working on an application with some hardcore real-time, natural language processing, and scalability requirements, and we chose to base it on a brand new thing called cloud functions.
Those requirements forced us to solve all kinds of mission-critical problems up and down the serverless stack. And it worked.
From that project we extracted Architect, our vision for an open source, primitives-first serverless framework, now hosted at the JS Foundation. …
4.0 introduced the new
public directory that automatically syncs your static assets to the cloud, making it an ideal companion to your existing frontend build steps.
Together, we think Architect’s
public directory and
@views system is going to change the game for web developers onboarding into the serverless world. …