Madrid DotNet 2019 summary



Thanks to Fenergo, this week I had the chance to attend DotNet 2019 in Madrid and it was a really rewarding experience. For this reason, I would like to post a summary of the day and the key point of the speeches I could attend.

First of all, the event started with a keynote by the Scott Hunter. He talked about the innovations incoming to the dotnet world. Some of the key points mentioned were: the introduction of Blazor, ML.net, c# 8.0, .net core 3.0 recent features like performance improvement and the future .NET 5, which will the only one version for .net to support Windows, Linux, macOS, iOS, Android, tvOS, watchOS and WebAssembly, etc.



Next, I attended the session "SSR with typescript, React and NextJS" by Carlos Bastos Pérez. In this session, Carlos showed how he does an analysis to choose a technology stack. In the case of NextJS, it allow us to build server side render react applications easily, which can be a really suitable solution when we need to support SEO in our SPA or to support browsers which don't support javascript. In addition, this can also provide performance improvement depending on the scenario. Regarding typecript, Carlos mentioned how it can be the key to produce code more maintainable and to reduce the amount of bugs in our code. Carlos also recommended the package typestyle, which allow us to type our css, so we don't end up with mess of classes repeated in our code. Here we have the example of the demo for this session: https://github.com/cbastos/dotnet-2019-ssr-typescript-react-nextjs

In the following session, "Asp.Net Core Good practices", Carlos Landeras and Luis Ruiz Pavón talked about different techniques to improve our dotnet applicaitons, such as code instrumentation, resilience, health checks, performance improvements with HttpContext Pipes, Endpoint routing, etc. In addition, they have shared a repository with examples of all these good practices here: https://github.com/CarlosLanderas/dotnet2019-aspnet-core-best-practices

In next session, "Introduction to Blazor", Ryan Nowak showed the current state of Blazor, the new dotnet framework based on Web Assembly, which will allow us to develop single page applications in C#. During the presentation Ryan showed examples of client and sever rendering with Blazor.



In the next presentation, "Improving Vue with typescript, inversify and vuex", Quique Fdez Guerra talked about the benefits of using technologies like typescript or inversify in our frontend application, in this case Vue. Quique highlighted how, apart from the technology used, typescirpt and inversify can help you to produce maintainable code based on dependency inversion and other patterns and good practices.

Last but not least, Hugo Biarge presented "Authentication in native and web applications", where he talked about different authentication scenarios, like: Local website, Applications using active directory and Applications using a OIDP as a Federation Gateway. The repository with the presented examples is here: https://github.com/hbiarge/authentication-samples

In conclusion, Dotnet 2019 was a really interesting conference, where I had the chance to learn new things and meet awesome people. I'm really looking forward to Dotnet 2020, which will be an event event greater, as Pablo Pérez (the CEO of Plain Concepts) announced.

I'm also preparing some posts related to the technologies presented, as there are some technologies I would like to investigate further. So, if you are interested in web development, stay tuned.

Happy coding!

Comments

Post a Comment

Popular posts from this blog

Building Micro-Frontends with Single-Spa

Image
Introduction Micro-services architecture is becoming trendy since it is a suitable option many projects, specially those that are complex and we want to be able spilt our business logic into different services that can be built and deliver independently. In spite of the fact that micro-services architectures are more complex, they increase the resilience of your system and increase the time-to-market delivery, which can be crucial for many companies. But it is not all about services and backend. With the introduction of single page applications (SPAs), we can build fully-functional user interfaces that can work independently in the browser. And here we should ask ourselves the same questions as for backend applications: Is my SPA becoming a huge monolith? Would I like to deliver functional modules independently? If you using micro-services, is there a relation between my services and your UI? Do we want to have functional teams that can deliver new features (frontend+backend) independe...
Read more

AWS assuming role + MFA with pulumi (and other applications)

Image
Introduction In AWS, managing your IAM in a centralized account is a good practice, so then you can assume a role to access to other accounts without need of duplicating users. You can find more info about this approach in this article . In addition, for security reasons, it is highly recommended to enable MFA (Multi-factor Authentication), so you need a device to generate a temporary code to get access. In the image below it is showed how assume role with MFA works, but you also have an article about MFA in this link . This approach is really useful and most of the configuration can be automated with pulumi (or other providers like terraform or CloudFormation). And once it is configured, you can switch your role and get access to other accounts with a few clicks.  However, when it comes to external software such us pulumi, getting access assuming a role and using MFA might not be too straightforward. In this article we will see how this can be configured and how we can easily refr...
Read more

Managing snapshots for Amazon ElasticSearch with Dotnet Core Lambdas

Image
Introduction It is awesome to have some useful services like ElasticSearch managed by AWS , so you don't have to care about patching, monitoring, etc.  When it comes to backup management for indexes, Amazon ElasticSearch includes automated snapshots. Automated snapshots are only for cluster recovery. You can use them to restore your domain in the event of red cluster status or other data loss. Amazon ES stores automated snapshots in a preconfigured Amazon S3 bucket at no additional charge. In particular, if you are using a higher version than 5.3, Amazon ElasticSearch takes hourly automated snapshots and retains up to 336 of them for 14 days. However, this policy might not be enough if you need to keep your snapshots for a longer 15 days, or you need to take a snapshot to create a new cluster in another region, subnet, etc. If you have different requirements to manage your snapshots, you will have to work with manual snapshots. For this part, AWS does not offer a good managed exper...
Read more