sheets:Spreadsheet sheet = test spreadsheetClient->createSpreadsheet(sheetName);
_ = test spreadsheetClient->
appendValue(sheet.spreadsheetId, ["Product", "Sales", "Date"], {sheetName: workSheetName});
foreach var {product, gross sales, date} in salesSummary {
_ = test spreadsheetClient->
appendValue(sheet.spreadsheetId, [product, sales, date], {sheetName: workSheetName});
}
Deploying and testing ETL flows
Creating particular person ETL duties as microservices permits the complete ETL circulation to be deployed in a Kubernetes cluster. Every ETL activity is usually a pod within the Kubernetes deployment, making it potential to extend or lower the variety of pods of particular person ETL duties primarily based on the load. Nonetheless, organizations normally have a number of ETL flows, every with many duties. Moreover, these ETL flows could be owned by completely different groups. Subsequently, it’s essential to have correct CI/CD pipelines, permission fashions, monitoring capabilities, and a number of environments for growth, testing, efficiency validations, and manufacturing.
Ballerina can work with all frequent CI/CD, monitoring, and deployment applied sciences, making it seamless to combine Ballerina-based ETL flows with a company’s present infrastructure. For instance, Ballerina ETL supply code could be maintained in GitHub, CI/CD actions could be carried out utilizing Jenkins, ETL flows could be deployed on Amazon EKS, and the executions could be monitored utilizing Prometheus and Grafana.
