Podcasts about nservicebus

SummaryIn this conversation, Vaughn Vernon and Udi Dahan discuss various topics related to software architecture, including service-oriented architecture (SOA), event-driven architecture, and sagas. They emphasize the importance of using the right architectural styles and patterns in the right places, rather than over-applying or misapplying them. They also discuss the role of patterns in software development and the need for a common language to facilitate communication among developers. Additionally, they explore the strengths and weaknesses of event-driven architecture and the misconceptions around API-first design. Finally, they delve into the concept of sagas as a way to handle complex business processes and policies.TakeawaysUse the right architectural styles and patterns in the right placesPatterns are important for facilitating communication among developersEvent-driven architecture should not be over-applied or misappliedAPI-first design should consider the actual business processes and not just CRUD operationsSagas can be a useful technique for handling complex business processes and policiesChapters00:00 Introduction and Background04:21 Understanding Service-Oriented Architecture (SOA)09:36 The Role of Patterns in Software Development18:17 Exploring Event-Driven Architecture35:07 The Concept of SagasUdi Dahan is one of the world's foremost experts on Service-Oriented Architecture and Domain-Driven Design and also the creator of NServiceBus, the most popular service bus for .NET. Hosted on Acast. See acast.com/privacy for more information.

Avalonia XPF This episode of The Modern .NET Show is supported, in part, by Avalonia XPF, a binary-compatible cross-platform fork of WPF, enables WPF apps to run on new platforms with minimal effort and maximum compatibility. NService Bus This episode of The Modern .NET Show is supported, in part, by NServiceBus, the ultimate tool to build robust and reliable systems that can handle failures gracefully, maintain high availability, and scale to meet growing demand. Make sure you click the link in the show notes to learn more about NServiceBus. Show Notes When you talk to the Temporal guys and look at the way that they've done some of their work is they have a... they have stuff that can run for years. So for instance, they'll kick off a workflow for one of their customers, kicks off a workflow when the customer's created, and that workflow is like managed by Temporal for as long as that customer is a customer. So it could be, you know, I don't know, occasionally sending out an email to, you know, "happy birthday" or something, or sending them promotions or whatever. So they see, they see workflows as like lifetime things — John Kattenhorn Welcome to The Modern .NET Show! Formerly known as The .NET Core Podcast, we are the go-to podcast for all .NET developers worldwide and I am your host Jamie "GaProgMan" Taylor. In this episode, John Kattenhorn joined us to talk about Temporal.io and their platform for building durable workflows which can operate for years at a time. John in the CEO of Applicita and wanted to talk about the ways that developers can build applications and workflows which can live in the cloud for a very long time. And the great thing about Temporal is it manages all of those resources for you. So if you imagined me and you trying to do that, we'd end up standing up, I don't know, a running service or something that was constantly polling the data, looking for eligible customers or something. You'd be burning some resources looking at that stuff, and that's not how they do that. So if you've got like a million customers, the Temporal system dehydrates everything that isn't relevant and only hydrates the workflows that have an action to perform — John Kattenhorn So let's sit back, open up a terminal, type in dotnet new podcast and we'll dive into the core of Modern .NET. Supporting the Show If you find this episode useful in any way, please consider supporting the show by either leaving a review (check our review page for ways to do that), sharing the episode with a friend or colleague, buying the host a coffee, or considering becoming a Patron of the show. Full Show Notes The full show notes, including links to some of the things we discussed and a full transcription of this episode, can be found at: https://dotnetcore.show/season-6/temporal-orchestrating-success-in-distributed-systems-with-security-and-simplicity-with-john-kattenhorn-with-john-kattenhorn/ Useful Links temporal.io Polly Durable Tasks from Microsoft Azure Event Hubs [Azure] Service Bus Cadence Godot Hangfire Saga pattern System.Text.Json Namespace GitHub samples eShop Temporal's YouTube channel Temporal's Slack John Kattenhorn on X Supporting the show: Leave a rating or review Buy the show a coffee Become a patron Getting in touch: via the contact page joining the Discord Music created by Mono Memory Music, licensed to RJJ Software for use in The Modern .NET Show Remember to rate and review the show on Apple Podcasts, Podchaser, or wherever you find your podcasts, this will help the show's audience grow. Or you can just share the show with a friend. And don't forget to reach out via our Contact page. We're very interested in your opinion of the show, so please get in touch. You can support the show by making a monthly donation on the show's Patreon page at: https://www.patreon.com/TheDotNetCorePodcast.

NService Bus This episode of The Modern .NET Show is supported, in part, by NServiceBus, the ultimate tool to build robust and reliable systems that can handle failures gracefully, maintain high availability, and scale to meet growing demand. Make sure you click the link in the show notes to learn more about NServiceBus. Show Notes Yeah. So what I was thinking the other day is that what we want is to concentrate on the business logic that we need to implement and spend as small as little time as possible configuring, installing and figuring out the tools and libraries that we are using for this specific task. Like our mission is to produce the business logic and we should try to minimize the time that we spend on the tools and libraries that enable us to build the software. —Giorgi Dalakishvili Welcome to The Modern .NET Show! Formerly known as The .NET Core Podcast, we are the go-to podcast for all .NET developers worldwide and I am your host Jamie "GaProgMan" Taylor. In this episode, I spoke with Giorgi Dalakishvili about Postgresql, DuckDB, and where you might use either of them in your applications. As Giorgi points out, .NET has support for SQL Server baked in, but there's also support for other database technologies too: Yes, there are many database technologies and just like you, for me, SQL Server was the default go to database for quite a long time because it's from Microsoft. All the frameworks and libraries work with SQL Server out of the box, and have usually better support for SQL Server than for other databases. But recently I have been diving into Postgresql, which is a free database and I discovered that it has many interesting features and I think that many .NET developers will be quite excited about these features. The are very useful in some very specific scenarios. And it also has a very good support for .NET. Nowadays there is a .NET driver for Postgres, there is a .NET driver for Entity Framework core. So I would say it's not behind SQL server in terms of .NET support or feature wise. —Giorgi Dalakishvili He also points out that our specialist skill as developers is not to focus on the tools, libraries, and frameworks, but to use what we have in our collective toolboxes to build the business logic that our customers, clients, and users desire of us. And along the way, he drops some knowledge on an essential NuGet package for those of us who are using Entity Framework.. So let's sit back, open up a terminal, type in dotnet new podcast and we'll dive into the core of Modern .NET. Supporting the Show If you find this episode useful in any way, please consider supporting the show by either leaving a review (check our review page for ways to do that), sharing the episode with a friend or colleague, buying the host a coffee, or considering becoming a Patron of the show. Full Show Notes The full show notes, including links to some of the things we discussed and a full transcription of this episode, can be found at: https://dotnetcore.show/season-6/from-net-to-DuckDB-unleashing-the-database-evolution-with-giorgi-dalakishvili/ Useful Links Giorgi's GitHub DuckDB .NET Driver Postgres Array data type Postgres Range data type DuckDB DbUpdateException EntityFramework.Exceptions JsonB data type Vector embeddings Cosine similarity Vector databases: Chroma qdrant pgvector pgvector .NET library OLAP queries parquet files Dapper DuckDB documentation Dapr DuckDB Wasm; run DuckDB in your browser GitHub Codespaces Connecting with Giorgi: on Twitter on LinkedIn on his website Supporting the show: Leave a rating or review Buy the show a coffee Become a patron Getting in touch: via the contact page joining the Discord Music created by Mono Memory Music, licensed to RJJ Software for use in The Modern .NET Show Remember to rate and review the show on  Apple Podcasts, Podchaser, or wherever you find your podcasts, this will help the show's audience grow. Or you can just share the show with a friend. And don't forget to reach out via our Contact page. We're very interested in your opinion of the show, so please get in touch. You can support the show by making a monthly donation on the show's Patreon page at: https://www.patreon.com/TheDotNetCorePodcast.

NService Bus This episode of The Modern .NET Show is supported, in part, by NServiceBus, the ultimate tool to build robust and reliable systems that can handle failures gracefully, maintain high availability, and scale to meet growing demand. Make sure you click the link in the show notes to learn more about NServiceBus. Show Notes Welcome to The Modern .NET Show! Formerly known as The .NET Core Podcast, we are the go-to podcast for all .NET developers worldwide and I am your host Jamie "GaProgMan" Taylor. In this episode, I spoke with Mark J Price, a software developer and educator with over 20 years of experience. We talked about .NET 8, Blazor, server-side rendering, and more. We also explore the compiler changes in .NET 8 and how they can improve performance and efficiency. Mark also discusses his upcoming trilogy of .NET 8 books, which cater to developers of all levels, from beginners to professionals: What I find when I'm learning something new is even if something has some documentation and it might have a kind of introductory tutorial, they are not always kept up to date and they're not always easy to follow because what tends to happen is the experts who build the platform are then told, oh, just write a tutorial for it. Now they're the experts, but they're not experts at education and so they're not always that great at actually explaining how to get started with something. So that's where my books come in, I feel. I'm an expert at education and I'm an expert because I'm actually not a quick learner. I'm not the quickest, I'm not the brightest, but I do notice the things that trip people up. And so when I first learnt GRPC, I had some misconceptions, I struggled with certain areas, but I notice all of that and I can write it down and so I can write a chapter that I think really helps people get started. —Mark J Price With a focus on providing accurate and up-to-date educational resources, Mark's dedication to the community and continuous improvement shines through in this engaging and informative conversation. With a focus on providing accurate and up-to-date educational resources, Mark's dedication to the community and continuous improvement shines through in this engaging and informative conversation. So let's sit back, open up a terminal, type in dotnet new podcast and we'll dive into the core of Modern .NET. Supporting the Show If you find this episode useful in any way, please consider supporting the show by either leaving a review (check our review page for ways to do that), sharing the episode with a friend or colleague, buying the host a coffee, or considering becoming a Patron of the show. Full Show Notes The full show notes, including links to some of the things we discussed and a full transcription of this episode, can be found at: https://dotnetcore.show/season-6/the-net-trilogy-and-learning-net-with-mark-j-price/ Useful Links Mark's previous appearances on the show: Episode 44 - Learning .NET Core with Mark J Price Episode 91 - C# 10 and .NET 6 with Mark J Price Episode 117 - Our Perspectives on the Future of .NET with Mark J Price Mark's .NET Trilogy books: C# 12 and .NET 8 – Modern Cross-Platform Development Fundamentals Apps and Services with .NET 8 Tools and Skills for .NET 8 Pros (there is no link for this, at the time of creating the show notes) Announcing .NET 8 Release Candidate 2 Tools and Skills for .NET 8 Pros GitHub Repo Conversation about PGO Episode 72 - Emulating a Video Game System in .NET with Ryujinx Performance Improvements in .NET 8 target framework moniker (TFM) The LangVersion element Dapper Cosmos DB JetBrains Rider Visual Studio Code Design Patterns: Elements of Reusable Object-Oriented Software Packt Publishing discord server Supporting the show: Leave a rating or review Buy the show a coffee Become a patron Getting in touch: via the contact page joining the Discord Music created by Mono Memory Music, licensed to RJJ Software for use in The Modern .NET Show Remember to rate and review the show on  Apple Podcasts, Podchaser, or wherever you find your podcasts, this will help the show's audience grow. Or you can just share the show with a friend. And don't forget to reach out via our Contact page. We're very interested in your opinion of the show, so please get in touch. You can support the show by making a monthly donation on the show's Patreon page at: https://www.patreon.com/TheDotNetCorePodcast.

In this episode, I had great fun chatting with Laïla Bougriâ about NServiceBus and how it can help with your distributed architecture. From its support for observability (including OTel) and dashboarding, to sagas and pub/sub. Even zombie and ghost messages! (spooky!). And as has been known to happen on this show - we did end up going on a tangent and geeking out about the awesome Jetbrains Rider too!Laïla is a Solutions Architect and Software Engineer at Particular Software. She's also a Microsoft MVP, and frequent speaker talking about topics such as dotnet, messaging, distributed systems, and software engineering in general.For a full list of show notes, or to add comments - please see the website here

In deze aflevering spreken we Dennis van der Stelt. Dennis werkt al ruim zeven jaar als ZZP'er bij Particular Software en bouwt mee aan NServicebus. Je kunt dus wel stellen dat hij enorm veel kennis en ervaring heeft met de tool. Hij duikt samen met ons dieper in alle functionaliteiten van NServicebus, geeft handige en praktische tips om de tool vanaf het begin nog beter voor je te laten werken en deelt welke shifts hij het komende jaar verwacht te zienKortom: een aflevering bomvol kennis en ervaring waar je echt iets van opsteekt.Shownotes:LinkedIn van DennisLinkedIn Cloud RepublicParticular Software

Happy New Year to all here in 2023. It's going to be a great year. It's a great time to be a programmer. A great time to be building with .NET; you are going to do great things this year. You have what it takes. You are smart, you have great tools, and you have a great team. You are a great leader. This episode is going to be all about remembering what happened this past year at the podcast.   Topics of Discussion:  [1:15] Jeffrey talks about the architect forums he's hosting and facilitating in 2023. You can register here. [1:46] Huge announcement in Microsoft Developer news including: - Android apps on Windows 11 - ARM processors getting big investments - Microsoft Dev Box — in preview — dev workstation in the cloud - Power Pages websites - Large SKU app service; up to 256GB RAM available for those who need it - Azure Arc, the new name of Hybrid Azure. And a single-node Azure Stack for remote locations but the programming model of Azure — looking forward to testing it at the right time. - Azure Container Apps tooling got better, and it became ready for prime time. Every team should be looking at this. - .NET 7 released. [4:11] What might the default application stacks and environments look like on the platform in 2023? - Windows 11 - Visual Studio 2022 w/ ReSharper - .NET 7 - Onion Architecture - Blazor for interactive applications - .NET service workers for back-end jobs and queue listeners - Entity Framework with Azure SQL — add on other storage services as per application. - Azure App Service for hosting while prototyping Azure Container Apps. - Application Insights with the Open Telemetry NuGet packages. - Azure Pipelines paired with Octopus Deploy (keep an eye on GitHub Actions as they fill out support for scenarios you need). - NordVPN for developer workstation work-from-home or remote Wi-Fi. [9:11] When it comes to developer workstations, desktop computers are still giving the most bang for the buck with power, and only a few laptops do the job really well. I have not reviewed all computers, and there are a lot out there. I can vouch for Alienware R series desktops. Liquid-cooled, so they are really quiet, even under full load. Dell Precision laptops are amazing for software engineers. I really wanted to love the Lenovo P1, but the fan was just too loud when it was under load. And we all know that cooling is so important in laptops. When a laptop gets too hot, your BIOS will slow down the processor to keep it from burning up. Then you no longer have a fast processor. And video calls use a good deal of processor, surprisingly — or not. For super mobile laptops that you can use for programming, I really do like the Microsoft Surface Laptop. I wanted to like the Surface Studio laptop, but they inverted the cooling and the battery placement, so it's very uncomfortable on my lap and my wrists unfortunately under load. The wrist wrest gets really hot. Normally the battery is under the wrist rest, but Microsoft swapped it on this one, so it's not fun using it as a laptop on your lap or even on a desk while hot and under load. [13:11] Highlighting some past episodes that will be interesting:  - Highlighting some past episodes over the year that might be interesting. - With Microsoft Orleans providing a new implementation of the Actor design pattern, we have a two-part series interview with Aaron Stannard, the creator of Akka.NET, episodes 172 and 173. - On the IoT front, Wilderness Labs has been trucking along creating system-on-a-chip options that run .NET natively and easily. I interviewed founder and CEO Bryan Costanich. - For those educating themselves for a career in software engineering, my interview with Henry Quillin might be useful. He talks about a programming internship and his education journey, his work earning his Eagle Scout, and how he became a working programmer even as he is just starting university. - More on embedded. Kevin Kirkus was with us in episode 186. He runs a testing team at Intel doing automated testing for their Xeon processor line. The design necessary for testing in this specialized environment gives us all plenty to think about. - For team leaders out there, I interviewed Mark Seemann. He wrote a recent book, Code That Fits In Your Head. He talks about the principles that are in the book. I subsequently bought and read the book, and I wish I had this book earlier in my career. Would have saved me a great deal of time. - On distributed systems, Udi Dahan is always a fascinating gentleman to listen to. Check out episode 192. As the founder and CEO of Particular Software, and the creator of NServiceBus, he is one of the world's leading experts on distributed systems, microservices, and messaging architectures. - Time-tested ideas are continually useful. I had the pleasure of interviewing Philippe Kruchten. He worked at Rational Software back when they were at the forefront of the software process in the 1990s. He published a paper outlining a framework for emergent, agile architecture. He didn't call it that. He called it the 4+1 Architecture, but only because it predated the agile manifesto. If you are an architect, and you aren't aware of this approach to architecture, give episode 195 a listen. - For the Blazor developers, I had Steve Sanderson on in episode 202. Steve is the original designer of Blazor, which has become the new default web application on .NET. He shared about the future of Blazor and WebAssembly. - Because there is so much going on in this space, Daniel Roth also joined me to discuss more Blazor Futures. - GitHub Actions is being talked about quite a bit. While loads of people are using it for builds, people are scratching their heads about where it fits in regarding deployments. Damian Brady, on the GitHub team and a former employee of Octopus Deploy, sheds light on this in episode 206. - Scott Hunter joined me in episode 211. He announced his new role at Microsoft running more of Azure development and .NET. He shared quite a bit behind the scenes regarding Microsoft's strategy there. - For the UX people. Mark Miller is the Chief Architect of DevExpress, the big UI components company. He has a brilliant user experience mind, and I was able to get him talking in episode 212. - Telemetry. We all need it to keep our software stable in production. The Serilog and AutoFac maintainer, Nicholas Blumhardt, joined me to discuss the fundamentals of modern logging and telemetry. Check out episode 217 for that. - More on the testing front, Eduardo Maltez, a software engineer doing some really interesting full system test work shares his thoughts on what makes tests reliable, stable, and fast — and how to fight brittle tests. Episode 224. - We closed out the year on the security front. With LastPass getting hacked and now Rackspace having a hacking-induced major outage, we all need to take action. Troy Vinson, a multi-certified security professional and certified ethical hacker, gave his perspective on the Rackspace breach and what every .NET team should learn from it.   Mentioned in this Episode: Architect Tips — New video podcast! Azure DevOps Clear Measure (Sponsor) .NET DevOps for Azure: A Developer's Guide to DevOps Architecture the Right Way, by Jeffrey Palermo — Available on Amazon! Jeffrey Palermo's YouTube Jeffrey Palermo's Twitter — Follow to stay informed about future events! Programming with Palermo programming@palermo.network   Want to Learn More? Visit AzureDevOps.Show for show notes and additional episodes.

