.net
Showing 6 out of 6 results
Expert talk: What’s Next for .Net?
.NET has been undergoing a massive development since its very beginning. Martin Thwaites, developer advocate for Honeycomb, and Hannes Lowette, head of learning and development at Axxes, enjoyed every step of its path. Join them as they reveal important milestones in .NET’s evolution as well as gain practical insights into web performance, running .NET at scale, and how to implement observability.
Holiday Special 2022
At GOTO we are all about learning so to wrap up 2022 we asked a few of our speakers and authors about the most exciting technology they learned this year. In addition to that, they shared what they think will disrupt the software world in the next five years. Their answers range from Dapper and Quarkus to Data Mesh’s revolutionary principles to deep focus. Tune in and learn more!
High-Performance Graphql With Asp.Net Core 3
In this talk Nate will share the tools and techniques used at Cobbler to set up and tune [ASP.NET](https://dotnet.microsoft.com/apps/aspnet) Core as a high-performance GraphQL server. He’ll cover library choices, performance measurement, the DataLoader and Relay patterns, and more. Basic familiarity with GraphQL API design is recommended but not required.
Nullable reference types in C# 8
The biggest feature of C# 8.0 is undoubtedly nullable reference types. Rather than trying to rush through *all* the new features, in this talk I'll *just* talk about this one. What's the point? What's the syntax? What's should you expect? What might be *unexpected*? I'll go into all of this and more! **What will the audience learn from this talk?** * How C# 8 allows developers to express nullability in the type system * The benefits of nullable reference types compared with earlier versions of C# * Tricky areas and "gotchas" **Does it feature code examples and/or live coding?** The talk will be live coding for the whole time, with samples on GitHub **Prerequisite attendee experience level:** [200](https://gotocph.com/2019/pages/experience-level)
Clean Architecture with ASP.NET Core 3.0
The explosive growth of web frameworks and the demands of users have changed the approach to building web applications. Many challenges exist, and getting started can be a daunting prospect. Let's change that now. This talk provides practical guidance and recommendations. We will cover architecture, technologies, tools, and frameworks. We will examine strategies for organizing your projects, folders and files. We will design a system that is simple to build and maintain - all the way from development to production. You leave this talk inspired and prepared to take your enterprise application development to the next level. **What will the audience learn from this talk?** The audience will learn how to build enterprise applications using ASP.NET Core 3 and following the principles of Clean Architecture. This talk provides practical guidance and will cover architecture, technologies, tools, and frameworks. **Does it feature code examples and/or live coding?** The talk features code examples and the attendees will get a link to the code repository on GitHub. **Prerequisite attendee experience level:** Level [100-400](https://gotocph.com/2019/pages/experience-level) There is something for everyone from beginner to expert.
Drinking a River of IoT Data with Akka.NET
**No prior Akka.NET knowledge is required for this talk.** Draw from Hannes's extensive experience in .NET to **learn how you can make scaling smart devices much easier using Akka.NET.** You cannot develop a device any more without it connecting to something. These ‘smart’ devices all have one thing in common: they generate a never-ending stream of data. If you want to process all that data for 100, 1000 or 10000 devices, you can probably get by with a very simple web stack. But as soon as you want to scale to 1000000 or more devices, you are going to need a better strategy. Scaling software is always tricky. We have all been through this. You load balance your web farm only to find out that your database is a bottleneck. Or to find out you need to synchronize caches across your farm, etc. State is always going to be what is getting in your way. Akka.NET and its implementation of the actor model makes scaling a bit easier. Developing stateful, concurrent code becomes a breeze. And on top of that, scaling and resiliency are also more straightforward to do. But there are pitfalls as well. There is no free lunch!
