@JoshDotOverholt@Dave_DotNet Yeah so, slightly missed the point but this shows a way, not proper, shows a N-Teir structure, which is one way of layering and enforcement through a repo doesn’t really scale across an org
@Geo5390@Rugby_Scoop This is exactly it, you can’t even see from this angle anything definitive - shouldn’t have blown up an immediate yellow a few minutes in… ref was over excited, could have done quick confirmation for everyone’s benefit
@Dave_DotNet but how… the type system isn’t built for it, ultimately. Sure, we get composable types, but the the power of discriminating them won’t be there
@mortenbraten@iStarr@kellabyte That’s a super straw man argument for stored procs… I don’t think it hits home on a number of points… any way, who uses sql properly these days…
@Dave_DotNet I would, because i like how it separates the UI layer from the system, so if you wanted to switch from API to console you can - or more importantly from old api to new api! it also provides great structure with co locating behaviour logic
@BugsBunny30143@Dave_DotNet Wait what? what do you mean generally limited threads… why would that be a thing? Most web servers I use have this as a configurable option, and as people make requests these web servers are usually scaled out along with that… I don’t understand this point