Spring Boot projects are exactly the kind of project that Serverless FaaS are great at taking over.  ToF(x) will convert your Java 8m Groovy or Kotlin source code, provided to us in a JAR or WAR file. For Maven projects, ToF(x) builds both a Lambda function (the default build) and a “boot” configuration that you can still use on your datacenter, EC2 instance or other VM. 

Some things to keep in mind before you submit your JAR or WAR file to ToF(x):
    1. Send only source code, don’t include .class files, as these are not needed and just take up too much space.  If you select to deploy to Lambda, ToF(x) will need to rebuild your project for Lambda anyways.
    2. Be sure you are using Maven (soon Gradle will be supported) builds properly.
    3. Note that since AWS Lambda, like all FaaS has a “start-up time” to load the JVM and Spring Boot, the first time the function is run, it may seem a bit slow to load.  Thereafter it will be faster until is it not used again for 5 minutes, then AWS releases the JVM and your function, requiring “start-up” next time.  You probably won’t notice this, we just thought you should know what is going on behind the scenes at AWS. ToF(x) is working on technology that will alleviate this, so check back soon.

AWS Lambda only supports Java 8. Most of the time this is not a problem for people, but if you do use special features of Java 9, 10, 11 or 12, you will either need to first recode those parts to be Java 8 compliant or use a custom Java 11 environment which you can read about here.  If you dont want to run the non-AWS Java 11 environment, Be sure your pom.xml file or build.gradle file is setup for Java 8 (Java version 1.8).   If the custom Java 11 environment is acceptable, ToF(x) will run the conversion for Java 9, 10, or 11 and remind you to use the custom environment.  Java 12 is not yet supported by Lambda.  We will keep you posted as this changes if you let us know you are interested.

Options:
Spring Boot currently supports conversion of the Java, Groovy or Kotlin JAR or WAR files (which may also use the Zip extension) and it is returned to you in just a few seconds.  Very soon we will also offer the following service options:
  1. Automatic Deployment to AWS – You don’t need to rebuild or deploy it yourself, just include your AWS credentials and let us know what email address to send you status updates to.
  2. Testing of Deployment – If you selected Automatic Deployment, we can also perform a series of comparative tests against your existing Spring Boot instance.
  3. Monitoring system installation and setup – We can deploy to your AWS account a system for monitoring your AWS Lambda based RESTful service.  The system provides both admin and end-user views of your function status and much more.  It’s something we highly recommend.

Which product code are you looking for with this option?  See the SciEssenc Store and look for product codes starting with 2FX.