- #Log stack house construction how to#
- #Log stack house construction full#
- #Log stack house construction code#
When putting together an application in this way, it’s important to organize our code well to allow the distinct parts of the application to be kept separate. Figure 4 illustrates this approach.įigure 4 The architecture of the application with the API and application logic wrapped inside the same Express project. This is what we’ll be doing with Loc8r, giving us one Express project containing a few sub-applications. With this approach, we have only one application to worry about hosting and deploying and one set of source code to manage. An additional benefit of this is that we can have more specific settings for each of the servers and applications which are best suited to the individual needs.Īnother way is to keep things simple and contained and have everything inside a single Express project.
If we’re expecting large amounts of traffic, we might even want our main application and our API on different servers. This is perfectly possible and a good way to go for a large project. The architecture diagrams we’ve been looking at imply that we’ll have separate Express applications for the API and the application logic. Wrapping everything in an Express project Although this isn’t necessarily how you might normally build a site, it gives you a great opportunity for learning all aspects of the MEAN stack. We’ll be building the architectures in the order they’re shown in figure 3, starting with a Node.js and Express application, then moving on to add some Angular before refactoring to an Angular SPA. Building all three of the architectures allows us to explore how each approach works and enables us to look at each of the technologies in turn, building up the application layer by layer. No specific business requirements are pushing us to favor one architecture over another.
#Log stack house construction full#
With these three options in mind, which is the best for Loc8r?įigure 3 Three options for building the Loc8r application, ranging from a server-side Express and Node.js application to a full client-side Angular SPA. A Node.js and Express application with Angular additions for interactivity.We can immediately envisage three possible application architectures, as shown in figure 3: If the aim is to promote the application as an application and drive use that way, then search engine visibility is a lesser concern. If the aim is to bring in organic traffic from search engines, then yes, it needs to be crawlable. Do we need something special from MongoDB, Express, Angular, or Node.js that’ll swing the decision a certain way? Do we want HTML served directly from the server, or is an SPA the better option?įor Loc8r there are no unusual or specific requirements, and whether it should be easily crawlable by search engines depends on the business growth plan. The more interesting and difficult question is: How do we architect the application? Application Architecture OptionsĪt this point, we need to look at the specific requirements of our application and how we can put together the pieces of the MEAN stack to build the best solution. Figure 2 shows the starting point, a REST API built with Express and Node.js to enable interactions with the MongoDB database.įigure 2 Start with the standard MEAN REST API, using MongoDB, Express, and Node.js.īuilding an API to interface with our data is the base point of the architecture.
Starting with the APIīecause the application is going to be using a database and passing data around, we’ll start building the architecture with the piece we’re definitely going to need.
#Log stack house construction how to#
But we still need to think about how to architect it, because we’re going to be transferring data from a database to a browser, letting users interact with the data and allowing data to be sent back to the database. On the face of it Loc8r is a simple application, with only a few screens.
0 kommentar(er)
