-
-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Roadmap/Production ready #3
Comments
Yes, it's a good point about the roadmap. We'll definitely hit 1.0 this year, but I cannot promise when exactly. I guess from a puristic point of view we are close, but it depends if we add a full hybrid mode within 1.0 or for later. We now have (at least, i.e., that we are aware of / in close contact with) 3 customers who use Piral.Blazor.Server. One of them is very close to production. Every time they detect some issue we try to close it very fast; in any case it seems to plateau right now which means from a stability point of view we are confident to be 1.0 ready very soon. Regarding the license; of course we won't be able to convince you / have all the answers for the future - but what I can tell you is that we don't plan on any license change or whatsoever. Our main product is consulting services (hire / contact us if you want to go through a potential migration from monolithic to distributed architecture) as well as software products for distributed frontends (such as the Piral Cloud - a leading micro frontend discovery service that plays nicely with our - as well as other - open-source libraries for micro frontends). I'll add roadmap to the docs with the 0.5 release. |
Thank you for the fast and detailed response.
Are there some examples for this offline replacements of the cloud feed 😉. As i understand this so far, the pilets can e.g. deployed to a private nuget feed. And the configuration, which pilets to use can configured in a dynamically changeable json file. The cloud service add additional functionality, e.g feature flags,.. and a more user friendly ui to manage the microfront ends. But functionally, they are the same? |
Well, we offer a Docker image - so you can just run it everywhere (e.g., on-premise - aka "offline"). Sure, you can also just have a JSON describing the MFs to be used, as well as a NuGet feed to actually get the MF packages (+maybe the same or other NuGet feeds for the dependencies). Functionality is pretty much the same, except that you will have a much harder time deploying + there won't be any live updates (so you'd need to restart the server or integrate something else - e.g., by polling the static JSON file) as easily as with a feed service; which naturally has events to be broadcasted. |
Been using for a long time now. It seems very stable to me. We are ready to go into production with it as it is. |
Did you trigger a preview build for the recent changes? |
It's automatically triggered / published. The preview version is 10938254736. |
Maybe just me, but I cant see it on NuGet.org. Only the old “Latest prerelease 0.5.0-preview.9323268279”
BR
Ulrik Farlov-Qvist
From: Florian Rappl ***@***.***>
Sent: Friday, 20 September 2024 16.48
To: smapiot/Piral.Blazor.Server ***@***.***>
Cc: Ulrik Farlov-Qvist ***@***.***>; Comment ***@***.***>
Subject: Re: [smapiot/Piral.Blazor.Server] Roadmap/Production ready (Issue #3)
Did you trigger a preview build for the recent changes? and publish to NuGet?
It's automatically triggered / published. The preview version is 10938254736.
—
Reply to this email directly, view it on GitHub<#3 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ALWY3AY5GLFKKD4FD5CT35DZXQYRNAVCNFSM6AAAAABG4YTGRSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNRTHEYDSOBVGM>.
You are receiving this because you commented.Message ID: ***@***.******@***.***>>
|
It's there. Just try downloading it. Nuget does not sort correctly. https://www.nuget.org/packages/Piral.Blazor.Orchestrator/0.5.0-preview.10938254736 (That's why I added the number - if you search on the page you'd get to the correct entry) Hope that helps! |
Now I see it. Neither NuGet.org nor Visual Studio NuGet explorer show it directly – bad sort order!
I have to manually select in the drop down…
Thanks!
Ulrik Farlov-Qvist
From: Florian Rappl ***@***.***>
Sent: Friday, 20 September 2024 18.57
To: smapiot/Piral.Blazor.Server ***@***.***>
Cc: Ulrik Farlov-Qvist ***@***.***>; Comment ***@***.***>
Subject: Re: [smapiot/Piral.Blazor.Server] Roadmap/Production ready (Issue #3)
It's there. Just try downloading it. Nuget does not sort correctly.
https://www.nuget.org/packages/Piral.Blazor.Orchestrator/0.5.0-preview.10938254736
—
Reply to this email directly, view it on GitHub<#3 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ALWY3A43MQO6MLBWERHZ3STZXRHVVAVCNFSM6AAAAABG4YTGRSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNRUGE2DAMZQGU>.
You are receiving this because you commented.Message ID: ***@***.******@***.***>>
|
New Feature Proposal
Add a roadmap.
Description
As the version number 0.* describes, the library is not production ready? I would like to know what features are needed to make the library useful in production. What is the target timeframe for 1.*?
Background
The library, framework is the final piece of my architecture. My company projects are now organized for micro frontends. But the deployment work as usual as monolith. Piral for Blazor Server would close the final gap. I would like to dynamically upgrade/deploy a pillet whithout to restart the complete application.
Discussion
Because it's not easy to integrate/replace this library in existing/huge projects. The decision to use it must be well ellaborated.
Pro:
Cons:
The text was updated successfully, but these errors were encountered: