KatvaSoft Blog

Low-Code part 2

I don’t know why but the Low-Code fascinates me. In many organizations, there is a need for different kinds of applications. Some applications are consumer-facing and some are internal. Where the Low-Code could make a big difference is in the organization’s internal use.

I was thinking that could Low-Code and Microservices change the organization’s software development landscape? In my experience, many projects are trying to create microservices, but even if the backend is done with microservices architecture the frontend usually is not. In many cases, the microservices backend is used with a monolithic frontend. Logic then starts to move to the monolithic frontend, workflows and microservices orchestration are in the frontend. Then the actual business logic starts to be defined in the UI.

What if the business rules would be situated in the specialized “orchestration” microservices? Or in process/workflow engine? (One interesting new workflow engine is Zeebe) And then if there would be “real” microservices, couldn’t you have different UIs for different use cases? For example, you could have back-office UI made with PowerApps and a consumer-facing UI made with React, both using the same microservices?

So, if we would create microservices that would encapsulate the business logic also and the UIs would be just a way to use these. Then the first back-office UI could be done with for example with Power Apps. Then if a more sophisticated UI would be needed, the current PowerApps UI could be done with React or Angular?

Leave a Reply

Your email address will not be published. Required fields are marked *

Social Media Auto Publish Powered By : XYZScripts.com