![]() ![]() (Note that all of the client-side code can be debugged in developer tools available in browsers such as Internet Explorer and Chrome.) In the solution’s path, all of the client-side code is in the public/app/src folder, while the server-side code is in the root folder. Solution Architectureįirst, let’s take a look at the overall architecture of this solution, as shown in Figure 1.įigure 1 The Overall Structure of This SolutionĪurelia is a client-side framework so it’s here only to handle client-side requirements, such as rendering HTML based on the view and view-model pairings, as well as routing, data binding and other relevant tasks. It also explains how to set up the requirements to run the sample. The ReadMe file that comes with the accompanying downloadable example explains how you can set up your own DocumentDB and import the data for this solution. What I’ll focus on here are the pieces of the solution that involve accessing, updating and binding the data. I had loads of support from members of the Aurelia core team and especially from Patrick Walters ( /pwkad), who not only helped ensure I was taking advantage of Aurelia features, but also indirectly forced me to further hone my Git skills. The stumbling blocks were many, and they went far beyond data-related issues. ![]() Then I set about recreating my Ninja example from the September column, this time using Node.js as my go-between from the Aurelia front end to DocumentDB. I inspected it carefully and shared what I learned with you in the second half of my November column. There’s an existing example that uses the DocumentDB Node.js SDK and a different front end. I finally came to the decision to use a different server-side solution: Node.js. I made this choice because there was no challenge in it-and therefore not much fun. One obvious and easy path I chose to skip was to use my existing Web API that wrapped interaction with DocumentDB in place of the Web API I worked with in my first Aurelia article. These failed attempts were documented in my November column ( /magazine/mt620011), the first of this two-part series. This was exacerbated by the fact that nobody had done this combo before-at least not publicly. While my curiosity gave me some advantage (persistence), my limited experience with these two new technologies, and with JavaScript frameworks in general, set me along a number of dead-end attempts to combine them. Still intrigued by both technologies, I thought I’d like to put the two together, using Aurelia as the front end of an application and DocumentDB as the data store. Then, in September, I played with data binding in Aurelia ( /magazine/mt422580). In June, I explored DocumentDB at a high level ( /magazine/mt147238). ![]() The new JavaScript framework, Aurelia, and the NoSQL document database service, Azure DocumentDB, are two different technologies that have captured my interest lately. Volume 30 Number 13 Data Points - Aurelia Meets DocumentDB: A Matchmaker’s Journey, Part 2 ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |