3 ms·

> was able to deliver the projects for 33% what it would have cost to deliver them with react or angular. That’s a pretty extraordinary claim. I know single s

> was able to deliver the projects for 33% what it would have cost to deliver them with react or angular. That’s a pretty extraordinary claim. I know single stack can be more productive, but that sounds very impressive. Could you perhaps talk details of: - styling blazor (eg. Bootstrap, tailwind); is it just drop in? How do you use it, eg. Without the tailwind preprocessor npm package? - interactive front end components (eg drag and drop) that lag badly when using SS blazor in examples. - bridging to native js (which is ultimately unavoidable in situations where you need integration like maps as far as I know) - scaling load on concurrent users (one ws per user right? Are you using the signalr service & functions? I tried this and found the long running azure functions are quite expensive to run. Do you have advice?

JamesBarney 4y ago
Sorry I misspoke I meant a 33% reduction in the size of the projects. So projects that would have taken 6 weeks in React took 4 Blazor server side. 1. We just dropped in a wrapbootstrap template. 2. We wrote some javascript for interactive front end components like drag and drop or rich text editors. It was a little more work than it would have been in React but not much and everything else more than made up for it. 3. We found it wasn't particularly difficult. We'd just put JSRuntime.InvokeAsync in a C# method. Used it for things like popups and initializing some js libraries. 4. We're only using Azure App Service and Azure SQL database. Our long running functions we just run as a scheduled service on the app service. (though eventually we'll to do some refactoring when we need to scale horizontally). We're a B2B SaaS company so our revenue is quite high compared to our compute usage. By our back of the envelope calculations we won't have to add another server until we're somewhere between 5 and 15 million ARR. We think we'll need to do about 2-3 months of refactoring at that point to allow for horizontal scaling. I wouldn't recommend Blazor-Server Side for B2C typical applications that have a low ARPU. The big advantage in development speed is we got the functionality of a SPA but at the development cost of a classic multi-page application.

JamesBarney 4y ago

Sorry I misspoke I meant a 33% reduction in the size of the projects. So projects that would have taken 6 weeks in React took 4 Blazor server side. 1. We just dropped in a wrapbootstrap template. 2. We wrote some javascript for interactive front end components like drag and drop or rich text editors. It was a little more work than it would have been in React but not much and everything else more than made up for it. 3. We found it wasn't particularly difficult. We'd just put JSRuntime.InvokeAsync in a C# method. Used it for things like popups and initializing some js libraries. 4. We're only using Azure App Service and Azure SQL database. Our long running functions we just run as a scheduled service on the app service. (though eventually we'll to do some refactoring when we need to scale horizontally). We're a B2B SaaS company so our revenue is quite high compared to our compute usage. By our back of the envelope calculations we won't have to add another server until we're somewhere between 5 and 15 million ARR. We think we'll need to do about 2-3 months of refactoring at that point to allow for horizontal scaling. I wouldn't recommend Blazor-Server Side for B2C typical applications that have a low ARPU. The big advantage in development speed is we got the functionality of a SPA but at the development cost of a classic multi-page application.