Video

👍👍

👍👍

"HTTP APIs don't magically remove Coupling" Do queues next!

Cache shouldn't be used to fix unavailability. Cache is small and expensive and it's used to store only the info that is more likely will be needed in the future to improve the performance. I recommend reading "Designs Data-Intensive Applications" by Martin Kleppmann. Please reply to this comment

Great take, really enjoyed this video

More typesafe config than dockerfiles seems attractive

Isn't this supposed to beef up your local development? I think you are missing the point with Aspire.

First, thank you for these videos. I seem them more as a discussion, kind of a "retrospective" in a way, rather than a discussion of "ok, based on what we've learned, let's do X". Part of the difficulty for me personally is...how do we measure the effectiveness of one approach, vs the other? And get visibility. For example: Implementing a system using a more monolithic approach, vs a microservice approach. It's difficult to see the "real" costs of everything from start to end, and to see the true measurement of latency, performance, maintainability, all the side tasks related to devops, etc. I feel like with topics like this, the industry does a "let's try this for 10 years...ok, now lets try something else. Or something we did before. Or a hybrid.". It all just seems like guesswork and experimentation, there's no way to get a clear answer when it comes to effectiveness, or we wouldn't be in this situation.

What's with the Hype? There is no hype. It's literally just Fowler tweeting about his newest framework pet project because he wants to make it a thing.

Welcome to IaaS

this is for local dev only...no place in prod. This (with the help from .Net 8) removes the need to use docker locally.

To me Aspire seems to be one of those things that can make previously straightforward things super trivial and previously complicated things next to impossible. At least for the time being. If you're not familiar with microservices and you're starting a new microservice based project, it can save you a lot of time. But then again you probably shouldn't start a completely new project using microservices if you don't have enough experience with them. Or even if you do. Imho you should resort to a distributed architecture only once it's absolutely necessary and there's no reasonable way to avoid it.

I've been playing with it for a couple of weeks since GA. The local dev experience is nice so far, though I haven't tried it on a large microservices implementation. I think there is value add with the C# layer of abstraction on top of docker. I don't care what ports are what, I just want to say which services can talk to what. That's a problem it seems to solve. ServiceDefaults is really nice to have. It seems like a solution that could be shipped outside of Aspire, maybe, but it's nice to get some recommended defaults for those cross-cutting concerns. The deployment story is not there yet. It works if you want to use the exact default resource types, but customizing things gets a bit gnarly. infra synth to bicep or using unstable APIs in C#.

I really liked the Orleans example but the big problem I see is everything being one big solution. First I don't like gigantic solutions hard to use and navigate. Second multiple teams setup where I don't run everything in Debug because it's some others team responsibility. I am not sure how this will scale.

It's just pointless right now. I was hyped for dapr and that turned out pretty bad when i tried to actually use it but aspire is not even on the level of dapr. It reminds me more of service fabric, which was truly awful.

I'll continue to work as a C# Dev for work, but C# is too much for side projects which is why I've moved on to Go

Great honest review! Local development is definitely where we add the most value! We’ve got lots of feedback as to where to spend time improving (multi repo etc etc). Deployment will be a longer journey but we will get there! One of the big advantages that people are beginning to realize is the extensibility. We’re seeing people build some very cool things by extending the model.

It looks similar to spring cloud. Your app code depends on "cacheService" and the runtime figures it out; locally that means spinning up a docker redis, in dev it means no cache and in prod it means a managed redis.

I recently converted my solution to Aspire - 20+ projects. I'm glad that I had my own service defaults. But it was so tedious to do. I had been using Tye before, and I liked it, but switched to Docker Compose when that experiment ended. I kind of miss the YAML now.

The standalone aspire dashboard is the easiest way to see Opentelemetry data locally. Using it daily already. Not sure about the rest of aspire. Feels like there's potential here but also feels like this might turn into yet another excuse to do microservices in the wrong context.

I don't see a lot of value on aspire at this moment.

Personally I find the standalone Aspire dashboard to be more interesting. I see it as being very useful with local dev / docker-compose scenarios so that I can get visibility into my OTEL data during local development but then replace it with an enterprise grade APM solution for staging and production environments.

I've been playing around with it and I think it has a lot of promise but it falls just short right now. Specifically when it comes to testing, I'd like to use the same AppHost configuration to spin up instances of my dependencies for integration tests and to configure test services like you can with WAF. It feels very all-or-nothing right now but hopefully, it'll be more flexible in the future. I've been using a combination of docker/compose/makefile to simplify local setup and I don't think I can walk away from it yet. However I might use both Aspire and my current tooling together in my next greenfield project to get a better sense.

how I see it the "needing javascript" isn't about javascript being somehow superior, it's about javascript being the only client-side programming language on the web and webapps requiring client-side logic to have a good UX. As you pointed out the popup problem is solved by preloading, but how do you achieve that? It can only be done with javascript.

