This post is a looong overdue follow-up of a sort to my previous post on the config API: https://medium.com/@pubuduf/ballerina-config-api-f6a9c455267b. …
Ballerina 0.970.0 introduced HTTP caching support. It does so by adding a caching layer on top of the plain HTTP client in Ballerina. The caching layer, complies with the RFC 7234 specification (it is not a complete implementation of the spec though). In addition to this, APIs are also provided for handling caching at the server side. In this post, we’ll take a look at the client side of caching using Ballerina 0.975.0.
Prerequisites
- Some familiarity with Ballerina language (syntax, services, endpoints). The Ballerina by Example page would be a good place to start.
- HTTP caching (basic understanding of how it works. This excellent article from Google would do…
Edit: This post is now heavily out-of-date with the newer versions of Ballerina. Please refer to the following post for up-to-date info: https://medium.com/@pubuduf/configuration-management-in-ballerina-b952cae80c49
Ballerina has been around for a few months now. It has come a long way since its launch back in February, constantly tweaking, improving and adding things based on user feedback.
Ballerina strives to be configuration-free as much as possible in order to make it hassle free for the user. But inevitably, there will be instances where you need to be able to feed in configurations dynamically, rather than hard coding it. To address this we added a config API to Ballerina. The API is two-fold: one gives an API to the Ballerina user which will allow the user to feed in configurations from various sources. …
About
