The growing popularity of the Cloud-based service model has led to a plethora of acronyms ending in “aaS.” Platform-as-a-Service (PaaS), Software-as-a-Service (SaaS), and Database-as-a-Service (DBaaS) remain three of the most common examples of these service offerings in the tech industry. Businesses of all sizes enjoy cost savings by leveraging the Cloud in this manner.
Now software developers, trying to keep up in an increasingly rapid business world, have their own Cloud-based service acronym. Enter Features-as-a-Service (FaaS). Does FaaS give application engineers the chance to build more functional software faster and at a lower cost? Let’s take a look.
Code Reuse in a Cloud-based Wrapper
Code reuse is a traditional way for programmers to accomplish more by doing less. It’s one of the reasons libraries and APIs are so popular throughout the industry. We’ve covered this technology and API Testing extensively in the past on this very blog.
FaaS essentially just makes this process more componentized; delivering a library of functionality in a convenient Cloud-based wrapper for software engineers to use in their own applications. Instead of spending time reinventing the wheel, developers are able to focus on the unique functionality that makes their app special. Technology VP, JT Ripton commented on the FaaS trend.
“Whereas on the backend developers already are using pay-as-you-go infrastructure such as Amazon Web Services for cloud computing and services such as Stripe for payment processing, FaaS takes the same approach but applies it to the front end,” said Ripton. He also notes developers struggling with implementing a public API need to consider FaaS as an option when speed is of the essence.
Scenarios where Usage of a FaaS is Smart
A variety of FaaS providers are currently supporting common functional areas within applications, potentially saving development teams both time and money. Mapbox is one such provider worthy of consideration when compared to Google’s Map API and its arcane documentation. A plug-and-play model simply works more efficiently in today’s era of Agile and DevOps.
Social interactivity is another good example. There is no need to build social functionality from scratch, when a provider like Tapglue offers their own FaaS. Their service includes functionality supporting user profiles and news feeds, as well as interactive features like sharing, commenting, and more.
Agora.io offers a FaaS that adds real time communication – voice and video – to an application. This would be a boon for a game developer working on a MMORPG or any other type of multiplayer title. Concentrate on your game’s functionality; not on getting codecs to work properly on a variety of devices.
Ripton stresses the essential difference between FaaS and other types of code reuse like an API is the front-end component. This is especially useful for teams without their own UI design talent. He feels this is a natural progression on how software gets written.
“FaaS is just the next evolution of the mashup and code reuse trend that’s been picking up steam over the past several decades. It isn’t a “revolutionary” idea, or even truly innovative. But it is perfectly in line with the way we code today — it is a new application of something we’ve seen before,” said Ripton.
Stay tuned to the Betica Blog for additional insights from an ever-changing software development world. Thanks for reading!