CASCONxEVOKE is one of Canada’s largest combined academic, research and developer conferences, welcoming 1,500+ attendees and 150+ speakers. This year, the LoopBack team attended and kept busy collaborating with other attendees at the LoopBack booth and delivering a workshop at the conference between November 4th and 6th in Markham Ontario.
Day 1: Booth Showcasing Fast and Easy API Creation with LoopBack
At our booth we had a great opportunity to show how LoopBack can make API creation fast and easy. It looks like the use case we’ve shown in our poster is a common use case for our attendees to build APIs!
Day 2: Workshop on Writing Scalable Node.js Applications Using LoopBack
On Day 2, we held a workshop about writing scalable and extensible Node.js applications using LoopBack 4. We presented the challenges we faced for LoopBack as a large scale Node.js framework and showed how we are addressing those challenges in LoopBack 4. While we introduced the concepts that make scalability and extensibility possible (such as Dependency Injection, extension/extension-point framework and Inversion of Control), the attendees also had a chance to build an extensible and scalable Node.js application step-by-step using those features.
Day 3: IBM Developer Booth
Throughout the conference, the IBM Developer booth was showcasing different developer-focused technologies, such as Appsody and LoopBack. We were delighted to be there on Day 3 to reach out more existing and potential users!
Some attendees asked about cloud deployment story for LoopBack. We have been focusing on a vendor agnostic approach. For instance, we recently completed a PoC and added a tutorial on how to deploy a LoopBack application as microservices using Kubernetes. While we recommend to deploy your applications to IBM Cloud, you can also deploy to another vendor of your choice.
LoopBack’s success depends on you. We appreciate your continuous support and engagement to make LoopBack even better and meaningful for your API creation experience. Please join us and help the project by:
- Reporting issues.
- Contributing code and documentation.
- Opening a pull request on one of our “good first issues”.