Having been early pioneers of serverless technologies at Iron.io, our team has watched the market grow and evolve, and we believe the Fn Project will help accelerate the adoption of serverless, evolve the architecture to include full serverless programming models, and create a path towards true multi-cloud computing. In this blog post, I’ll cover the what and why of the Fn Project.
Open sourcing the Fn Project on stage at Java One (Click to view video)
What is the Fn Project
The Fn Project today consists of 4 major components:
- Fn Server is the Functions-as-a-Service system that allows developers to easily build, deploy, and scale their functions into a multi-cloud environment. It’s fast, reliable, scalable, and container-native, which I’ll discuss more below.
- The Fn Load Balancer (Fn LB) allows operators to deploy clusters of Fn servers and route traffic to them intelligently. Most importantly, it will route traffic to nodes where hot functions are running to ensure optimal performance, as well as distribute load if traffic to a specific function increases. It also gathers information about the entire cluster which you can use to know when to scale out (add more Fn servers) or in (decrease Fn servers). Read the complete article here.
For regular information become a member in the WebLogic Partner Community please visit: http://www.oracle.com/partners/goto/wls-emea ( OPN account required). If you need support with your account please contact the Oracle Partner Business Center.
Blog
Twitter
LinkedIn
Forum
Wiki
Technorati Tags: PaaS,Cloud,Middleware Update,WebLogic, WebLogic Community,Oracle,OPN,Jürgen Kress