What we're about

The Louisville .NET Meetup group is dedicated to helping developers around Louisville to become better developers with an emphasis on the Microsoft .NET technology stack. We hold meetings on the third Thursday of each month.

The Louisville .NET Meetup group is also host to Code PaLOUsa (codepalousa.com (http://www.codepalousa.com/)), the Louisville Global Azure Bootcamp (louisville.azurebootcamp.net), and the Louisville Global DevOps Bootcamp.

Upcoming events (2)

[ONLINE] An Evening with Scott Hunter

Online event

** VIRTUAL/ONLINE Event ** We will be having a special Louisville .NET Meetup on June 9 with the one and only Scott Hunter – who is responsible for the Microsoft .NET platform, which includes .NET Framework, .NET Core, ASP.NET, Entity Framework, .NET Tools, Web Tools, and the managed languages (C#, F#, and VB). Attend to hear about the great things coming to .NET 5 and beyond. Once Scott is done; we’ll stay online and just chat as long as people would like (just like going to BJ’s after our in-person meeting). -- Scott Hunter -- Scott Hunter is responsible for the Microsoft .NET platform, which includes the .NET Framework, .NET Core, ASP.NET, Entity Framework, .NET Tools, Web Tools and the managed languages (C#, F# and VB). Prior to leading the .NET Platform, Hunter helped the Azure Developer Experience team build the Azure SDK’s, App Service Tooling, Azure Redis Cache, Azure API Management, ASP.NET, Entity Framework and the Web Tooling. In his spare time, he loves hiking mountains in Washington State and around the world.

ACID 2.0: Designing Better APIs and Messages

Online event

** VIRTUAL/ONLINE Event ** ACID 2.0: Designing Better APIs and Messages Databases uphold 4 promises. Transactions are Atomic, Consistent, Isolated, and Durable. That's fine for the small, directly-connected scope of a database, but what about distributed systems? How can we ensure correctness across APIs and message queues? When we cross compute boundaries, we need a different set of promises. We need to know that the system will behave correctly when messages arrive out of order. It needs the ability to retry on delivery failure without causing duplication. And we must be sure that all nodes converge even if they don't all subscribe to the same queues. We need ACID 2.0. A system that is ACID 2.0 is: · Associative · Commutative · Idempotent · Distributed Each of these guarantees is vital for the correct behavior of a system. And better yet, they provide guidance for designing Web APIs and service bus messages. They are precisely defined, so that we can verify with certainty whether the systems we build uphold these promises, or whether we are setting ourselves up for failure. Build better Web applications, mobile apps, and microservices. Make them resilient. Make them ACID 2.0. Once Michael is done; we’ll stay online and just chat as long as people would like (just like going to BJ’s after our in-person meeting). -- Michael Perry -- Michael travels through space clinging to the carbon hull of a spherical ship made of molten iron. He commands an army of microorganisms which decompose the molecules that he captures to provide chemical energy for his cells. His mission is to increase entropy throughout the universe. Michael wrote The Art of Immutable Architecture, a book on applying mathematics to building distributed systems. Learn more at https://immutablearchitecture.com. In his spare time, he records Pluralsight courses on CQRS, XAML Patterns, Cryptography, and Provable Code. Formerly a Microsoft MVP for seven years. He maintains the spoon-bending Assisticant, Correspondence, and Jinaga open-source libraries. He shared videos about distributed systems at historicalmodeling.com. And he helps his clients at Improving benefit from the power of software mathematics. Software is math. Every class is a theorem. The compiler is the proof. And unit tests check our work.

Past events (122)

[ONLINE] Entity Framework Past and Future

Online event

Photos (155)

Find us also at