Patterns and Practices for Real-World Event-Driven Microservices

Download this episode

Download Video

Description is an e-commerce startup competing with Amazon. We're heavy users of F#, and have based our architecture around Azure-based event-driven functional microservices. Over the last several months, we've schooled ourselves on what works and what doesn't for F# and microservices. This session will walk you through the lessons we have learned on our way to developing our platform.





Available formats for this video:

Actual format may change based on video formats available and browser capability.

    The Discussion

    • User profile image

      This was an interesting session. It gave me some insight into why C# remains the most popular language in the .NET framework.

    • User profile image

      Ehen will this session recording be available?

    • User profile image

      @Shobana: absolutely, in ~12 hours we will have the on-demand video up so you can download it.

    • User profile image

      I'm now more intrigued about F# and it's power to accomplish more with less code than using C#. As a trainer, I wish there was some courseware available so I could teach it.

    • User profile image

      Great info about Microservices. Thanks

    • User profile image

      Very interesting talk about the F# coding style and Microservices practices.

      However the C# examples could been written with less lines (for instance suppressing curly brackets for single statements in "ifs" and "usings") and the "discriminated union" not necessarily "in 4 files" as suggested.

      Plus, having Linq, C# can be very expressive and concise as that F# query.

    • User profile image

      If F# is so great, why are there only templates for console apps and libraries in Visual Studio? Why hasn't Microsoft at least added support for ASP.NET MVC?

    • User profile image

      Microservices looks like a total disaster if you ask me. I'm so sick of hearing about this hype. What will ThoughtWorks come up next that we have to do?

    Comments closed

    Comments have been closed since this content was published more than 30 days ago, but if you'd like to send us feedback you canĀ Contact Us.