Udi Dahan is one of the world's foremost experts on Service-Oriented Architecture and Domain-Driven Design and is also the creator of NServiceBus; the most popular service bus for .NET. Udi joined us back on Episode 32 to discuss Microservices.   Topics of Discussion: [2:47] Udi talks about some of the changes, and similarities, in distributed computing in the last five years as well as generational differences to approach learning. [11:27] Udi defines what a service mesh is and when it's applicable. [14:46] Udi discusses his concerns regarding using a service mesh and common problems encountered. [22:28] With most of the new generation of programmers using Web service-based programming, what does Udi think they need to hear? [27:50] Why Udi thinks the larger companies and vendors need to take more responsibility and “do more good.” [32:48] Udi shares more on NServiceBus's offerings and functionality and why developers need to learn more. [36:36] Are there any pieces of NServiceBus that will need more than just a .NET standard support?   Mentioned in this Episode: Architect Tips — New video podcast! Azure DevOps Clear Measure (Sponsor) .NET DevOps for Azure: A Developer's Guide to DevOps Architecture the Right Way, by Jeffrey Palermo — Available on Amazon! Jeffrey Palermo's YouTube Jeffrey Palermo's Twitter — Follow to stay informed about future events! Particular Software — NServiceBus Episode 32 — Microservices   Want to Learn More? Visit AzureDevOps.Show for show notes and additional episodes.   Quotes: “Every generation of programmers needs to relearn kind of the same points over again.” — Udi [3:51] “We're still essentially coming up with new generations of technologies that are addressing the same category of problems.” — Udi [6:16] “The problem is not rooted in what do they need to hear so much as who do they need to hear it from.”— Udi [23:51] “If you know a thing, if you can help, then you should.” — Udi [29:47] “NServiceBus essentially takes all of the problems that you never want to have, and the challenges that most people don't know that they're going to have so they don't appreciate it until they have it, and essentially prevents them from happening.”— Udi [34:29] “That ounce of prevention is equivalent to a pound of cure.” — Udi [34:46]   Udi: Website | Twitter

In deze aflevering praten Florian en Dibran met gast Daan de Schepper over Event-driven Microservices. Dibran en Daan zijn bij een klant bezig met het ontwikkelen van Event-driven Microservice landschap en praten in deze aflevering over de ervaringen, best practices en pitfalls. Dibran en Daan vertellen verder hoe ze met hun team van een design tot een werkend Event-driven Microservices landschap zijn gekomen met behulp van NServiceBus.Veel luisterplezier!

Joining Jeffrey today is return guest, Mark Fussell! Mark works on the Azure Incubations Team and is the Product Manager for Dapr, the Distributed Application Runtime. He has been working at Microsoft for over 19 years and has been a passionate advocate for building microservice-based applications for the last 10 years. He has a proven track record of building innovative computing platforms, running large-scale cloud services, and starting new million-dollar businesses within corporations.   Last time Mark was on the show, he and Jeffrey discussed Dapr and what it can do for developers. In this episode, Mark and Jeffrey discuss the new 1.0 release of Dapr. Mark shares how to build, test, deploy, and monitor an application that’s built and deployed using Dapr. He speaks about the team’s journey for the last six months with working on the 1.0 release, the new and exciting changes with the 1.0 release, and all that Dapr is currently capable of.   Topics of Discussion: [:38] Be sure to visit AzureDevOps.Show for past episodes and show notes. [:50] About The Azure DevOps Podcast, Clear Measure, and Jeffrey’s offer to speak at virtual user groups. [1:16] About Jeffrey’s newest podcast, Architect Tips! [1:20] About today’s episode with return guest, Mark Fussell. [1:42] Jeffrey welcomes Mark Fussell back to The Azure DevOps Podcast. [2:03] Mark gives a rundown of what’s new at Microsoft, how he ended up on the Azure Incubations Team at Microsoft, and what the team works on. [3:15] An overview of Dapr. [5:08] The huge news for Dapr: the new 1.0 release. [5:41] Mark elaborates on the journey for the last six months with Dapr and what’s new and exciting with the 1.0 release. [7:07] Is Dapr aimed squarely at processes such as backend services with no UI (that either need to be triggered by something or to pop up and do something)? [9:19] Is Dapr only for Javascript apps? Is it for .NET developers? How is it positioned? [11:55] The strategy of Azure and the positioning of Dapr. [13:25] What are some of Dapr’s main goals? Can Dapr be as simple as a single backend process to a whole bunch of backend processes?  [21:53] A word from Azure DevOps Podcast’s sponsor: Clear Measure. [22:24] Is there overlap with Dapr and open-source distributed application frameworks for .NET such as MassTransit and NServiceBus? Did the Azure Incubations Team discuss these when developing Dapr? [24:19] Jeffrey and Mark dive into the operational side of Dapr. Mark speaks about how to build, test, deploy, and monitor an application that’s built and deployed using Dapr.  [28:24] Does Dapr integrate with Application Insights on its own set of custom events and custom metrics? [29:28] What does deploying with ASP.NET look like? Is it possible, with Dapr, that you would not need to deploy a second process (whether it be Windows Service, Azure Function, or Containers) and you can simply bundle it in with a regular app service web application deployment? [33:51] Mark provides an update on the status of Kubernetes in Azure. [37:04] Discussing the future of running and deploying to Azure.   Mentioned in this Episode: Architect Tips — New video podcast! Azure DevOps Clear Measure (Sponsor) .NET DevOps for Azure: A Developer's Guide to DevOps Architecture the Right Way, by Jeffrey Palermo — Available on Amazon! bit.ly/dotnetdevopsebook — Click here to download the .NET DevOps for Azure ebook! Jeffrey Palermo’s Youtube Jeffrey Palermo’s Twitter — Follow to stay informed about future events! The Azure DevOps Podcast’s Twitter: @AzureDevOpsShow Mark Fussell’s LinkedIn Mark Fussell’s Twitter @MFussell Dapr Dapr on GitHubrDapr for .NET Developers, by Robert Vettor, Sander Molenkamp, and Edwin van Wijk Azure DevOps Podcast Ep. 66: “Mark Fussell on the Distributed Application Runtime or Dapr” KEDA Azure Queue Storage Azure Service Bus MassTransit NService Bus Azure DevOps Podcast Ep. 128: “Simon Timms on Microservices Architecture” Azure Application Insights OpenTelemetry Collector ASP.NET Kubernetes Azure DevOps Podcast Ep. 110: “Stefan Schackow on What’s New in Azure App Service” “Microsoft’s Dapr Introduces Cloud Native Development to the Enterprise” | The New Stack “Microsoft's most useful open-source project for Kubernetes, Dapr hits the 1.0 primetime” | The Register “Distributed Application Runtime (Dapr) v1.0 Announced” | InfoQ “Microsoft’s Dapr open-source project to help developers build cloud-native apps hits 1.0” | TechCrunch “Microsoft’s open source Dapr hits prime time to help developers embrace microservices” | VentureBeat   Want to Learn More? Visit AzureDevOps.Show for show notes and additional episodes.

