All decks
  • What happens when you cancel an HTTP Request?

    With reactive libraries like RxJS, we got used to easily cancelling requests on the client side… but what really happens on the back-end? Is the request really canceled? Did we really improve the app’s performance and reduce cloud costs? Or did we just trigger some crazy chaos? Let’s dig deeper into how request cancelation works from the front-end to the back-end and how we can leverage reactive frameworks and libraries like Angular, RxJS and NestJS to boost performance and reduce costs from the front-end to the database with some reactive programming. 💻 https://github.com/yjaaidi/ng-experiments/tree/http-request-cancelation

  • What happens when you cancel an HTTP Request? @AngularLyon

  • RxJS Flattening Strategy

  • Boosting time to market by dancing the limbo @AgileTourParis

    Using branches, pull requests & code reviews is currently the most classical approach to work collectively on a product. Let's see the limitations of this approach and experiment some new techniques based on atomic changes, timeboxed TDD & Test && Commit || Revert. Careful! You might lose code.

  • Angular Component Unit-Testing Workshop

  • Boosting time to market by dancing the limbo @AngularUp

    Using branches, pull requests & code reviews is currently the most classical approach to work collectively on a product. Let's see the limitations of this approach and experiment some new techniques based on atomic changes, timeboxed TDD & Test && Commit || Revert. Careful! You might lose code.

  • Angular Air - Timeboxed TDD & TCR

  • Angular Testing Workshop