Tools like jekyll, Hugo, or Hexo have popularized static websites in recent years. The so-called JAM Stack allows you to deliver highly dynamic content with no back-end layer at all. Additionally, developer-first APIs enabled front-end developers to build even more complex functionality. This they can do without leaving the browser sandbox. Let’s see how you can leverage modern API-first platforms to ship a solid prototype of a business application. The approach presented in this article might become a useful asset in your solution architect’s toolbox.
What’s an API-first platform?
- There is NO user interface (GUI). Or in some cases, there is a GUI but it’s secondary to the core product.
- Interaction with the service is through a web-based API. This is a programmatic way of connecting services and transferring data across the web in a machine-readable way.
- The value of the service is usually in the data that’s delivered (through the API).
- Pricing is often usage-based, meaning that the cost is based on the number of requests made to the API.