Front-end developers, are you frustrated by complex or course API's that require you to make multiple requests to render a simple view? Are you tired of heavy response objects that contain a multitude of fields when all you needed were a few? Are you constantly referring to the API documentation to determine how to use a particular end point? Server developers, are you tired of creating custom end points or tacking on extra fields to support an seemingly esoteric need in the UI? Are you having a hard time managing changes to your API over time and determining the best versioning strategy of your REST or Ad Hoc end points? Are you struggling to keep your API documentation up-to-date? Does any of this ring true for you? If so, you should consider adopting GraphQL. In this talk, Jay Hogan will introduce you to the core concepts of GraphQL, present the key benefits of GraphQL over REST or ad hoc endpoints and perform a code walkthrough of a simple web-based NodeJS app that leverages GraphQL.
Join Engineers from the CarMax team as they discuss their journey to transform the search capability on carmax.com to Universal React rendered via ASP.NET MVC and Nodejs. We will discuss the business case, demonstrate the technology, and the business impact of this new technology.
In this talk, we'll discuss what WebAssembly is, how it works, and how it can team up with your JS to make your applications much more powerful. By the end of the talk you should feel confident enough to try it yourself and see where it might be applicable to your needs.
During this talk you will create a Web Application that will manage the line for a new ride at a Theme Park. It will handle the queueing of guests waiting in line for the newest ride in your park, and will allow for VIPs to skip to the front of the line when they arrive.
The application will interact with a USB RFID scanner that is exposed via a local WebSocket. A demo WebSocket application will be provided for download as well. You will learn how you can handle a guest tapping their RFID media and how you can observe those actions and respond in React + Redux; allowing the guest to skip to the front of the line for the new ride at your Theme Park.
Angular 4 comes at the development world with a great combination of what we loved about Angular, mixed with some great pieces of React! We’ll talk about the benefits, as well as how we can utilize this platform. With the help of our yeoman generator jHipster, you will be embedded in the open source world with all the resources needed to build the web, mobile and tablet application you’ve been envisioning!
First we will cover the changes from Angular 2 to 4, why we skipped 3, and why React has anything to do with an Angular application. Then we will jump into the ease of creating the application you want with jHipster! You can have not only the Angular within your code, but also Spring Boot and Bootstrap in just a few clicks of your mouse.
Serverless architecture suffers from an unfortunate name. While not actually serverless, the technology still serves a valuable purpose in computing. In this talk you will learn the following:
* Why serverless is an unfortunate name
* How serverless applications work
* Where you would use a serverless application
* How to build them on Amazon Web Services with Node
What if we could describe to our component the data it needs?
Stateless Components in React are a pleasure to test and debug: testing is `does this prop render this markup` and debugging is `what prop is wrong?`. We can create building blocks upon other components to use, creating larger and larger abstractions. And for a static prop tree, one might grok how the data can flow from parent to child, but as the interactions grow and more actions/events are fired that update the global prop/state tree, it becomes difficult to keep those connections and relations in ones head.
Stateful Components or Redux/Flux store management offer ways to handle those connections but in a somewhat awkward fashion when it comes to asynchronous `actions`. We also end up having to find ways to connect those asynchronous actions into our synchronous render. How can we use the idea of a single source of truth between the state of our UI components and the state of our data ( database )?
Enter `RxJS`. Using familiar Array#extras methods like `map`, `filter`, and `reduce`, we can create a single source of truth with clear, direct, explicit updates, dependencies, and code. We can also use `WebSockets` and hook actions on the server into the state of the client to have an in-sync `store`, shared between client and server.
Reactive Programming, with its ideas of streams and Observables, offers an elegant solution to the mess that is asynchronous events.
Serverless Microservices are small (micro) programs run on ephemeral cloud (serverless) hardware. They definitely do have some benefits or there wouldn't be ten zillion blog posts and companies promoting them, but they have some pitfalls too.
* Smaller programs have fewer responsibilities and are easier to reason about in isolation.
* Not having to manage your own hardware is 👌 *chef kissing fingers* 👌
* Coordination becomes tricky, and you sacrifice your ability to control your environment.
Learn how to stitch together many small programs to achieve big results, and how to do it all independently, in parallel, with confidence.
In this talk, we will consider some strategies for learning React and some of React’s core principles. From there, we will discuss how taking a component-based view of our front-end can help us build an application architecture that scales over time. Finally, we’ll examine some important libraries in the React ecosystem and what problems they are working to solve.
Depending on time, this might just talk about ES5 scopes, or I might be able to go into ES6 and TypeScript.