Hi RG,
I'm working in outssytems for the first time with this new client engagment. i'm a solution architect from a open source/mainframe background.
I'm working in outssytems for the first time with this new client engagment. i'm a solution architect from a open source/mainframe background.
- Occasionally connected = offline? - Yes wanted to understand offline functionality of Outsystems. The healthcare client I'm working for has majority of client locations that are in very remote areas, hence the proposal is to provide them smart apps via mobile/tablets so that the the data can be captured offline and then synced. The current desgin of the architecture is such that, the moment the URL page hits the server you'll get server not found. This is the reason I want to implement the hexagonal design pattern with microservices so that only specific functionalities can be exposed and not make the app a heavy weight.
- hexagonal and microservices design patterns = UI framework? - Hexagonal Architectural Pattern, will have multiple logical functions (Microservice), which will be bundled and deployed independently. In short please have a look into the below link. It'll give an idea of what I want to implement via Outsystems - http://geekswithblogs.net/cyoung/archive/2014/12/20/hexagonal-architecturendashthe-great-reconciler.aspx
- With respec to the UI, please find the attached fragmented UI model. The current client system design doesn't follow this but I as per the client requirements like to implement this. i was told there are technical challenges in this and I'm not sure how much complex it is.