How to Use NoCode as a Microservice in an Architecture...
summary
How to treat NoCode platforms as microservices inside a conventional software architecture: the talk explains using NoCode tools to build rapid automations that interact with multiple interfaces, and addresses integration challenges with existing technical and business constraints. It covers creating effective communication patterns between NoCode teams and traditional developers and between systems, and presents practical lessons learned (successes and failures) from a real implementation.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 1:05Problem and solution
- 2:28Existing architecture
- 3:09No code with Make
- 4:33Integration in architecture
- 5:57Decoupling via Pub/Sub
- 7:43No code quality standards
- 8:26Monitoring and metrics
- 9:10Cost optimization
- 9:51Alerting and notifications
- 10:32Log centralization
- 11:35Staging environment
- 12:21Results and outcomes
- 13:32Q&A
related talks
58mBuilding low code/no code services with Azure
40mIs No Code eating the software world?
41mEnable Enterprise Citizen Development with Low Code No Code
39mWhy You Should Look Into Low Code
28mLow Code Or No Code
28mWhy no-code is a game-changer for SME's
57mThe Future: Low Code & Citizen Developer
07m"Learn how no-code/low-code can make you more productive."
