@HartMilitary Hearing Peter describe a 14", 3.5T shell delivering artillery train as "choo chooing up and down" the railway line was the best part. Great series so far, loved this episode, thanks so much!
@alasdairpreston@SteGriff GraphQL maybe? That's been the big push I've seen of giving control to the front end. Would be moot if you were consuming someone else's data with CORS enabled.
@alasdairpreston@SteGriff That actually makes me think from this whole thread how you go about consuming external API's — can't think of a good example though!
@MerseyFerries@AppreciatePlc Not sure you can class hounding people on a Monday morning on their way to work as an activity. 😂
Appreciate what they might be trying to do (albeit the wrong time), but half a dozen staff stood in front of the gangplank with people trying to get bikes on is not creating joy.
@SteGriff@alasdairpreston Glad you touched on the wildcard as well. If you're writing your own service, this is definitely an important aspect, and not the end all solution!
@SteGriff@alasdairpreston Nice article.
The harder part is definitely server side, as with FED you're always dealing with the same languages, where as server-side has many implementations.
@AzureDevOps I've got a single artifact with two .NET Core packages (single codebase; one API front, one event front).
At deployment, I've got two tasks each targeting each package respectively . The second task always deploys to both functions (wipes API). Is there a known bug?
@AzureDevOps What's really strange is, even though the tasks are targetting different apps in Azure, the Azure deployment manager shows both the tasks deployed to both apps at the same time.