Why should you consider moving to serverless functions? Servers are expensive to maintain and during peak times the available servers don’t handle requests fast enough. Many are moving to cloud environments where the cloud provider manages resources dynamically and pricing is based the amount of resources actually used.
Container technologies like Docker give you the flexibility to deploy software on any servers and the scale you need. In the serverless model, you don’t pay for a server; you pay for the amount of time a server is actually used.
Microservices also support serverless computing, because they can be decomposed into small functions and scaled independently. Those functions are stateless and serverless - without any configuration required. Developers can take advantage of serverless infrastructure only if their applications leverage functions.
Announced at JavaOne last year, the Fn project, a container-native platform, is open source, cloud neutral to avoid cloud lock-in, and integrated with Docker containers. In his article, Johan Vos describes the Fn platform and how developers can easily write and maintain Java functions and test them in a standalone environment, or deploy them in a Fn server. He shows examples of functions using Java and Maven, and regardless of the language and build system you use, you can focus on developing your functions without worrying about how to run them in a specific environment.