This week, Jeffrey is joined by return guest, Simon Timms, to discuss microservices architecture.   Simon Timms is a long-time freelance Software Engineer, multi-time Microsoft MVP co-host of ASP.NET Monsters on Channel 9, and also runs the Function Junction Youtube channel. He considers himself a generalist with a history of working in a diverse range of industries. He’s personally interested in A.I., DevOps, and microservices; and is skilled in Software as a Service (SaaS), .NET Framework, Continuous Integration, C#, and JavaScript. He’s also written two books with Packt Publishing: Social Data Visualization with HTML5 and JavaScript and Mastering JavaScript Design Patterns.   Two years ago when Simon was last on The Azure DevOps Podcast, he and Jeffrey discussed Azure Functions and Processes. In their conversation today, they’re focusing on all things microservice-related. Simon has done a lot of work in the space of microservices and has a lot of insight on best practices; when (and when not) to use it; how you run it in production; how to build, test, configure, and deploy; what a visual structure solution looks like for a microservice; how to make a decision if you’re looking at a software system; and much more. If you’ve been wanting to learn more about microservices architecture, this is a not-to-miss episode!   Topics of Discussion: [:38] Be sure to visit AzureDevOps.Show for past episodes and show notes. [1:00] About The Azure DevOps Podcast, Clear Measure, and Jeffrey’s offer to speak at virtual user groups. [1:45] Clear Measure is hiring! Be sure to check out the link in the show notes. [1:55] About Jeffrey’s newest podcast, Architect Tips! [2:19] About today’s episode with Simon Timms. [2:51] Jeffrey welcomes Simon to The Azure DevOps Podcast. [3:38] About today’s discussion with Simon on microservices. [4:54] Microservices: what it is and how it is different from simply splitting up a system into multiple applications. [7:43] Does a microservice architecture have its own version control repository? [8:45] Does Simon tend to have a microservice in its own version control repository, or, does he tend to have many microservices in the same version control repository? [9:38] What are shared dependencies? What does that mean in the context of microservice architecture? [12:26] Key tenets to keep in mind if you’re going to use microservices. [15:09] How to identify if utilizing microservices is the right (or wrong) architecture pattern for what it is that you’re doing. [19:53] A word from Azure DevOps Podcast’s sponsor: Clear Measure. [20:26] What is and isn’t considered a microservice? [25:02] What would cause you to choose one protocol/type of web service/messaging queue over another? [27:40] If Simon was to start a project today, would he say that there is a go-to way to do asynchronous queue-based messaging? [31:35] For someone new to the space of microservices, would Simon recommend NServiceBus as a good start? [33:57] With each different version, do control repositories have their own DevOps pipeline? [34:55] Is there a product or a method that works great when you have half a dozen independent programs running? [38:18] Simon’s recommendations on further resources to check out to learn more. [40:12] Jeffrey thanks Simon for joining the podcast once again!   Mentioned in this Episode: Architect Tips — New video podcast! Azure DevOps Clear Measure (Sponsor) .NET DevOps for Azure: A Developer's Guide to DevOps Architecture the Right Way, by Jeffrey Palermo — Available on Amazon! bit.ly/dotnetdevopsebook — Click here to download the .NET DevOps for Azure ebook! Jeffrey Palermo’s Youtube Jeffrey Palermo’s Twitter — Follow to stay informed about future events! The Azure DevOps Podcast’s Twitter: @AzureDevOpsShow Simon Timms (Blog) Social Data Visualization with HTML5 and JavaScript, by Simon Timms Mastering JavaScript Design Patterns, by Simons Timms Function Junction Youtube Channel ASP.NET Monsters The Azure DevOps Podcast Ep. 23: “Simon Timms on Azure Functions and Processes” NServiceBus Azure Application Insights   Want to Learn More? Visit AzureDevOps.Show for show notes and additional episodes.