This video is my first look at Aspire and I think I can ignore it for while (maybe forever)

Still need to look at this more, my gut reactions to this were a concern about centralized configuration and not quite understanding how or if various teams working on parts of a system would or could use this. It feels like a solition in search of a real problem. Really feels like DevDiv is being asked to try hard to influence devs to use more azure instead of solving real problems. Apologies for the sinicism, I've just been doing this too long. Maybe it will be the next big thing and i'll see the light, as of now though I'm not convinced.

I’ve used it in anger. It’s decent enough, but it’s maintained by a knob (David Fowler is horrendously arrogant and unhelpful). It’s a solution to Microsoft’s problems (a bit like azure which is overpriced hosting). It’s nowhere near production ready. Perfect workflow is for developing with dependencies, avoiding docker compose for local is ideal. Most people won’t benefit though, as if you’re running real microservices it doesn’t work well across teams.

Meh... If you're a billy who's just starting out with microservices it might be useful - but is it "better" or does it solve a problem that didnt exist? I'd sit on that fence

That giggle at czcams.com/video/maVXnkYEDIE/video.htmlsi=j86VSrADgTAwqrkP&t=23 We already know Fowler's brain is connected to Twitter, he's in the matrix already

The only coding channel with 99% talk and 1% code snippets from twitter

I completely agree! Your customers don’t really see most of the tech behind, and even things like waiting for popups or loading times are not as important as the value the service provided. Delivering 100% pristine products is a fairy tale made by folks, who never shipped things to production, but have 100% coverage on their hello worlds.

Honestly, 3 years of Hey everyday and it is a slow, high churn product that hasn't seen core improvements since launch but what has been improved is their bottom line, launching new products, optimising cloud costs. It's a great example why you would care about client JS or whatever gets the job done but server side apps just doesn't. A non-dev would say it's slow and they don't like it but you can convert that to say customer care about JS if you add nuance so yes customers doesn't know what words to use but they do care about JS

Hey this is great content about software architecture

Wait so the whole thing here is that if you simulate a slow connection then the app is slow because server responses are slow? That’s kind of a bizarre take given that most of the time that’s not going to be an issue. Even if the user does have a slow connection, the app will need to make some a request to the server at some point and the user will most likely experience some loading time or potentially some other type of negative experience (like seeing stale data but the client not making it obvious that loading is taking longer than usual). A slow connection is going to produce a poor user experience regardless of how much JS you use - you might be able to smooth that over with some client side logic, but is that the most important thing if 99% of the time your users have a stable fast internet connection? Which can reasonably be expected for the businesses Basecamp and Hey serve.

This was a mature take on this. I was watching Theo giggle making fun of this app, and comparing them to Google. He make some fair points but there's a an immaturity there that needs to be addressed. Personally I was pressured into building a very large project solo and when I was done I personally thought what I made was garbage, but the customer was so happy with the result. You're right, done is better than none. There are so many factors into getting from A to Z and sometimes we have to cut C and D out in order to finalize something. If we have the time, we can go back and improve on it. But you need a thing to exist first in order to improve on it.

Someone stole this guys upper lips

Your last point is by far the most important, thank you for making it. The best software speeds up a workflow, nobody cares about about every little nuance unless it is egregiously slow or adds an extra click. Yes always know what you are doing, but at the end of the day ship something that works for the customer.

👍👍

👍👍

gold

6:15 That's golden wisdom right there. I can absolutely relate, I'm in that exact situation now. FTE -> Half a decade of contracting + side gigs -> Back to FTE. And my perspective has absolutely widened!

So what’s the point in using MediatR in this example, rather than putting the logic in the controllers?

Do use 404 (if not found) Don't use inappropriate http code. Also consumer context matters. Rule #10 if it is security, you don't really need to put unauthorized.

Based on what is going on so far, this looks more like someone's ideal standards.

Been telling this to all my dev friends for ages)) Business guys want the “Buy” button working as soon as possible and don’t want to listen to your lame ui components, and architectures😅 and how you need more time to fix an unfixable “module not found” error

Big thanks to Event Store for sponsoring Derek Comartin that provides very valuable content on this channel.

Still very relevant! Thanks

great conclusion Derek. I'm just getting more and more passionate about the top level goal of our job which is modeling the business value... And if so called garbage is enough to model the reality, why do we need to fight over some technocratic-religious patterns? They were all invented to solve some particular problems within specific context after all...

As a customer, I’m care about the page, if it load more than my life time or malfunction or privately collecting my personal information without my consent , i’m out so basically the customers who know about tech also are considered as a customer ? Am I right ? They may not care at first, but for the long run they do care and do re-search about your business practice

Well. This garbage you've made, you'll need to support. And Idk about you guys, but I love myself enough to refuse to spend my time and health on developing garbage.