Am trying to build an application where customer can customize the application logic via drag and drop. The drag and drop interface will be controlling the logic of the flow (let's say, customize the logic of a chatbot flow), how such applications are developed, knowing that the need to be auto-generated and deployed in real-time.
For further actions, you may consider blocking this person and/or reporting abuse
Top comments (2)
It's hard to say for sure, (I'm not sure if Twilio put out a developer blog on Studio), but it's very likely an "event-driven" system.
You can learn some basics on how this works with AWS here: aws.amazon.com/event-driven-archit...
Essentially, the application logic sits on top of a system of registering "listeners" to "events".
Typically events are created by the service. Things like "a user registers", or "Customer sends an sms to target number".
Your users can then register individual listeners to those events, and attach an action to them, like "send an email", or "send an sms with a form".
Actions are usually defined by both the service and third parties in order to extend functionality.
The front end is then responsible for allowing events to be linked to actions, and chaining them together arbitrarily to create "application logic".
Event driven architectures are typically microservice-based (often as a service mesh in my experience) where they communicate with each other over something like gRPC as opposed to REST in order to help keep latency and response times down, especially once the chain starts to get long.
Thanks a lot for your reply