586 karma · joined February 8, 2013
MCP Apps are pretty awesome and seem ideal for internal tool use-cases. They're visual, so they make AI much more accessible for every role in a company. AI without UI is a black box.
• Devs forever want choice.
• Open-source LLMs are getting better
• Anthropic ships fantastic models
• Doesn't expose your app’s data to multiple companies
• Consolidated security, billing, config in AWS
• Power of AWS ecosystem
If you use the Framework's (optional) observability product, pricing is based on Traces and Metrics, like most observability solutions.
Credits are used to pay for these various features.
I highly recommend you discuss this with us/me. We're small, approachable, flexible, and you've been with us so long we're more motivated than ever to make this work.
You can opt out of the observability features in the Dashboard.
You love developer tools that help you build more and manage less.
We're working on three big tools and services. You can impact all of them:
• Serverless Cloud - A next-generation Heroku, led by Jeremy Daly.
• Serverless Desktop - A graphical user interface for building serverless applications.
• Serverless Framework CLI - The application framework that started the serverless movement.
We are 100% remote in North America, Europe & China.
The Serverless Framework open-source experience does not do this. But there are premium features, like Serverless Framework Components (which this post is actually referring to) which do this.
When you use these premium features you must log into the Serverless Framework SaaS offering via your CLI, accept a TOS, etc.
At the same time, we need to make sure our communication on these SaaS offerings and how they work is more clear. With respects to that, we'll collect all of the feedback we can to get this right!
Further, this is all designed to support and facilitate our upcoming component-scoped permissions, which will significantly reduce required permissions for the Framework, compared to what Serverless Framework Traditional requires.
We'll add more clarity in the docs specifically on credentials and try to make this known upfront.
The candid reason developers and Fortune 500s use serverless cloud infrastructure is because they want to build more and manage less.
The "Serverless Framework" is a developer tool that helps developers deploy their apps to serverless cloud infrastructure, without having to be an expert in that type of infrastructure. It makes it easy for developers to deploy Django, Flask, Express apps so that they auto-scale and pay only per request, never for idle.
Here is how you can deploy Express.js in seconds to serverless infrastructure:
Make no mistake, serverless cloud services are the greatest building blocks of all time. That doesn't mean you should use all of them, nor use them in the most granular manner.
As always, the architect should make prudent decisions.
- Austen @ Serverless Inc.
Pick a template:
• Serverless Fullstack App - https://github.com/serverless/components/tree/master/templat...
• Serverless Websockets Backend - https://github.com/serverless/components/tree/master/templat...
• Serverless API Backend - https://github.com/serverless/components/tree/master/templat...
• Serverless Website - https://github.com/serverless/components/tree/master/templat...
• Scheduled Task - https://github.com/serverless/components/tree/master/templat...
• & More - https://github.com/serverless/components/tree/master/templat...
The full statement from the source material says bloated cloud infrastructure "configurations", referring to verbose configuration files. Needlessly critical? It depends on your experience with these.
These, serverless, cloud, and more are abstractions. Fortunately, if the abstraction doesn't fit your needs, you aren't forced to use them.
When the Serverless Framework was created in 2015, there were only few use-cases you could do with a serverless architecture (an architecture built on auto-scaling, pay-per-execution cloud services, like AWS Lambda) because the services that had serverless qualities were few and immature.
Since then, a growing number of new and existing cloud services have "serverless" qualities. These days, "serverless" seems less of a fad, and more of an important chapter in the story of the cloud, as it evolves as an abstraction over infrastructure.
It's likely large and small cloud vendors will continue to introduce serverless cloud services to the market. All of which will continue to expand the number of use-cases you can do with a serverless architecture.
The Serverless Framework's initial application model is a great abstraction for many use-cases, and it helped hundreds of thousands of people start building serverless applications, easily.
Now, it's time to expand that model. Serverless Components represent multiple models, all designed around specific use-cases. This approach can better suit the growing number of serverless use-cases we're seeing. Additionally, as students of developer tooling and infrastructure provisioning, we've learned that by first knowing the use-case, you can build better infra/app automation that's faster, more stable and more relevant. There are many innovations we seek to introduce with the Serverless Components paradigm.
Overall, the "serverless" movement is about building applications with radically low overhead. As software eats the world, this trend seems to have come at an appropriate time. Serverless cloud services will continue to emerge and mature. Fortunately for us, they represent the greatest building blocks of all time. Who knows, perhaps a new golden era of software development is upon us.
Either way, Serverless Components is here to make it even easier for every developer to deliver radically low cost/overhead software.
Serverless components can be used declaratively (YAML) or programmatically (JavaScript).
It's the JavaScript experience that takes a lot of inspiration from React when you wish to write your own reusable Serverless Component.
Many common use-cases (APIs, Websites, Websocket backends, Scheduled tasks) are perfect for serverless architectures.
Serverless Components give you a React-like experience to deploy them more easily than ever.
---
Short video preview: https://twitter.com/goserverless/status/1156977112147845120
---
Here's a quick-start guide...
Install Serverless Framework
• npm i -g serverless
• https://github.com/serverless/serverless
---
Pick a template:
• Serverless Fullstack App - https://github.com/serverless/components/tree/master/templat...
• Serverless Websockets Backend - https://github.com/serverless/components/tree/master/templat...
• Serverless API Backend - https://github.com/serverless/components/tree/master/templat...
• Serverless Website - https://github.com/serverless/components/tree/master/templat...
• Scheduled Task - https://github.com/serverless/components/tree/master/templat...
• & More - https://github.com/serverless/components/tree/master/templat...
---
Make sure you have AWS credentials set up
• https://github.com/serverless/components#credentials
---
Hopefully these enable everyone to build more and manage less.
Enjoy,
Team @ Serverless.com