With vendor lock-in, the main concern is the impossibility of embracing new services as part of the vendors' serverless architecture. This concern comes down to a fear of being locked in with a cloud provider.

It is recommended to use as many features as you can of the cloud provider of your choosing. You can do so by starting a pilot and evaluating the cloud provider; be sure to create an assessment of pros and cons before moving more code onto the cloud.

Don't let this concern put you off of using serverless architecture. Instead, it is recommended to start a proof of concept and evaluate the cloud provider. Serverless is a new technology that will evolve with time, and there are ways to keep FaaS independent, such as by using Spring Cloud functionality. We will work on an example of this in a later section of this chapter.

Finally, you should understand that moving to another vendor (from cloud-to-cloud) is not as difficult as it was in the past (when we were moving our application or legacy code to on-premises environments).