 The current talk is No Code Platform powered by Python and Django, which will be presented by speaker Bhagwan Kumadi. Bhagwan is founder of Architect Corner, and I request Bhagwan to take the stage. Hi, this is Bhagwan Kumadi. Today I'm going to talk about the No Code Platform. So I'm just going to share this screen. So I'm currently working at the Director of Product Engineering with Value Momentum, and I have worked on various platforms, technology stacks. So the latest, my passion is more interested in Python and Django. And back in my college days, I used to work on various functional languages. And at that point, we used to have very old languages based on what you call before CC++ Java and Tic-Tic-A, right? And there were a couple of others which were very famous for AI at that time, right? And so it's a very present coincidence that I'm currently working on function programming, not just object-oriented. At that point, I was working in CC++ also. The other aspect is the Django part and the No Code Platform. I hope you're all familiar. So let's get into the presentation so that we can get into the actual topic. So No Code Platforms are very famous, and the current focus in this representation is more on health care and insurance. But in general, the No Code Platforms are shaping the future for enterprise. The first question is, okay, I'm a Python developer, what's in it for me? Why should I worry about No Code Platforms? Excuse me. Similarly, a mind map for presenting what are the No Code Platforms and why No Code Platforms? And presenting in health care, insurance, what are the challenges in a small demo and who else is doing this and what's next? So the immediate question you have is saying, Bhagawan, great, maybe they may be shaping the enterprise. But tell me, what is in it for me? Why should I care as a Python developer? So most of the time you have this dream, right? Can I have a No Code Platform or a code generated and deploy and upgrade my application on fly? And if you're an insurance company and an insurer, can I create new insurance policies for customers without code? If you're a doctor, can I provide technical support without any code? Can I have applications created to make my job easy? Might be the staff in the hospital or in a pharmacy or in an insurance company. Pharmacy, right? Can I create online pharmacy catalog updates and push them to the customers? Can I create applications on the No Code Platform? The dream of a business analyst without even thinking of any code, any technology, any technology staff, right? Now I'm going to use this mind map across the presentation so that we have keep in mind. So you have on the right-hand side, No Code Platforms and No Code Platforms, right? And you have on the left-hand side, domain specific things. So very common thing, domain independent things are you have an application, you have resources, you have market requirements, you have data sources, you have customizations, you have legacy systems and migrations and applications goes through upgrades and updates and you have in-house applications also not just applications which are for customers. And there are No Code Platforms which are code generators like the others are based on AI, Neural Schedule, like any other IT project like No Code Platforms require licensing, subscription, budget and it is based on a tech stack. Training is needed, it has metadata, denotes DevOps for deployment. On the domain specific side, you can get into insurance, home insurance, travel, health insurance, auto insurance, healthcare, wellness apps, digital health and payment processing which is common across insurance and healthcare. Now question is why No Code Platforms? So lower barrier to entry, deployment cost is low, shorter development cycles, reduced maintenance burden, enhanced customer experience, integration of legacy systems, improved productivity, right? And strong built-in governance, rapid prototyping and software development, democratization. So let's say you want to develop this for insurance. What do you do on No Code Platforms? You focus on underwriting process, claims processing, insurance code, customer buying and insurance policy, customer onboarding, adjustments, renewals, product life cycle management and dynamic case management. So according to the survey, 65% of applications will be created with No Code tools by 2024 and the market capital estimate rise over 21 billion by 2022 March. In healthcare, the same similar functionality but focusing on healthcare specific domain like patient safety, quality monitoring, monitoring, patient discharge, electronic medical records management, medicine management, appointment schedule. On the pharma front, we have complaints, audit, pharmacists, network communication, digitalization of research, direct visibility and medical supply chain management. Now, many of my customers when they'll take a look at this presentation, say it's very, it's really well structured. You have a mind map, you have what's in it for me and talked about example, the processes for the No Code platforms. But can you tell me what are the challenges? What are the obstacles? What are the issues? First thing is the maintainability which we are going to talk about is regarding the upgrades and challenges and in terms of maintenance, in terms of new technology stacks which are coming in and also upgradability, performance. Even a new technology stack or a new UI framework, remember comes in. Now currently, let's say the No Code platform has capability to build AnglerJS, right? But certainly the customer says, but no, no, no, no, the latest I heard is React is, React and view.js are the very far, very far popular and I don't like AnglerJS, I want to have the No Code platform build the React application. Next customer says, no, no, no, view.js is really great, I want to build a new.js. The latest customer which I heard is saying, no, I don't want to focus on UI frameworks, I want to focus on multi-experience development platform, I want a multi-experience platform and no code platform which worries about different experiences, not just UIX, not just the rest of the frameworks. I want to have conversational experience, I want immersion experience, I want different vertical IVR based, SMS based, social media, what's up based? I don't want to just get locked on Angler or React or view.js. I want to be independent of channel, I want to focus on amni-channel, right? But those are some of the challenges on the maintainability and also upgradability. How do you go about upgrading? Let's say you have a technology stack which is fixed, but there are versions, there are changes, there are new features coming in with the same technology stack. You need to worry about all those upgradability and provide those features within the no code platform. Similarly, performance, can I deploy this application for 1,000 users? In insurance, let's say 1,000 clinics, 1,000 doctors. But tomorrow another customer says, I know how 10,000 doctors across India, can I deploy this for 10,000 doctors will the application work on the cloud? So those are some of the performance related challenges which we need to focus on. And also security, right? Will my data, use my data secure, right? It does it, like if it is healthcare, HIPAA is the HIPAA compliance, what do you call it? Does the application conform by HIPAA insurance, HIPAA compliance? Similarly, data security, PCI DSS, right? Information security standards. And scalability, I want to take this from one continent to another continent, new geography, right? It's not just adding more, creating a new instance or it is multi-tenant adding more tenants. But also you need to focus on the geography, specific taxation, geographic specific, culture, internationalization, localization. The many things which come up when you want to scale across multiple continents, multiple geographies and some of the countries like Europe and North America will have compliance standards, regulations, even so simple thing like pharmacy, but to take off in India, right? We had to go through even pandemic, I think the government was really tough again as a pharmacy. Only some of the cases when there was lockdown, they allowed them to deliver, right? Not all of them were allowed. Now, let's step into the core problem. Now understanding the obstacles, understanding the challenges, how do you go about overcoming them? What are the solutions? Now, let's take a step back, right? What is, you have an application which you want to build. What does an application architecture consist of, right, different modules? You have user management, user onboarding, right? Once it gets user registered, user login, authenticate, authorization, but to access different modules, right? And the user gets onboarded, he has a profile, he has payment, payment or a wallet enabled, payment of what you call service enabled, or he has a wallet, right? To buy a product or to buy a subscription for a particular application. So these are very basic things, but you start out from those modules and keep adding new modules which are more functional. And all of these require services, right? Back when you have some need to have an authentication service, authorization service, registration service, onboarding service, and you have visualization layer, right? Here, I guess, put mobile and web, but some of them are interested in not just mobile and web, I want in SMS, I want IVR, I want immersion experience, I want convolutional experience, chatbot to be connected to these services. And also some templates, right? There's a template which a customer want to over what you call use, use for a specific process, right? And that consists of events. The template consists of multiple events, multiple entities, and entities are tied up with events related to simple things like create, read, update, delete, or more complicated things like notification, workflow approval, and so on. So underneath, you need to have the services layer, the actual classes which are built, and the data access layer, the persistent service where the data has to be persisted to a particular data source, right? Or any other external or internal data source or service. Now let's look at from the UI frame. So you have the backend very clearly. There are services, there are data, data sources, and you have data management persistent services on the right hand side, and you have service bindings. On the left hand side, an application typically consists of pages and desktop views or web views or mobile, and each of that particular page will have controls, right? Typically it has a label and it has a specific control type, right? And it needs to get input from somewhere or the user has to input in, right? It's read only, right? Or the person has to type it in. So these are some of the variants within the pages and controls. Now that's on the left hand side, and you have services which provide the data either to update the data within the controls or take this input and send it to the data sources. So these particular pages, whenever the, let's say, take a simple form, a login form, the data comes in, you want to send it. You need to have a service on the other side, a login service, which takes this username and password, right, to a service and push it in, right? That's a request which comes to a login service. Login service goes back to the data service, business service calls the persistent service, gets the username, checks for this particular user if it exists, sends back the response. So that's when it comes back, right? There will be a, what do you call that, a controller, like page controller or a UI controller or a framework-based controller which looks at and then moves the user from one page to another page based on the response, right? Let's take a complicated example, not just login service, but a complicated example, there's a dashboard which I'm clicking on the menu and then you get a sender request to the services saying that please get the data or let's pour all the customers or order all the products. Let's say order all the products, the response comes back and the response comes back and gets a JSON and this has to fit in a table, the table has to be rendered. So you see that the service bindings, similarly the UI bindings have to be created with the table and the data. Now let's look into the local platforms, right? Now, stepping before we get into no code, let's look at local programs. Local is more like code generation, right? What do you need to generate an application which consists of pages, which consists of services, which consists of data services and database schema? So you have a channel, you have application which consists of views and services. A view consists of view identifier, view fields, form or form fields and view types like CRUD and services like method and request and response. So underneath we have DevOps, cloud, databases, like what you see in any typical architecture. The local platform uses this particular metadata to generate code. Once the code is generated, you need to have Maven or some kind of built in which builds the tools, builds the application, sends it across and deploys it on the cloud, right? Now that's local. Don't let's say we want to go to a no-code platform. How will this work? Like we discussed, you have modules, you have services, you have templates and events, right? Now let's go further than persistence. You have analytics, messaging, multi-channel services and templates which are related to tasks, right? I need to create particular form and create an application, create an account, let's say in insurance domain. And I need to, I have a form which I have to use for a user to fill up the form, have calendars, right? Which I have to show, display when I pick the date and so on, workflows, content, translators, cross-automation. Similarly, like we talked about events like not just CRUD events, not just notifications, alerts, activity monitoring and external app notifications. Now it's not just a no-code platform. The next requirement is I want to make this more like a software as a service, which I need to provide to the user. So typical features which are there in a software service like module management, subscription management, metering, billing, auditing, calendar management, document management and configuration management. So the customers say it looks good conceptually and understand how you store your world from application to no-code, to no-code platform and what are the features and how do you make it service after the service and how customers or users use it. But I want to see this in a specific example. It's two abstract and pages, view, service binding, view binding, it may look good for an architect or a developer to understand, but it looks very conceptual, very abstract and not really pragmatic, right? So give me an example and show me how it's going to work. So let's pick insurance vertical. You have modules like code management, policy creation, self-service, payment processing, claim processing, billing management, operations handling, data management, data reporting, commissions, authentication, authorization, roles management. Now what are the integrations which are required for other modules which you talked about insurance to work? Okay, typical insurance like you want to have auto insurance or life insurance or medical insurance is basically you need to fill up a form, send the information, get the test done and the results have to be provided to the user, the agent and agent has to give back the policy. On the integration, what are the integration, backend integration which are required? One is custom relationship manager, they are AI platforms, fraud analysis, geo coding service providers, if it is property and casualty, you require fledged hazard services. In any insurance you see a chat bot right-hand side, it keeps popping up in a test messaging service, you need cyber risks course, loss cost, replacement cost, crime reports, if it is what you call home insurance, then you want to know for that particular area what is the crime rate, fledged hazard metrics, predictive CRT modeling. So these are some of the backend services and integrations which are required. Now we have all this ready, the integrations, you have the modules and how do I do this practically? And this is where you have to visualize, you have a business analyst where you have a process design which needs to be done, you have to sketch the process and we talked about for each process there's an input and there's an output, input is most of the time a page or an email or a trigger which even which comes which has data, which has to be processed by a public service, the response comes back and you have the output being rendered or you move to the next next process by some event or an action by the user. For this you need screens, so how do you go about designing these screens? The screen designer needs to be there when you drag and drop, you have a pallet and you bring in the controls, you create a page, you create a form, you have a layout and place them properly and you have actions, right? Buttons are some actions which needs to submit this particular information, render this particular screen. And what if you have a custom widget that you don't like this pallet and want to create it a widget, but you have custom widgets. I don't like the standard layout, let's slow layout or three by three grid, four by five grid, I want custom layout, right? Like the fancy UI, UI screens, like what, how unicorn screens are there, right? I want the custom layout, I want things more, what do you call, not linear, more complex or not symmetric, you want asymmetric. And similarly, custom dashboards and custom search. Now, we have the designers, so we have the screens design, we have the backend services, we have the modules which are working, but also I want guided workflows, right? Not simple integration, but I want a user to be taken step by step. If for example, to send a SMS, it has to be more like a wizard, right? Or old times wizard, but it has to be more like a bubble driven where user knows what to do, right? He clicks on the particular control and you see a bubble coming up, right? For SMS integration, how to compose email or collaboration tools for content management, customer service, advertising services, service, project management, marketing, schedule and chat tools. See, this is the next level feature. Or you want to have compliance level features for HIPAA, PCI, DSS, GPDR, WCAG, ADA, FERPA, IRDA at FEMA. Now, let's say we have all these applications done and we showed you the customer, customer service is great for mobile and web, but I'm not just happy with mobile and web, I have IoT data coming from IoT sensors, I have wearable data, people know latest, I heard Facebook has glasses, please do me Google or some of the other companies used to have glasses and watches and sending information and that information has to be composed on the cloud. I want to create a cloud data, what data on the cloud, right? And then process the particular data and create apps around the particular data, like an IoT cloud or wearable cloud, okay? Or the conversation experience, I have chatbots configured on Google or the Dialogflow or Amazon legs or IBM, Bluemix, Watson, right? Or any other platform, I have one in my own chatbot, but it needs information, I can get the account data, I can get the, what do you call here, the person's name, I can get the check number, right? I need to tie this up with my banking services or insurance service, I can get the policy number, I want to back in to work with the chatbots. It's similarly AR, AR, VR, like a property concern, casualty, insurance, right? The person is saying yesterday, what do you call an apartment, it takes a photograph and you have the location for this on mobile, but I want to tie this up with the backend services to provide information to the user, how safe is this particular area? What are the hazards, previous hazards that have happened? All the information which is required for the home insurance or property casualty code will be provided, all the services have to push in that information, right, crime rate, weather, flood hazards, what are the problems with this particular building, right, if you have any historical information and that helps the user to understand, also agent to give you to assess and explain the code, why this particular code is very high for property casualty insurance. Similarly, PWA desktop, and what do you require for all this, whole of this multi-experience development platforms to work, the mesh app service architecture? So let's see what is mesh service mesh architecture, right, you have your delegates, you have various front-end frameworks which you talked about like chatbots, voice platforms, IoT platforms, ER, VR, AI platforms, variables, and each of them will have chatbots frameworks, if they're on frameworks, interaction frameworks, like voice framework, IoT framework, in the case of, yeah, you have NLP frameworks, and there are gateways like service mesh gateway and there are gateways of which these frameworks talk to, right, and back-end you have services with chatbot and you have, if you're using IBM, you'll have Watson services, if you're using Amazon, you'll have Amazon Lex services, if you're using Dialogflow, you'll have Google Cloud services, or your own services which are persistent analytics and messaging and multi-channel, all through going through the service mesh gateway where the services can be composed and sent across to BFF, which is back-end service for front-end service, which is a framework for front-end framework. And what are the capabilities of this particular service mesh platform? You can have lifecycle management, you have security, traffic management, policy management, multi-tenancy, extensibility, and multi-cluster operations. I have a small demo, so I'll just share that. Sure, so you can actually register on- I hope you're able to see the video in fast forward. I already registered, so I'm going to log in. So you can update your profile and you can choose the subscription, subscription has a payment type, the credit rate, the way to pay for the back-end, and subscription types of grants and the approach and cost. The world subscription covers everything like having health, life, all kinds, policy management, payment processing, building a self-service portal, and the cost is something to do with it. If you look at grants, it only has clients for other types of insurance, like health, life, auto, and home, the cost is $522. Silver has health, life, auto, and home, and has clients for policy management, cost is $622. And custom is where you can have and develop your own services, and you can have portals for health, life, and auto, and home, and integrate those services for clients for policy management, or payment processing, or building a self-service portal, and they can have enhanced models built also, which can be integrated for the other models. The cost is $452. So you can configure the portals. Each portal will have a layout, like if you're logged in to manager to have capabilities to access menus, like assigned profile and tasks, agent is assigned a profile, it has assigned profile and grant, and you may have server layouts where you can choose a assigned profile, assigned profile, crime, and assigned profile, crime and failed reports. So as the org admin, I can create users and send them email to get started, and they have different roles, customer, agent, manager, and you have agents in server, and they have names, and they all belong to my organization, and I am the organization admin who manages the users in terms of the roles, the layouts, and also the data sources. Let's say the server protein requires the data sources for crime data or threat hazard data, or likely for life insurance and mortality rate, I couldn't include, but we can have data services, services is configured for life mortality, or apartment calls, or loss calls or replacement calls, or assets itself. And also, you can pay for the subscription. In this case, let's say you have selected a good card, you can pay for the grant subscription, or credit card, or PayPal, or Netbacking. So now let's look at the other side of the platform. We have seen the org admin. Now we are looking at the customer portal. So here again you can register, and the org admin sends the email and click on the register, you have the organization, the road setup, you can set in the password. So the customer portal has the health insurance, the premium, the policy coverage, and the nominee, and the premium per year, the home insurance, and the number of claims, which are processed. So you can update your own profile. You can also pay through debit card, the premiums, credit card, PayPal, and Netbacking. And that was the customer portal. So let's look at the manager. So in the manager portal, you have what you call various tasks, you can manage your own profile, Thomas Smith, and you can also have what you call agent and server here. And you can assign this method as an agent, and you can select different assessment or output or create policy. So after creating, you can look at the tasks which are assigned, and you can check who has the various tasks assigned. Let's look at the agent portal. So agent portal again, you can manage the profile, and here you see the tasks which are assigned for the agent. Now let's look at the server here. The server got the task assigned. Crime reports, if you go back to the data sources what you're going to get, you're going to get uniform crime reporting, which is the data source here. And you can put it on select. Similarly, you go to flit hazard reports. If you have different flit hazard data, and you can search for the zip code. So that was the demo for healthcare and insurance. So I'm going to go back to the presentation now. So that was the presentation of the demo based on Python, Zango, and MySQL and using the HTML file. Now, many of you will have this question in mind, Bhagawan, it's a great demo, but how do I get started? What are the basic things I need to look at? So for anybody, whether you're a developer or from insurance or healthcare or staff, what are the scalability requirements? What is your plan to improve new users' cases? You have this basic functionality, but what else you can add? It create a small roadmap kind of thing and you can jot down the features. What is your current and future user base? Is scaling horizontally an option? You plan to deploy your applications on the cloud or you have announced what is your current technology stack? What are your future requirements and what technology stack will help you to get to there? What are your compliance requirements? Is your platform microservices based? Does your platform support other rest services or you have to integrate with any other external rest services or any other external data sources? What is your budget? What is the pricing model supported by the no-code platform? So these are some of the things which you need to first jot down and create a plan if you want to get started. Sorry to interrupt, Bhagawan. I think we crossed 30 minutes. So please find it up soon. I just have two more slides. Can you finish it soon? Yeah. The next question you have in mind is I have an existing local platform, right? It works great. I just want to make it no-code platform. So how do I make it, right? So first candidate for assessment where you want to move them into no-code platform are the services. Second is funds, pages. Then you look at the database schema and then the whole integration services or the deployment or the cloud, right? So you look at all these components and identify what are the variants which I can configure from the UI, like an admin, right? Similarly, as a user or application developer, right? How do I configure and make this work either runtime or design time, right? Or deployment time. The next question you have in mind is I already have a microservices based platform, right? For insurance or based in India, by-based in India or Europe. I have a microservices platform which provides me all the data. I'm not going to be talking about crime rate or anything for proper decasualty or life insurance, actually services or healthcare providing all the data. But I want to make this no-code, right? To make it more like an insurance platform. So it's more like a methodology where you start looking at universal connectors, right? How do you go about connecting to any possible data source? Like any possible data source. It's not just rest, right? It can be old soap, it can be JAX, JAX, what do you call it, JAX, JAXR, right? Or JAX messaging. It can be any other protocol but you should have capability to connect and provide those connectors. And as you know, these are all external data sources, right? Data source is not just with which you are not in your control. You don't even know the database schema, right? Sometimes they are not even exposing the services. They might just provide you the lower data sources to pick the data, right? And also you have to provide, you have to worry about authentication. But each of these, they provide you the credentials how to connect to using universal connector to a particular service, a particular data source. And there is authorization. You can only access this particular part of the database schema, this particular part of service, not all the methods. Even within the method, the data which comes in which will be parsed. And you have access control, rate limits, request headers, which you need to pass on, pagination of data, right? Sometimes the services, you keep sending the information as you keep saying, one, two, three, four, like you've seen in UI at the bottom here, one, two, three, four pagination. Similarly, the rest services will have a parameter saying that do I want the limit of reserves which will be sent there will be 10 or 20. I want the fourth row, which is the fourth set of each consisting of 10. It's similar use of defined variables and so on. But you need to capture all these first and then make them configurable through a no code platform. Then you should be able to realize the next step where you want to take this and bind them to the UI services or create a multi-experience adderment platform which needs to bind the immersive experiences or convolutional experiences or IoT or variables to the services which is coming up. The other last question is who else is doing, right? I just added this. There are many, many people, many companies which are focusing on chat boards, emails, web and connectors, right? Like we talked about the universal connectors. Some of them are already available like automate.io, like Zapier, IF, triple T, trade.io, right? Parabola, flow, block spring, action desk, right? And that's a commercial friend. Robot open source, AppSymbol, Convertigo, Zoget, Mendex, Integui, Sartcon, VisionX. The last thing is, so you have this roadmap back on, what is next, right? You have the no code automation platform. So what's next? The next level which you are looking at is not just the stop at the no code platform for domain specific. The idea is to evolve this for no code AIML. Evolve this for something like OpenAI or BERT where you have the transformers. It have make it capable of presenting explainable AI features. It's not just taking a decision. It's not just having AI services for what you call decision making or classification or supervised learning or unsupervised learning, but also explain some of the rational decisions which are required for a person who is taking this particular data to understand why this particular decision is made. The classic example is there's a customer who's looking for an insurance code. They look at the various plans and his information, look at the developer and present possible options for code, let's say auto insurance for the family. They provide different packages. As a customer, I would like to know why package one is good versus package two. Why was the decision made? Is just the cost or something else which is happening behind, which could be explainable to the customer. Similarly, agent needs to know if the internals, why was this decision made? Let's say some actual sense data which presents saying that based on his health and so on, his code is very high for health insurance. You should be able to explain, the agent should be able to explain to the customer saying this is the reason why your health insurance is very high, right? So that's the next level which we want to reach. So thank you. If you have any questions, that's a good time.