<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Settled Engine Room - Medium]]></title>
        <description><![CDATA[Settled&#39;s Engineering Blog - Medium]]></description>
        <link>https://medium.com/settled-engineering?source=rss----b374bcedc8d9---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Settled Engine Room - Medium</title>
            <link>https://medium.com/settled-engineering?source=rss----b374bcedc8d9---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 14:25:18 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/settled-engineering" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[My journey to becoming a full stack developer and how company culture helped me]]></title>
            <link>https://medium.com/settled-engineering/my-journey-to-becoming-a-full-stack-developer-and-how-company-culture-helped-me-55efb8bc8fa7?source=rss----b374bcedc8d9---4</link>
            <guid isPermaLink="false">https://medium.com/p/55efb8bc8fa7</guid>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[full-stack]]></category>
            <category><![CDATA[company-culture]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Sandy Chuchuca]]></dc:creator>
            <pubDate>Fri, 07 Sep 2018 15:30:59 GMT</pubDate>
            <atom:updated>2018-09-07T16:59:29.581Z</atom:updated>
            <content:encoded><![CDATA[<p><em>I joined a new team with the dream of becoming a full-stack web developer. 16 months later I can now say </em><strong><em>I am</em></strong><em> a full-stack developer.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gmmu7h7jeQ68ojO7s8fUYg.jpeg" /></figure><h3>💪 Joining an early stage start-up business</h3><p>Joining Settled involved different and exciting new challenges. From getting my head around the startup business stuff to new technical tools and skills to learn. The journey wasn’t easy, but what made the difference was the amazing company culture that made my experience so much better. And I want to say a few more words about it.</p><h3>🚲 Venturing into the tech world</h3><p>Ok, before I continue I have to tell you that I’m not a native speaker, so that made things funnier. My new fluent English and I were ready to work and live in London.</p><h4>🗓 First week</h4><p>My first day started with my favourite song on the speaker and a big welcoming at our new office, I received my Linux computer that I happily set up, then had a welcome lunch with the team. :D</p><p>I also experienced my first stand-up and Scrum planning session (now we use Kanban as you can read in my colleague’s <a href="https://engineroom.settled.co.uk/moving-from-scrum-to-kanban-a-positive-experience-with-a-few-things-to-keep-in-mind-bf82b378e9be">post</a>).</p><p>I remember seeing one of my colleagues showing us a page he was building and asking for feedback. They gave me a great first impression of how they worked together and it gave me mentally, a massive smile.</p><h4>🎮 Second week and first challenge</h4><p>My background before Settled was Java and loads of SQL and a basic understanding of front-end technology.</p><p>I was willing to start any front end task to expose myself as soon as possible to full-stack development. Full stack is something so important for consumer-facing businesses that need to iterate fast, and respond to customer demands quickly — that’s exactly what Settled does!</p><p>Two remarkable events happened. Firstly, I could finally start the real job and secondly, a new colleague joined us with whom I have worked with daily and happily so far.</p><p>In our first planning session, I loved the way the team encouraged me to pick up a task that I thought might help my brand new career development. This is a feature that I really like about our team and I think is important to keep everyone happy.</p><p>Javascript, HTML and CSS for the first time became part of my daily work. :D</p><p>Web development documentation and styling were a small part of the challenge. The Javascript part was a small bit of the adventure. Our designer helped me from the smallest and basic CSS to building the Google Maps feature elements, and even more impressive was for him to be able to see single pixels that had been wrongly placed, where I couldn’t see anything.</p><h4>🏖 Next steps</h4><p>Soon I felt settled at Settled!</p><p>After 2 months at Settled I had a short break and when I came back, the team had organised an away day. We went to a big house where amongst fun, food, drinks, games and dancing, we worked tirelessly together to find new ideas to add or improve Settled. We were grouped into teams and each team had to think about a part of the product to improve and to share the final solution which we had written down.</p><p>I was amazed by this entire collaborative, engaging process and thoroughly enjoyed being part of it.</p><h3>📝 My learnings</h3><p>We have had 4 more of these sessions in the last year. What I’ve learnt from these experiences is that focusing over a short period of time a whole group can bring great new ideas to the product and importantly these activities bring us closer and help us to create a great company culture.</p><h3>🚀 What my full stack career looks like now</h3><p>I joined Settled for three reasons:</p><p>The first one, I believe in the product.</p><p>Second, I like the opportunity that a startup environment represents — it’s challenging and exciting.</p><p>Finally, I wanted to become a full-stack web developer. And a startup presents you with unique opportunities to constantly learn new skills and tools.</p><p>What full-stack developers should look out for:</p><ul><li>Believe in the product</li><li>Appreciate the startup environment and what it can offer for your personal and career development</li></ul><p>So far, I’ve been describing the whole Settled team but I also belong to the tech team.</p><p>From a more technical career perspective as I briefly said earlier in the tech team I have had the opportunity to build my own learning path, being able to decide the tasks and challenges that I wanted to face, as well as going to training courses and conferences.</p><p>On a daily basis, I have to say that our friendly and collaborative approach to work makes for a flexible team that is able to review and change our processes and technology in order to innovate and remain a cutting-edge and innovative technical team. This fluent work ethic makes me feel like I’m always going forward in my career along so far a happy path.</p><h3>👌 …and finally, it’s all about work</h3><p>What Settled has provided so far is a calm, happy and supportive environment which I consider my second home. I can feel supported here, and that helps me to grow as a professional, and most importantly as a person.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=55efb8bc8fa7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/settled-engineering/my-journey-to-becoming-a-full-stack-developer-and-how-company-culture-helped-me-55efb8bc8fa7">My journey to becoming a full stack developer and how company culture helped me</a> was originally published in <a href="https://medium.com/settled-engineering">Settled Engine Room</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The developer of the future]]></title>
            <link>https://medium.com/settled-engineering/the-developer-of-the-future-47384fec4eeb?source=rss----b374bcedc8d9---4</link>
            <guid isPermaLink="false">https://medium.com/p/47384fec4eeb</guid>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[full-stack-developer]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Ranj Abass]]></dc:creator>
            <pubDate>Mon, 23 Jul 2018 14:31:40 GMT</pubDate>
            <atom:updated>2018-07-24T08:48:59.183Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*pCPSS7IG4RP5wdrkXNVZwA.jpeg" /></figure><p>Recently I’ve been thinking about the state of development and the makeup of the modern developer.</p><p>At Settled we are an early stage startup and for that reason, the things that give us a competitive edge is the ability to deliver and change at speed. The increased speed of development and fewer bottlenecks results in shorter feedback loops and greater agility as a product development team.</p><p>One thing that gives us agility is that all our developers are full-stack, which means there are never any bottlenecks in the type of development work we need to deliver. Some weeks we are frontend heavy and some weeks we are backend heavy, which is not a problem for us, as all our engineers are capable of working across the entire stack.</p><p>Now some people may say you need the division of labour to create front-end and back-end specialists. However, I believe this is actually more suited to large enterprises that have matured to a size where they are able to deploy teams of specialists to focus on software optimisation across their various products.</p><p>We are a product and customer-driven business, the most important thing for us is to deliver the features our customers want as fast as possible. We have found that creating a team of full-stack developers has resulted in our developers being more product focused and having a stronger connection to the product.</p><p>The reasons for this are as follows:</p><ul><li>Developers are responsible for delivering features end to end, resulting in UX driven development.</li><li>Developers begin to take greater pride in the work they deliver as it is tangible and visible and as a result take a greater interest in customer feedback and interviews.</li><li>Being a full stack team we heavily rely on frameworks tooling and Paas/SaaS products. What does this mean? It means that our developers are freed of the cognitive load of low-level generic problems, to think more about the domain-specific problems that are important to our customers.</li></ul><p>The level of engagement with the product also results in better relationships with the rest of the product team i.e. Product Managers and UX/Design. Resulting in a highly aligned team that collaborates very tightly with each other. The most important benefit of this increased level in engagement and alignment is overall a happier team.</p><p>With all of the above in mind my predictions for the future are as follows:</p><ul><li>I see the industry moving more towards full-stack product engineers.</li><li>All of the low level and generic problems of software will be solved by SaaS and frameworks that will free engineers to focus on their problem domain.</li><li>JavaScript to continue to mature as a backend programming language as NodeJs becomes the de facto full stack environment.</li><li>PaaS and serverless the predominant infrastructure for running code in the cloud, with the same full stack developers required to code these infrastructures.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=47384fec4eeb" width="1" height="1" alt=""><hr><p><a href="https://medium.com/settled-engineering/the-developer-of-the-future-47384fec4eeb">The developer of the future</a> was originally published in <a href="https://medium.com/settled-engineering">Settled Engine Room</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Top tips for Node.js]]></title>
            <link>https://medium.com/settled-engineering/top-tips-for-node-js-17933479b1d9?source=rss----b374bcedc8d9---4</link>
            <guid isPermaLink="false">https://medium.com/p/17933479b1d9</guid>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[node]]></category>
            <dc:creator><![CDATA[Charlie Furniss]]></dc:creator>
            <pubDate>Fri, 29 Sep 2017 14:33:39 GMT</pubDate>
            <atom:updated>2017-09-29T14:38:38.904Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*rDCm-7LSVjueq5bbY5eU6Q.jpeg" /><figcaption>At Settled we love Node.js</figcaption></figure><p><strong>Top tips for Node.js</strong></p><p>Here at Settled Tech we chose to build our core customer platform, the Settled Hub, with Node.js because its simplicity allows us to respond quickly to customer feedback.</p><p>We’d like to share some best practices for Node.js. As a team, we prize simplicity, clarity and efficiency in our code, above cleverness, newness or ascribing to particular principles. So all of the following aim to make our product more robust and more efficient and to make our lives easier both as individual devs and as a team.</p><ol><li><strong>Ensure that code runs from within its directory</strong></li></ol><p>Trying to run a node app from outside its execution directory will break the file path. To ensure that code within index.js runs in the correct context, we include the following line at the start of index.js:</p><pre>process.chdir(__dirname);</pre><p><strong>2. Use Yarn for package download</strong></p><p>We find that <a href="https://blog.risingstack.com/yarn-vs-npm-node-js-package-managers/?utm_source=nodeweekly&amp;utm_medium=email"><strong>Yarn</strong></a> offers a faster, more dependable way of installing packages because:</p><ul><li>It installs packages in parallel, rather than in series like NPM and bower. This makes installation faster and means a single request failure won’t disrupt an entire install</li><li>It creates cached versions, meaning that previously installed packages are available offline</li><li>It uses a flat dependency structure which avoids the problems associated with duplication and (in Windows) long file paths that arise with nested structures</li></ul><p><strong>3. Include scripts in package.json</strong></p><p>Including scripts, like the following, makes code easier to understand and simpler to execute — by running <strong>npm run [SCRIPT NAME]</strong> in the command line.</p><pre>&quot;scripts&quot;: {<br>  &quot;postinstall&quot;: &quot;bower install &amp;&amp; grunt build&quot;,<br>  &quot;start&quot;: &quot;node app/index.js&quot;,<br>  &quot;test&quot;: &quot;mocha app/tests/*.js app/tests/**/*.js&quot;<br>}</pre><p>For example,</p><ul><li>the <strong>postinstall</strong> command builds assets after npm install. It’s not rocket science, but it just makes everything plain and simple and upfront</li><li>the <strong>start</strong> script allows us to run node app/index.js with all the relevant dependencies from node_modules/.bin, so you don’t have to install NPM modules globally</li><li>the <strong>test</strong> script allows us to run tests without having to dig around finding out which module we’ve used and what are the file paths</li></ul><p>Following the same principle, any custom script enables us to group together important and potentially verbose commands to perform specific functions.</p><p><strong>4. Include a Level attribute for environments</strong></p><p>We use a config file for each of our development, staging and production environments to define variables such as urls and authorisation details for third party services that might differ between each.</p><p>We find it useful to define a level attribute as follows:</p><pre>&quot;env&quot;: {<br>  &quot;level&quot;: 3,<br>  &quot;id&quot;: &quot;development&quot;<br>}</pre><p>This helps to simplify logic that determines configuration and make it more readable, eg:</p><pre>if (config.env.level === 3) {<br>  spdy.createServer({<br>  key: fs.readFileSync(&#39;./keys/server.key&#39;),<br>  cert: fs.readFileSync(&#39;./keys/server.crt&#39;),<br>}, app)<br>  .listen(port, (err) =&gt; { if (err) { throw new Error(err); }<br>    console.log(&#39;Listening on port: &#39;, port);<br>  });<br>}</pre><p><strong>5. Use async/await to resolve/reject Promises</strong></p><p>Until recently we used Promises to handle all our asynchronous code. But since the release of Node 8, we have been using Javascript’s <a href="https://blog.risingstack.com/mastering-async-await-in-nodejs/"><strong>async/await feature</strong></a> to simplify the way we resolve/reject Promises.</p><p>This is primarily related to readability, particularly in cases with nested Promises. So the following example…</p><pre>const getPropertyValuation = () =&gt; {<br>  return getAddress()<br>    .then(address =&gt; {<br>      ...<br>      return getPropertyDetails(address)<br>        .then(propertyDetails =&gt; {<br>          ...<br>          return getValuation(propertyDetails);<br>        })<br>    })<br> }</pre><p>… can be rewritten with <strong>async/await</strong> as:</p><pre>const getPropertyValuation = <strong>async</strong> () =&gt; {<br>  const address = <strong>await</strong> getAddress();<br>  const propertyDetails = <strong>await</strong> getPropertyDetails(address);<br>  <br>  return getValuation(propertyDetails);<br>}</pre><p><strong>6. Use an NPM module to make API calls</strong></p><p>We prefer to use modules like <a href="https://www.npmjs.com/package/node-fetch">node-fetch</a>, <a href="https://www.npmjs.com/package/request">request</a> or <a href="https://www.npmjs.com/package/superagent">superagent</a>. All of these enable you to build a request URL by using an easy-to-use object, in which you can include things like query strings and headers, as follows:</p><pre>const options = { <br>  method: &#39;GET&#39;,<br>  uri: &#39;https://sampleapi.com&#39;,<br>  headers: {<br>    &#39;User-Agent&#39;: &#39;Request-Promise&#39;,<br>    &#39;Authorization&#39;: &#39;Basic QWxhZGRpbjpPcGVuU2VzYW1l&#39;<br>  },<br>  qs: {<br>    limit: 10,<br>    skip: 20,<br>    sort: &#39;asc&#39;<br>  }<br>}</pre><p>Modules like node-fetch or <a href="https://github.com/request/request-promise-native">request-promise-native</a> that come with built-in Promise functionality make handling responses clear and simple, with none of the complications that arise from asynchronicity:</p><pre>const request = require(&#39;request-promise-native&#39;);</pre><pre>const getExtractFromWikipedia = (title) =&gt; {<br>  const options = {<br>    method: &#39;GET&#39;,<br>    uri: &#39;https://en.wikipedia.org/w/api.php&#39;,<br>    qs: {<br>      titles: title,<br>      action: &#39;query&#39;,<br>      format: &#39;json&#39;,<br>      prop: &#39;extracts&#39;,<br>      exintro: true<br>    },<br>    json: true<br>  }</pre><pre>  return request(options)<br>    .then((response) =&gt; handleReponse(response))<br>    .catch((err) =&gt; console.log(err))<br>}</pre><pre>getExtractFromWikipedia(&#39;Miles Davis&#39;)<br>  .then((text) =&gt; console.log(text))</pre><p><strong>7. Handle logic for routes in services</strong></p><p>At Settled we don’t subscribe to any particular MVC best-practice — like <a href="https://www.sitepoint.com/10-ruby-on-rails-best-practices/">Fat Models Skinny Controllers</a> or <a href="https://blog.makersacademy.com/forget-fat-models-its-time-for-skinny-controllers-and-skinny-models-a9b84ec481b7">Skinny Models, Skinny Controllers</a>.</p><p>However, in an effort to keep our code readable we do try to limit our routes to handling their inputs and outputs. With this in mind we prefer to handle any more lengthy logic — for processing data or making API calls, for example — in a service that we require in the route.</p><p>Not only does using services in this way keep our code more readable, it means their code is reusable.</p><p><strong>8. Handle user authentication in middleware</strong></p><p>Like most Node.js users, we employ <a href="https://expressjs.com/">Express.js</a> to organise our MVC architecture. Its <a href="http://expressjs.com/en/guide/using-middleware.html"><strong>middleware</strong></a> feature provides a simple way to configure and make checks on an HTTP request on its way to the server.</p><p>As well as using some of the useful NPM modules that help configure a request, we have written our own middleware module that authenticates a user with every request to the server.</p><p>This we require and use in index.js in the usual way:</p><pre>const authentication = require(&#39;./middleware/authentication&#39;);</pre><pre>app.use(authentication);</pre><p>The beauty of this module is that it not only authenticates the user, but also retrieves a base set of user data which is then available on every page.</p><p><strong>9. Build page models from an Environment model</strong></p><p>Javascript’s <a href="https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Classes/extends"><strong>extends</strong></a><strong> </strong>keyword allows you to create a class that is the child of another. This comes in handy when building page models that share commonly used data.</p><p>At Settled we create an Environment model that contains setup information and user data as follows:</p><pre>...</pre><pre>module.exports = class EnvironmentModel {<br>  <br>  constructor (user, cookies) {<br>    // General<br>    this.appVersion = …;<br>    this.environmentLevel = …;<br>    this.environment = …;<br>    this.settledHomePage = …;</pre><pre>    // User data<br>    if (user) {<br>      this.userId = …;<br>      this.userFullName = …;<br>      this.userEmail = …;<br>      this.userPrimaryRole = …;<br>    }<br>  }<br>};</pre><p>Creating a page model as a child of the Environment model with the <strong>extends </strong>keyword means all this data is available in the new model:</p><pre>const EnvironmentModel = require(&#39;./environmentModel.js&#39;);</pre><pre>module.exports = class FeedbackModel extends EnvironmentModel {<br>  constructor (user, cookies, pageName, thread, feedbackId) {<br>    super (user, cookies);<br>    this.pageName = pageName;<br>    this.feedbackId = feedbackId;<br>    this.thread = thread;<br>  }<br>};</pre><p>Note that the <a href="https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/super"><strong>super</strong></a> keyword is used here to call the Environment model’s constructor.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=17933479b1d9" width="1" height="1" alt=""><hr><p><a href="https://medium.com/settled-engineering/top-tips-for-node-js-17933479b1d9">Top tips for Node.js</a> was originally published in <a href="https://medium.com/settled-engineering">Settled Engine Room</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why Settled Uses Microservices, and Why You Should Be Too]]></title>
            <link>https://medium.com/settled-engineering/why-settled-uses-microservices-and-why-you-should-be-too-d65b421c9ae9?source=rss----b374bcedc8d9---4</link>
            <guid isPermaLink="false">https://medium.com/p/d65b421c9ae9</guid>
            <category><![CDATA[docker]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[microservices]]></category>
            <dc:creator><![CDATA[Josh Cole]]></dc:creator>
            <pubDate>Tue, 31 Jan 2017 11:15:28 GMT</pubDate>
            <atom:updated>2017-01-31T11:15:27.538Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PbQ4XWWtkX8XNxGuGdJ-Tw.jpeg" /><figcaption>One of the great strengths of containerisation is complete environment encapsulation.</figcaption></figure><h4>By now, a lot has been written about microservices and we’re starting to discover some excellent usage patterns, and yet there are still developers starting new projects and building new applications using monolithic architectures. It’s time to change.</h4><blockquote><strong>N.B.</strong> Scroll to the bottom for a list of handy resources on microservices.</blockquote><p>Traditionally, applications were built from a single large codebase. This sounds simple in practice but lends itself to a myriad of problems as the application grows more complex. Monoliths like this eventually become unwieldy to maintain and improve, and with multiple points of failure they become brittle.</p><p>I was first initiated in the school of microservices in early 2016 when I joined prop-tech start-up <a href="https://www.settled.co.uk/">Settled</a>, and in particular a tool called <a href="https://www.docker.com/">Docker</a>. Docker is an occasionally convoluted but extremely powerful tool for containerisation and this makes it a great fit for building microservices.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*di3tvuBj-ItHxDDSH4tQ3Q.png" /></figure><p>Like many organisations, Settled has a large PHP monolith that can be a challenge to work with and struggles to meet the evolving needs of the business.</p><p>As a team, our task was to carve out blocks of functionality from this monolith and rebuild it as a constellation of Node.js-based microservices.</p><p>The plan was to increase the pace of innovation in the tech team and reduce the amount of time spent on maintaining the tech stack. Ultimately the project was a huge success, and after a year of using Docker in production we can say that as a team, Settled recommends it wholeheartedly. The Docker team has been making big strides over the last year and whilst there is still a long way to go, it’s finally coming of age.</p><p>The big benefit of containerisation and why it’s a hot topic these days is <em>environment encapsulation</em>. In short, this means that everything inside a Docker container is completely separate from the outside environment, save for a few (very small) entry points that you define.</p><p>Encapsulation gives us a long list of benefits but does require a different way of thinking. Some may argue this is a disadvantage, but in fact it encourages developers to produce higher quality code by design, in the same way that functional programming enforces better code quality.</p><blockquote><a href="http://amzn.to/1WdOuOY">Building Microservices</a> by Sam Newman is an excellent resource if you’re interested in getting your teeth into microservices in more depth.</blockquote><p><a href="http://amzn.to/1WdOuOY">Building Microservices: Amazon.co.uk: Sam Newman: 9781491950357: Books</a></p><h3>Benefits of Microservices</h3><h4>Predictability</h4><p>We define what goes into our containers at build time; from our application’s dependencies all the way down to the specific flavour and version of operating system we want. We know exactly how our application will behave no matter the machine it’s running on.</p><p>No more incompatibilities between developers with different versions of dependencies on their local boxes. No more differences between staging and production environments. No more time wasted fixing inconsequential problems.</p><h4>Portability</h4><p>Applications running in Docker take their entire environment with them. This makes them predictable but also makes them extremely portable because the environment we really care about is the one encapsulated within the container.</p><p>Docker containers can run on various flavours of Linux, Mac and Windows machines and a new server can be spun up and a Docker container quickly deployed without any fuss and zero manual setup.</p><h4>Deployability</h4><p>Using Continuous Integration we can setup a beautiful, automatic deployment workflow that takes all the pain out of pushing to production. At Settled when we merge a feature branch into our <em>master</em> branch, an automated testing environment is spun up on demand (we use <a href="https://www.codeship.com/">Codeship</a>), which runs our tests and builds the final Docker image. Incidentally, Codeship uses Docker itself to create on-demand encapsulated testing environments.</p><p>When all the tests have successfully passed we deploy the new Docker image to our servers using Docker Cloud by flicking a switch, and with our staging environment this redeploy happens automatically.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/698/1*jL7_JsOmut0TLeCx-oyfvA.png" /><figcaption>Containers can be moved and deployed anywhere.</figcaption></figure><h4>Responsibility</h4><p>Each individual microservice should have a Single Point of Responsibility. This decouples it from the greater application and makes it super easy to improve, remove or replace one particular aspect of the application without impacting the rest of it. Good luck doing that with a monolith!</p><p>Having a single responsibility also makes it clear to developers what the service should and should not be doing. Rather than adding tangential functionality to a loosely related area a new microservice should be created. In this way a constellation of microservices evolves and changes as the needs of the business change.</p><h4>Scalability</h4><p>A traditional monolith is easy to scale vertically by adding more resources to the server but not so easy to scale horizontally. Microservices on the other hand are easy to scale both vertically and horizontally because they are decoupled from all other services and each have a single responsibility. We can simply spin up more containers or servers and put a load balancer in front of them — job done.</p><p>This does require that each microservice is completely stateless. It’s not sensible to store data of any kind insider an individual container instance because killing, redeploying or even just restarting it can cause data loss. The environment inside the container is designed to be ephemeral and immutable, but with the flexibility of a temporary local file system.</p><h4>Securability</h4><p>A container runs its own operating system which can be locked down and customised as much as needed. It is completely separate from the host OS and the only entry points to the container are those you define at build time, and typically these cannot be modified once deployed.</p><p>If someone were to gain access to the container they would have a hard time breaking out to the host machine (or vice versa), and if they did they’d soon find they’re running as a user with no privileges. Not to mention they’d only have access to a limited portion of the overall application.</p><h4>Agility</h4><p>Containers typically take less than one second to boot up. That’s the entire operating system <em>and</em> your application. Docker achieves this by sharing the Kernel between the host operating system and the OS inside the container, so unlike a Virtual Machine there’s no waiting around. It just works, instantly.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pXZy9e7gw5YhaVfd5CxxiA.jpeg" /><figcaption>Containers are blazingly fast compared to virtual machines.</figcaption></figure><h3>Excellent Resources</h3><p>These are a few of the resources I found useful when learning about microservices:</p><ul><li><a href="http://martinfowler.com/articles/microservices.html">Microservices</a> (Martin Fowler) (Article)<br>A well written and comprehensive article on the general concepts behind the microservices architecture. This is a great introductory piece.</li><li><a href="http://amzn.to/1WdOkqQ">Building Microservices</a> (Sam Newman) (Book)<br>If you want a more in-depth introduction to microservices then this is the book to read.</li><li><a href="https://www.nginx.com/blog/introduction-to-microservices/">Introduction to Microservices</a> (Chris Richardson) (Blog Series)<br>A detailed series of blog posts comparing microservices to monolithic applications aimed at users of NGINX.</li><li><a href="https://docs.docker.com/engine/getstarted/">Getting Started with Docker</a> (Tutorial)<br>If you’re new to microservices or Docker you can work through this simple tutorial to get up and running quickly.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d65b421c9ae9" width="1" height="1" alt=""><hr><p><a href="https://medium.com/settled-engineering/why-settled-uses-microservices-and-why-you-should-be-too-d65b421c9ae9">Why Settled Uses Microservices, and Why You Should Be Too</a> was originally published in <a href="https://medium.com/settled-engineering">Settled Engine Room</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How We’re Using Progressive Web Apps to Shake Up the Property Market]]></title>
            <link>https://medium.com/settled-engineering/how-were-using-progressive-web-apps-to-shake-up-the-property-market-7affedfd07db?source=rss----b374bcedc8d9---4</link>
            <guid isPermaLink="false">https://medium.com/p/7affedfd07db</guid>
            <category><![CDATA[mobile]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[progressive-web-app]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[proptech]]></category>
            <dc:creator><![CDATA[Dean Hume]]></dc:creator>
            <pubDate>Mon, 23 Jan 2017 17:21:48 GMT</pubDate>
            <atom:updated>2017-02-02T12:11:22.398Z</atom:updated>
            <content:encoded><![CDATA[<h4>Discover the process behind our new smart dashboard built with Progressive Web Apps</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*C2A8tIBDvbR_viGeUzuCLg.jpeg" /></figure><p>At <a href="https://www.settled.co.uk/">Settled</a>, we are passionate about improving the process of buying and selling homes. We want consumers to be able to buy and sell their property online in a completely transparent, straightforward and reassured way.</p><p>More than 50% of our traffic to the <a href="https://www.settled.co.uk/">Settled</a> website comes via mobile devices, which makes it one of our primary platforms for discovery. As you’d imagine, we want this platform to be a fast, engaging experience for our users, so we decided to build a Progressive Web App for our user dashboard. If you’ve not heard of Progressive Web Apps before, they are a set of features that leverage new, open web APIs to offer a mobile web experience that loads fast, uses less data, and re-engages users in multiple ways. Mobile network coverage in the UK is pretty good, but even 4G can be flaky at the best of times. We wanted people to be able to enjoy using the web app whilst offline and see features while on the go</p><p>Once customers have signed up to our site they are directed to a our Hub (or user dashboard). Here, buyers and sellers can easily see the status of their listings, chat with interested buyers and sellers, sign up for legals, mortgages and much more.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/0*Pl8ZDOSBKlv7MBz8." /></figure><p>Our Hub is built as a Progressive Web App, which means that when users visit via their browser they find a fast app-like user experience. When they come back, it loads nearly instantly, even on flaky networks. This allows us to write one code base that works on most devices, reaching more users.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/271/0*x29GGvn9uEC-oHYz." /><figcaption>The Settled Hub has been optimised for mobile devices of any size</figcaption></figure><h3>Under The Hood</h3><p>Under the hood, we leveraged the power of service workers to allow us to cache the results of relevant network requests, meaning that the data can be accessed quickly or even when the user was offline.</p><p>We used Google’s awesome <a href="https://github.com/GoogleChrome/sw-toolbox">Service Worker Toolbox</a>, which provides common caching strategies for dynamic content, such as API calls, third-party resources, and large or infrequently used local resources. This meant that once a user has visited the first page on the dashboard, they had all of their resources cached allowing for lightning fast visits to other pages on the site.</p><p>The great thing about Progressive Web Apps is that they are installable and live on the user’s home screen, without the need for an app store. Using service workers and a <a href="https://developer.mozilla.org/en-US/docs/Web/Manifest">web app manifest file</a>, we were able to provide our users with to access the dashboard at the tap of a button.</p><h3>HTTP/2</h3><p>We wanted to squeeze as much as we could out of our technology and opted to serve requests using HTTP/2. By using <a href="https://http2.github.io/faq/#why-revise-http">HTTP/2’s multiplexing capabilities</a> which deliver even faster web requests via the server when compared to HTTP1.1.</p><p>Progressive Web Apps require web requests to be served over HTTPS, and because this is a requirement for HTTP/2, it made it an easy transition to make. By doing so, we noticed that HTTP/2 gave us a super fast<a href="https://developers.google.com/web/tools/lighthouse/audits/first-meaningful-paint"> time to first meaningful byte</a>, and then once the data had been cached using service workers, our users experienced even faster repeat load times.</p><p>Our server side code is written using Node.js and we used the brilliant spdy package to help us get HTTP/2 up and running. If you’d like to get started with HTTP/2, we recommend checking out the <a href="https://github.com/indutny/node-spdy">spdy Github repo</a> for more information.</p><h3>Performance</h3><p>This all sounds amazing — but what does it mean for the user? So far we have been impressed with the results. Since launch, we’ve noticed that our users spend twice as long engaging with the site. Due to service worker caching, we’ve noticed 3 times less data being downloaded by users, as well as a huge improvement in our page load times.</p><p>Web performance is important to us here in the tech team at Settled. We regularly use the Hub ourselves on our own mobile devices, and understand how frustrating it can be waiting for a web page to load. Since launching the Progressive Web App late 2016, we’ve served hundreds of thousands of web requests and managed to shave off an average of 3 seconds from the page load time.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ONpxbmiQHC713L8f." /></figure><p>In order to audit the performance of our Progressive Web App, we use <a href="https://github.com/GoogleChrome/lighthouse">Lighthouse</a>. It is a great tool for auditing, providing performance metrics, and checking best practices for your Progressive Web Apps.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/779/0*YaEk_PwxMIxNSMjf." /></figure><p>In fact, we are super proud to announce that we get a score of 99 out of 100 when audited using the tool!</p><p>If you’d like to try out the web app for yourself, head over to <a href="https://www.settled.co.uk/">settled.co.uk</a>. We’ll be constantly looking to update and improve the Progressive Web App over the next few months and look forward to sharing the journey!</p><p>Oh and we’re hiring ! Check out <a href="https://www.settled.co.uk/jobs/mid-level-full-stack-developer">our site for more information</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7affedfd07db" width="1" height="1" alt=""><hr><p><a href="https://medium.com/settled-engineering/how-were-using-progressive-web-apps-to-shake-up-the-property-market-7affedfd07db">How We’re Using Progressive Web Apps to Shake Up the Property Market</a> was originally published in <a href="https://medium.com/settled-engineering">Settled Engine Room</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>