Joining Jeffrey Palermo today is Mike Sigsworth, a Principal Software Architect at Clear Measure.   Mike has been developing for over 20 years (most of that in the .NET space) and an unquenchable curiosity to learn keeps him close to the cutting edge of technology. He is also incredibly passionate about board games and is an avid listener of sci-fi audiobooks!   In today’s podcast, Jeffrey and Mike are talking about a huge project that Mike is working on for a client that has made some big shifts for a massively critical system. They discuss this project, how they handled migration to .NET Core, tackled containerization, broke up services into microservices, how the DevOps pipeline was pieced together, and the overall structure of the team. Mike also gives his thoughts and sheds some light on Docker, Helm, Kubernetes, NServiceBus, and more.   Topics of Discussion: [:38] Be sure to visit AzureDevOps.Show for past episodes and show notes. [:46] About The Azure DevOps Podcast and Jeffrey’s offer to speak at virtual user groups. [1:55] About today’s episode with Mike Sigsworth. [2:17] Jeffrey welcomes Mike to the podcast. [2:21] Mike gives some sci-fi audiobook recommendations. [3:11] The lessons learned and challenges he (and his team) have overcome with moving from .NET Framework to .NET Core, figuring out when they need to split something out to a separate git repository, etc. [6:13] Mike gives some context, explaining the type of system it is, the shape of the environment, etc. for this client. [7:42] How big is this production environment? [8:22] Mike explains what a ‘pod’ is and how it works. [9:01] Mike shares how their environment is all in AWS. [9:40] Mike speaks about the course of the project and how it has evolved over time and some of the challenges they faced. [12:16] Talking Dapper.[14:19] Mike continues detailing the evolution of the project from moving to .NET Core, getting things running in Containers, and more. [15:28] Mike shares about a recent fun experience he had with Kubernetes and NServiceBus. [17:30] Mike gives his take on NServiceBus and whether or not he thinks it will be sticking around. [20:16] A word from Azure DevOps Podcast’s sponsor: Clear Measure. [20:44] Having fully containerized their environment, in most cases does that provide them with a zero-downtime deployment process? [24:51] With this type of system architecture, how did they piece together their DevOps pipeline? [27:50] Mike speaks about their testing surface area and how they know when something is not destabilized whenever a new Git commit comes through. [30:43] For such a massively busy system, what’s the necessary structure for the team? [32:00] Mike shares some of the indispensable go-to resources he recommends listeners to check out. [32:58] In the future when Cloud providers may have “plug and play” Container or Kubernetes services, would Mike give up some control in order to just say, “Run my stuff”? [34:13] Jeffrey thanks Mike for joining the podcast!   Mentioned in this Episode: Azure DevOps Clear Measure (Sponsor) .NET DevOps for Azure: A Developer's Guide to DevOps Architecture the Right Way, by Jeffrey Palermo — Available on Amazon! bit.ly/dotnetdevopsebook — Click here to download the .NET DevOps for Azure ebook! Jeffrey Palermo’s Youtube Jeffrey Palermo’s Twitter — Follow to stay informed about future events! The Azure DevOps Podcast’s Twitter: @AzureDevOpsShow Mike Sigsworth Hyperion Cantos Dragon Masters Kubernetes NServiceBus Adobe Analytics Google Analytics Snowflake Amazon Web Services (AWS) TeamCity Octopus Deploy AWS CodeBuild GitHub Actions Docker Helm RoundhousE   Want to Learn More? Visit AzureDevOps.Show for show notes and additional episodes.

NServiceBus #enterprise - ospite Mauro Servienti - 18 by Web Radio Activa

This week Udi Dahan is joining The Azure DevOps Podcast! Udi is the founder of NServiceBus, the CEO of Particular Software, and Microsoft’s Regional Director. He is one of the world’s foremost experts on service-oriented architecture and domain-driven design.   He started programming when he was just 8 years old and got his first professional gig at 19 years old. Soon after, he got involved with .NET, then, a number of years later, became an independent consultant. Over the years, he saw that many of his clients were struggling with building their distributed solutions, and so he founded NServiceBus — “the most developer-friendly service bus for .NET.” Soon, that became part of a bigger project; his company, Particular Software.   In this episode, Jeffrey and Udi are discussing microservices and some of the trends, challenges, and problems in the software industry today. Udi gives his advice and recommendations to developers and teams on how to go about making decisions around microservices while giving examples of common mistakes and problems he often sees. He also gives advice on those looking to move forward with an existing legacy system they are trying to modernize as well as those who are looking to build something entirely new.   Topics of Discussion: [:38] Make sure to visit AzureDevOps.Show for past episode and show notes. You can also find the podcast on Twitter @AzureDevOpsShow. [:56] About today’s guest, Udi Dahan. [1:33] Udi explains his journey in the software industry up to present day. [6:36] What are microservices? And in the industry, what are some of the trends, challenges, and problems of today? [18:48] A word from The Azure DevOps Podcast’s sponsor: Clear Measure. [19:14] How big is a microservice? How does Udi recommend going about making decisions around them? What are some problems and mistakes he often sees? [25:18] Udi gives advice to developers and teams on how to move forward with an existing legacy system that they’re looking to modernize (or, if they’re in the midst of building something entirely new)… who do not want to end up with an inflexible, monolithic system! [39:40] Udi’s resources that he recommends listeners take advantage of! [40:44] Udi’s last pieces of advice. [42:00] What Udi recommends listeners follow-up on.   Mentioned in this Episode: Azure DevOps Clear Measure (Sponsor) Udi Dahan (LinkedIn) Udi Dahan’s Blog Twitter @AzureDevOpsShow NServiceBus Particular Software MVP Summit WCFRabbitMQ Azure Service Bus Amazon SQS .NET Rocks! Podcast Domain-Driven Design: Tackling Complexity in the Heart of Software, by Eric Evans Patterns of Enterprise Application Architecture, by Martin Fowler Eventual Consistency Loose Coupling   Want to Learn More? Visit AzureDevOps.Show for show notes and additional episodes.

Jeremy Miller is using Jasper to distribute computing. This episode is sponsored by Smartsheet. Show Notes: Nancy (NancyFx) was mentioned FubuMVC was mentioned too. TIBCO webMethods RabbitMQ as a "store and forward" queue (video) Azure Service Bus NServiceBus (from Particular Software) More on the Happy Meal metaphor from Jimmy Bogard The Oatmeal (comic) Jasper website - Jasper on Gitter Book: Enterprise Integration Patterns For more on Akka, check out episode 062 with Ted Neward Jeremy Miller is on Twitter. Want to be on the next episode? You can! All you need is the willingness to talk about something technical. Music is by Joe Ferg, check out more music on JoeFerg.com!

Summary Adam Ralph talks about the challenges of distributed systems, queues, coupling, and how NServiceBus helps with microservices, SOA and long running processes. Details Who he is, being "a white space bigot"; what he does; working for Particular, evangelist and engineer. What NServiceBus is, infrastructure for distributed systems, queues, retires. History of NServiceBus, commercial and free versions. Main reasons to us NServiceBus - abstracts the message transport, retires, deduplication and the fallacies of network computing, insights into the flow of messages, monitoring on the transport system. Publish/subscribe. Sagas for long running processes, saving state, an example of a saga in action, sagas can run infinitely. Loose coupling, "pit of success"; different kinds of coupling - temporal, location, logical. an example of decoupled ordering service, thin events vs fat events, contract coupling, set an id very early. What scale do you need to be at to use NServiceBus. How to get started with NServiceBus. Monitoring what is happening. NServiceBus on containers. Adam is running a workshop in May at Micro CPH, Copenhagen.

