In this article series we’ll go through Web Components development in context of microservices. We’ll use Polymer as the library that will help us out. The objective is to create a microservice that will handle full functionality. The service will contain not only back-end API (as is the case with most microservices) but also front-end in form of Web Components. Later on, when the time comes to use the service we’re creating, we’ll simply import Web Components. That is quite a different approach than what you might be used to. We won’t create a Web Application that calls APIs handled by microservices. We’ll import parts of the front-end from microservices. Our objective is to have a microservice that contains everything; from front-end to back-end. Please refer to the Including Front-End Web Components Into Microservices article for more information that lead to this decision.
Tag Archives: Polymer
Developing Front-End Microservices With Polymer Web Components And Test-Driven Development (Part 1/5): The First Component
With a realtime, bidirectional data channel, we have to the power to make our devices interact with one another. As a result, this has opened up the doors for more interactive experiences. Think of the Wii, Playstation Move Motion, and Xbox Kinect. These gaming technologies let users use a motion controller to connect real life movement to gaming motion.
We want to do the same with a smartphone and a computer, more specifically a web browser. In this blog post, we’ll show you how to use PubNub and Polymer to bridge that gap by turning your smartphone into a Material Design gamepad, a motion controller for realtime gaming experiences.
The live demo, called Kitteh Anonymous, can be seen here. Open up two browsers and watch as your messages are sent and received in realtime. In this tutorial, you’ll be writing the lite version of this demo.
Over the previous year, the Polymer team has spent a lot of time teaching developers how to create their own elements. This has lead to a rapidly growing ecosystem, buoyed in large part by Polymer’s Core and Paper elements, and the Brick elements created by the team at Mozilla.
As developers become more familiar with creating their own elements and start to think about building applications, it opens up a number of questions:
How should you structure the UI of your application?
How do you transition through different states?
What are some strategies to improve performance?
And how should you provide an offline experience?