ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Developer tools · #ballerina
Use Ballerina 2.0’s declarative @retry annotation to add robust retry logic to your HTTP client. Combine with a circuit‑breaker, test against a mock server, and consider latency and idempotency trade‑offs.
Ballerina moves HTTP routing and payload validation to compile time. Services attached to listeners with verb-encoded resources, typed records for automatic marshalling, and explicit error types reduce runtime routing and marshalling bugs in cloud-native APIs.
A decision guide to blocking versus future-based calls in Ballerina integrations, with a start/await example and a way to verify the latency change.
Learn how Ballerina automatically emits an OpenAPI 3.0 spec from your service annotations, inspect it locally, and customize the output for real‑world microservice documentation.
Learn how to declare an http:Listener, attach a service, and define resource functions to handle REST endpoints, plus how to enable HTTP/2 and avoid common pitfalls.
I am looking to harden a Ballerina microservice by limiting its permissions to only what is necessary. Ballerina provides first‑class service constructs and extensible metadata for cloud integration. How can I configure authentication, authorization, and runtime privileges (e.g., user, file system, network) using these language features to achieve a least‑pr
Deploying a Ballerina service as a Docker container and running it in a Kubernetes cluster involves compiling the source to a native binary, building an image that contains the runtime, and defining manifests that describe pods, services, and scaling policies. The challenge is to keep the image small, expose appropriate health signals, and manage configurati
When working with Ballerina services that persist state or rely on external data stores, ensuring that backup and restore operations are correct is important for reliability. What steps, tools, or practices can be used to verify that a backup captures the necessary state and that a subsequent restore returns the service to a known good condition? Please outl
When a Ballerina Swan Lake http:Client call fails TLS validation, the secureSocket record offers two levers: a cert field for custom trust (a PKCS12 truststore or PEM file) and a verifyHostName boolean that switches name checking off. Certificate validation is enabled by default, and the documented escape hatch for a name-mismatch failure is setting verifyHo
docker
kubernetes