{"action":"created","issue":{"url":"https://api.github.com/repos/dsuryd/dotNetify-Elements/issues/32","repository_url":"https://api.github.com/repos/dsuryd/dotNetify-Elements","labels_url":"https://api.github.com/repos/dsuryd/dotNetify-Elements/issues/32/labels{/name}","comments_url":"https://api.github.com/repos/dsuryd/dotNetify-Elements/issues/32/comments","events_url":"https://api.github.com/repos/dsuryd/dotNetify-Elements/issues/32/events","html_url":"https://github.com/dsuryd/dotNetify-Elements/issues/32","id":391482395,"node_id":"MDU6SXNzdWUzOTE0ODIzOTU=","number":32,"title":"Dotnetify for Composite UI provided by microservices","user":{"login":"jersiovic","id":4950766,"node_id":"MDQ6VXNlcjQ5NTA3NjY=","avatar_url":"https://avatars3.githubusercontent.com/u/4950766?v=4","gravatar_id":"","url":"https://api.github.com/users/jersiovic","html_url":"https://github.com/jersiovic","followers_url":"https://api.github.com/users/jersiovic/followers","following_url":"https://api.github.com/users/jersiovic/following{/other_user}","gists_url":"https://api.github.com/users/jersiovic/gists{/gist_id}","starred_url":"https://api.github.com/users/jersiovic/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jersiovic/subscriptions","organizations_url":"https://api.github.com/users/jersiovic/orgs","repos_url":"https://api.github.com/users/jersiovic/repos","events_url":"https://api.github.com/users/jersiovic/events{/privacy}","received_events_url":"https://api.github.com/users/jersiovic/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":1,"created_at":"2018-12-16T16:22:07Z","updated_at":"2018-12-17T03:11:39Z","closed_at":null,"author_association":"NONE","body":"I'm evaluating the posibility of using dotnetify for an app based on microservices where each microservice also provides its own VMs and UI elements with dotnetify.\r\n![](https://docs.microsoft.com/es-es/dotnet/standard/microservices-architecture/architect-microservice-container-applications/media/image21.png)\r\nThe idea is to use for certain views composition of different components dinamically loaded from different urls.\r\nFor example catalog microservice will provide composite view named product that will be composed by a product_catalog component that is a form element loaded from the same microservice,  product_commercialTerms is a component with a form element loaded from commercial term microservice and other elements related with product entity loaded from other microservices.\r\nIf I show only a submit button for all the view. When it is pressed  it will submit data on product_catalog view model, if validation of data in server side is ok view will be informed and an event on client side named Product_catalog_Update_Validated will be emited (using a library like that https://github.com/chrisdavies/eev ) it will be handled by all the other commponents in the view that will validate its part of the data on server side, product_commercialTerms for this example. If all of them emit an event saying everything is ok like product_catalog then container view will use same procedure for commiting all the data each one on its own microservice.\r\n\r\nAll of that is theoretical. Do you think there is any problem on using Dotnetify in this scenario? Do you think it is a reasonable approach? \r\nThank you"},"comment":{"url":"https://api.github.com/repos/dsuryd/dotNetify-Elements/issues/comments/447709706","html_url":"https://github.com/dsuryd/dotNetify-Elements/issues/32#issuecomment-447709706","issue_url":"https://api.github.com/repos/dsuryd/dotNetify-Elements/issues/32","id":447709706,"node_id":"MDEyOklzc3VlQ29tbWVudDQ0NzcwOTcwNg==","user":{"login":"dsuryd","id":14990482,"node_id":"MDQ6VXNlcjE0OTkwNDgy","avatar_url":"https://avatars2.githubusercontent.com/u/14990482?v=4","gravatar_id":"","url":"https://api.github.com/users/dsuryd","html_url":"https://github.com/dsuryd","followers_url":"https://api.github.com/users/dsuryd/followers","following_url":"https://api.github.com/users/dsuryd/following{/other_user}","gists_url":"https://api.github.com/users/dsuryd/gists{/gist_id}","starred_url":"https://api.github.com/users/dsuryd/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/dsuryd/subscriptions","organizations_url":"https://api.github.com/users/dsuryd/orgs","repos_url":"https://api.github.com/users/dsuryd/repos","events_url":"https://api.github.com/users/dsuryd/events{/privacy}","received_events_url":"https://api.github.com/users/dsuryd/received_events","type":"User","site_admin":false},"created_at":"2018-12-17T03:11:39Z","updated_at":"2018-12-17T03:11:39Z","author_association":"OWNER","body":"What you're thinking here is definitely inline with the project's vision.   Here's what I stated when I introduced dotNetify-React in a Medium article last year:\r\n> My desire with this project is to get to a state that can support full-stack micro-service on .NET platform: the ability to have a complex web app composable of independent front+back-end modules that can be worked on and deployed by completely autonomous teams with very minimal downtime. \r\n\r\nWith that said, there's still a lot more things to figure out to get to the production-ready state.  DotNetify and dotNetify-Elements are still designed for a monolithic SPA, so you may end up with roadblocks."}}
{"actor":{"display_login":"dsuryd"}}