To research
- Microsoft - Whats new in ASP.NET Core 5
- Microsoft - Whats new in ASP.NET Core 6
- Microsoft - Whats new in ASP.NET Core 7
- SVELTE - Latest Frontend framework
- Rust Learning - Finish tutorial
- Caddy server
- Hazelcast - Info
- Web sockets streaming
- gRPC
- Kafka
- Essential Kafka Learning video
- Stream processing design - Only in Scala / Java
- Kafka
- Rx .net
- Using Rx, you can represent multiple asynchronous data streams (that come from diverse sources, e.g., stock quote, tweets, computer events, web service requests, etc.), and subscribe to the event stream using the IObserver
interface. The IObservable interface notifies the subscribed IObserver interface whenever an event occurs. - Because observable sequences are data streams, you can query them using standard LINQ query operators implemented by the Observable extension methods. Thus you can filter, project, aggregate, compose and perform time-based operations on multiple events easily by using these standard LINQ operators. In addition, there are a number of other reactive stream specific operators that allow powerful queries to be written. Cancellation, exceptions, and synchronization are also handled gracefully by using the extension methods provided by Rx.
- Using Rx, you can represent multiple asynchronous data streams (that come from diverse sources, e.g., stock quote, tweets, computer events, web service requests, etc.), and subscribe to the event stream using the IObserver
- akka.net - Currently on this section of Bootcamp - Also ordered book
- Lunch and learn videos
- Microsoft Azure Well-Architected Framework
- ASP.NET Core: Building a GraphQL API
- AWS App Sync
- Web UI testing framework written in TypeScript and is cross platform - PlayWright
- Blazor
- Blazor Server App
- Renders content generated by the server, all processing is done on the server.
- SEO would continue to work as the page is generated a sent on render.
- Conceptually its like the ‘UpdatePanel’ from the old days of webforms where content is generated on the server and sent back to the browser. Interactions with the content are sent to the server and rendered and the changes are returned to the browser.
- There can be a lag from interaction to display. This is evident in the counter sample where 10 rapid clicks on the counter button do not necessarily increase the counter by 10 as not all the button depresses are sent due to lag.
- Blazor Web Assembly
- Renders on the client using WASM.
- Large assets
- Blazor Server App