Version 6 of nServiceBus is imminent! Carl and Richard talk to Udi Dahan about his on-going efforts to build a great service bus in a sustainable business way. The conversation starts out talking about sustainable open source businesses and what has worked (and not). Udi then dives into the cool new features of the latest version of nServiceBus, with a strong focus on asynchronicity. Reliability across clouds and on-premise systems is also a key focus of this version of nServiceBus, so you can run your software where you want. Then a deep dive into the architectural models of services buses, including a great conversation on microservices and actor models. Check it out!Support this podcast at — https://redcircle.com/net-rocks/donations

Version 6 of nServiceBus is imminent! Carl and Richard talk to Udi Dahan about his on-going efforts to build a great service bus in a sustainable business way. The conversation starts out talking about sustainable open source businesses and what has worked (and not). Udi then dives into the cool new features of the latest version of nServiceBus, with a strong focus on asynchronicity. Reliability across clouds and on-premise systems is also a key focus of this version of nServiceBus, so you can run your software where you want. Then a deep dive into the architectural models of services buses, including a great conversation on microservices and actor models. Check it out!Support this podcast at — https://redcircle.com/net-rocks/donations

Jake Ginnivan is a Senior Consultant at Readify. He's an open source enthusiast, blogger, speaker, microsoft MVP and a fan of good beer. He is a contributor to a number of open source projects including AutoMapper, Shouldly, NSubstitute, XBehave, DbUp and Funnelweb. The best way to get in touch with Jake is to flick him a tweet. Today I gave him a call to talk about his latest efforts on a project called GitVersion. GitVersion is an Easy Semantic Versioning solution for projects using Git. We started the conversation by taking a quick look at what Semantic Version. Jake is taking the lead on the next release of GitVersion. To give you some background. GitVersion has been on GitHub since August 2013. Since then it's had 22 releases with 54 contributors and it's used by the team NServiceBus and Octopus Deploy. I got to using GitVersion on a project this week and I found it interesting to see how many different ways it can be used for different solutions. GitVersion works on many levels. It can assess your commit messages, tags and branches. It gathers up all that data and creates a useful version number. Depending on your configuration it will then include that version number in your solution. GitVersion is useful for whatever pipeline you've got going on. Whether it be Team City, Visual Studio Team Services, Chef, Puppet, Octopus Deploy. It's going to work because at the end of the day it can be encapsulated into a single simple to use command line tool that can be plugged in whereever you like. GitVersion is a tool that will help your project remain semver compliant. Thinking about what this means and how this sort of standardisation can help your project continue to evolve whilst others depend upon it got me thinking... Spending some time exploring semver has got me thinking about transitive dependencies and how this sort of idea is often at the core of backlog management, grooming and prioritisation. Perhaps semver could be a useful tool early in the scrum cadence. Perhaps the idea of semver could be useful for versioning many things, not just released packages of code.

Check out RailsClips!   02:38 - Derick Bailey Introduction Twitter GitHub Blog Entreprogrammers RabbitMQ: Patterns for Applications by Derick Bailey 03:36 - RabbitMQ request-response Messaging Pattern 05:22 - Synchronous/Asynchronous; Chronological/Non-Chronological 10:33 - Why Do JS Devs Care About RabbitMQ? 12:10 - RabbitMQ and Complexity 14:04 - RabbitMQ’s Model Pub/Sub - Redis Enterprise Integration Patterns: Designing, Building, and Deploying Messaging Solutions by Gregor Hohpe Exchanges, Queues, and Bindings 22:15 - Event Emitters, Organizing Your Code Documentation 31:18 - Service Busses & Monitoring Systems NServiceBus 32:58 - How do you decide you need a messaging system? 36:40 - When Applications Crash… 39:24 - Event Sourcing Kafka 44:05 - Fault Tolerance/Failure Cases “Just let it fail” 50:21 - Putting RabbitMQ in Place Scheduling Long Wait vs Short Wait 58:28 - Formatting Your Messages RabbitMQ: Patterns for Applications by Derick Bailey 01:04:13 - “Saga” (Workflow) 01:05:10 - RabbitMQ For Developers Use code JSJABBER for 20% off the bundle! Picks W3Schools (AJ) 1984 by George Orwell (AJ) The edit button on the MDN page (AJ) [YouTube] W3Schools is just... Better (AJ) The Go Programming Language (AJ) [YouTube] Go Programming: Learn the Go Programming Language in One Video (AJ) hackthe.computer (AJ) Maze Algorithm (AJ) A* Algorithm (AJ) React Rally (Jamison) Web Design: The First 100 Years (Jamison) Evan Czaplicki: Let's be mainstream! User focused design in Elm @ Curry On Prague 2015 (Jamison) Paracord (Chuck) Soto Pocket Torch (Chuck) Exploring ES6: Upgrade to the next version of JavaScript by Dr. Axel Rauschmayer (Derick) Small World (Derick) Star Wars Darth Bane Trilogy (Derick) LEGO Star Wars The Empire Strikes Back Slave I Set #75060 (Derick)

Check out RailsClips!   02:38 - Derick Bailey Introduction Twitter GitHub Blog Entreprogrammers RabbitMQ: Patterns for Applications by Derick Bailey 03:36 - RabbitMQ request-response Messaging Pattern 05:22 - Synchronous/Asynchronous; Chronological/Non-Chronological 10:33 - Why Do JS Devs Care About RabbitMQ? 12:10 - RabbitMQ and Complexity 14:04 - RabbitMQ’s Model Pub/Sub - Redis Enterprise Integration Patterns: Designing, Building, and Deploying Messaging Solutions by Gregor Hohpe Exchanges, Queues, and Bindings 22:15 - Event Emitters, Organizing Your Code Documentation 31:18 - Service Busses & Monitoring Systems NServiceBus 32:58 - How do you decide you need a messaging system? 36:40 - When Applications Crash… 39:24 - Event Sourcing Kafka 44:05 - Fault Tolerance/Failure Cases “Just let it fail” 50:21 - Putting RabbitMQ in Place Scheduling Long Wait vs Short Wait 58:28 - Formatting Your Messages RabbitMQ: Patterns for Applications by Derick Bailey 01:04:13 - “Saga” (Workflow) 01:05:10 - RabbitMQ For Developers Use code JSJABBER for 20% off the bundle! Picks W3Schools (AJ) 1984 by George Orwell (AJ) The edit button on the MDN page (AJ) [YouTube] W3Schools is just... Better (AJ) The Go Programming Language (AJ) [YouTube] Go Programming: Learn the Go Programming Language in One Video (AJ) hackthe.computer (AJ) Maze Algorithm (AJ) A* Algorithm (AJ) React Rally (Jamison) Web Design: The First 100 Years (Jamison) Evan Czaplicki: Let's be mainstream! User focused design in Elm @ Curry On Prague 2015 (Jamison) Paracord (Chuck) Soto Pocket Torch (Chuck) Exploring ES6: Upgrade to the next version of JavaScript by Dr. Axel Rauschmayer (Derick) Small World (Derick) Star Wars Darth Bane Trilogy (Derick) LEGO Star Wars The Empire Strikes Back Slave I Set #75060 (Derick)

