We are introducing the private alpha version of our platform in the coming weeks and we will be sending out invitations to companies, teams and hobbyist. Today, I’m excited to share a timeline for Fleet and the expected releases, ready for private alpha, public beta and a little bit of the resources we’re planning for GA.
TLDR
- Fleet Functions technology will be ready for testing for private alpha 🎉
- The CLI for deployments and authentication will be ready to start testing 📦
- The Console will have many features in the private alpha: invocation metrics, average time and health; rollback quickly; Secrets; Teams; Tokens; Preview deployments... 😎
- We will have support for the serverless framework ready in Q3 2020 🎉
- Public Beta is planned for early Q3 2020 🚀
- Many exciting features for GA (GraphQL, Github deployments, Dynamic memory, WebAssembly, Stateful functions ...) 👀
We are very excited about our runtime tests and provisioning of functions in the cloud, we are eager to know how people's functions will perform, we still have a lot of scope to remove latency from our infrastructure and we are excited about it because we can reduce it even more the function's execution time.
Stay tuned! you who signed up for the waiting list, we will be sending emails to you in the coming weeks, if you have not signed up for the waiting list just sign up at the end of the post 👇.
Recap: What is Fleet Functions?
Fleet is the technology for the next generation serverless, capable of executing functions with almost zero cold start for the JavaScript environment providing the Node.js APIs, scaling functions quickly and automatically. This also involves performing functions in isolation, with network protection barriers, I/O, memory and CPU usage. Read more about how our technology works and how it differs from the rest.
In summary you don't need to monitor servers or know if the server is online, it doesn't exist in the FaaS world. The functions can easily meet high demand, it is scaled up and down and you pay only for what is used.
The function is only invoked when it receives a new request, functions in execution can also handle new requests to take advantage of the Node.js event loop and increase the capacity limits of requests. To learn more about how it works, read more about provisioning our technology.
What to expect from private alpha
Private alpha will have many features that enable teams, companies and hobbyists to adopt and test their Node.js functions on top of our technology. The Console will have features to allow teams to work together.
- Deployments to production or use for previews deployments
- Rollbacks of deployments quickly
- Adding Secrets to functions
- Configuration of environment variables
- Metrics to measure demand (invocations, errors, avg response time) in a macro view or by function
- Create projects
- Add members with permission level to the project
- Generate token for the CLI
The CLI will have limited resources in its first version, only deployment commands and account authentication. We are planning to integrate with serverless framework for Q3 2020 and add the command in our CLI to set up a local development environment.
The functions will have a resource limit initially, it will not be possible to configure the memory consumption by function, it will not initially have access to the file system and we will not have log collect initially. These features will be available in the coming months.
- Functions are triggered via HTTP
- Functions have a maximum run time of 5 minutes
- Functions have up to 29 seconds to respond to a request, otherwise the connection will be closed but its function is still operating
- Functions can make outbound connections
- Subdomain runfleet.io
We will not initially support the deployment of static files, be it assets, css and html. We plan to add support later.
You may encounter small instabilities or perhaps a high latency although we are working to reduce these occurrences, we will only be operating in a region initially SFO2, we hope to expand when we launch for production. We will be refining our infrastructure to stabilize, reduce latency.
We plan to send invitations to those on the waiting list in the coming weeks.
Let us hope that the guests can help us to direct the product, giving us continuous feedbacks so that we can continue improving and refining the product, if you are interested in participating in private alpha, sign up below.
Getting Fleet ready for production
While we are planning and making the final preparations to start private alpha testing, we are putting together our roadmap for the launch for the public beta. We will be making another post about the preparations for launching a General Availability (GA) version soon with all the features.
Our main priority now is to launch private alpha for people on the early access list, we will have a short term for closed door testing to keep track and make adjustments before going for open testing. Our planning is that at the early Q3 2020 we will be opening the doors to the public with a more stable version of resources and our technology.
GA Roadmap
This is a list of resources that we are planning for our GA, the list is not organized by priority and we can change it at any time, we will be keeping you updated.
- Logs
- Serverless framework plugin
- Trigger function via GraphQL
- Emails alerts
- Github deployments and Github Actions
- Memory configuration by function (Dynamic memory)
- Custom domains
- WebAssembly support
- Stateful functions
- HTTP Cache by region
In the next posts we are describing these features in more detail and our view on each one.
Stay up to date about Fleet 👀
If you are curious about the next changes, keep an eye on our Twitter and the blog, we will be posting more about it.
Also be sure to follow Fleet on Twitter and subscribe to our Newsletter below 👇