Check out RailsClips!   02:38 - Derick Bailey Introduction Twitter GitHub Blog Entreprogrammers RabbitMQ: Patterns for Applications by Derick Bailey 03:36 - RabbitMQ request-response Messaging Pattern 05:22 - Synchronous/Asynchronous; Chronological/Non-Chronological 10:33 - Why Do JS Devs Care About RabbitMQ? 12:10 - RabbitMQ and Complexity 14:04 - RabbitMQ’s Model Pub/Sub - Redis Enterprise Integration Patterns: Designing, Building, and Deploying Messaging Solutions by Gregor Hohpe Exchanges, Queues, and Bindings 22:15 - Event Emitters, Organizing Your Code Documentation 31:18 - Service Busses & Monitoring Systems NServiceBus 32:58 - How do you decide you need a messaging system? 36:40 - When Applications Crash… 39:24 - Event Sourcing Kafka 44:05 - Fault Tolerance/Failure Cases “Just let it fail” 50:21 - Putting RabbitMQ in Place Scheduling Long Wait vs Short Wait 58:28 - Formatting Your Messages RabbitMQ: Patterns for Applications by Derick Bailey 01:04:13 - “Saga” (Workflow) 01:05:10 - RabbitMQ For Developers Use code JSJABBER for 20% off the bundle! Picks W3Schools (AJ) 1984 by George Orwell (AJ) The edit button on the MDN page (AJ) [YouTube] W3Schools is just... Better (AJ) The Go Programming Language (AJ) [YouTube] Go Programming: Learn the Go Programming Language in One Video (AJ) hackthe.computer (AJ) Maze Algorithm (AJ) A* Algorithm (AJ) React Rally (Jamison) Web Design: The First 100 Years (Jamison) Evan Czaplicki: Let's be mainstream! User focused design in Elm @ Curry On Prague 2015 (Jamison) Paracord (Chuck) Soto Pocket Torch (Chuck) Exploring ES6: Upgrade to the next version of JavaScript by Dr. Axel Rauschmayer (Derick) Small World (Derick) Star Wars Darth Bane Trilogy (Derick) LEGO Star Wars The Empire Strikes Back Slave I Set #75060 (Derick)

Il concetto di Enterprise Service Bus non è cosa semplice da comprendere, e per questo con il nostro ospite Mauro Servienti cercheremo di acquisire alcune delle nozioni di base su questo argomento.Inoltre, vista la grande esperienza di Mauro su NServiceBus, cercheremo di capire insieme alcune delle features che questo ci offre e come adottarlo nei nuovi progetti.

Post po polsku poniżej / Polish version below 14th episode of DevTalk is a special one. First of all: this is the first episode in english! Second: my guest is a well-known, widely respected expert, the one and only Udi Dahan! Udi is a creator of NServiceBus and founder of Particular Software. His thoughs about […] The post 14 – CQRS with Udi Dahan appeared first on DevTalk.

Carl and Richard talk to Udi Dahan about the state of NServiceBus. NServiceBus is Udi's on-going development effort to make the development and maintenance of complex, distributed systems easier. The conversation digs into how developers fall into the N+1 trap of adding more and more interactions between different applications until the system becomes unmanageable - or force the interaction to take place at the very back end of the system, like the database, leading to slow interactions and complexity in the database that shouldn't be there. Whether you use NServiceBus or not, Udi's thinking on bus-based application design will open your eyes!Support this podcast at — https://redcircle.com/net-rocks/donations

Carl and Richard talk to Udi Dahan about the state of NServiceBus. NServiceBus is Udi's on-going development effort to make the development and maintenance of complex, distributed systems easier. The conversation digs into how developers fall into the N+1 trap of adding more and more interactions between different applications until the system becomes unmanageable - or force the interaction to take place at the very back end of the system, like the database, leading to slow interactions and complexity in the database that shouldn't be there. Whether you use NServiceBus or not, Udi's thinking on bus-based application design will open your eyes!Support this podcast at — https://redcircle.com/net-rocks/donations

Carl and Richard talk to Mike Hadlow about EasyNetQ, a simple API for .NET developers to communicate with RabbitMQ. The conversation starts out dealing with the fundamentals of queuing, it's advantages (and disadvantages) and how it impacts your architecture. Mike also digs into Microsoft Message Queue (MSMQ) and how it differs from RabbitMQ. From there Mike digs into the role of EasyNetQ and how it relates to products like MassTransit and nServiceBus. Whether you're new to queuing, just digging into MSMQ or keen to go deep on queuing, this show is for you!Support this podcast at — https://redcircle.com/net-rocks/donations

Udi Dahan is an Enterprise Development Expert and also the author of NServiceBus. Udi educates Scott on how a service bus works, and how it fits into a world of brokers, workflows and services.

Carl and Richard talk to Mike Hadlow about EasyNetQ, a simple API for .NET developers to communicate with RabbitMQ. The conversation starts out dealing with the fundamentals of queuing, it's advantages (and disadvantages) and how it impacts your architecture. Mike also digs into Microsoft Message Queue (MSMQ) and how it differs from RabbitMQ. From there Mike digs into the role of EasyNetQ and how it relates to products like MassTransit and nServiceBus. Whether you're new to queuing, just digging into MSMQ or keen to go deep on queuing, this show is for you!Support this podcast at — https://redcircle.com/net-rocks/donations