When creating a distributed system, photo handling becomes less trivial. At the first signs of scale it can become a real pain point in the application. Why?
Over the past few weeks I’ve been working extensively with all three technologies. Here are some of my notes:
Ephemeral cloud-based functions like AWS Lambda and GCE Functions are gaining traction quickly. If done right, they can be economically beneficial and enable infinite scalability™ without forcing you to wade into swarms of containers. If applied incorrectly, they can result in a much more expensive, over-engineered, and difficult to manage application. It’s important to understand that it isn’t all or nothing. Serverless is in our future, but it isn’t our exclusive future.
Functions as a service (FaaS) are functions configured in a cloud provider with a single entry point which lay dormant until triggered. Planning for FaaS is similar to…
The purpose of this article is to highlight some of the most common and bulletproof deployment strategies (we’ll be using stackahoy.io here).
While this is the most basic type of deployment, it’s also the fastest to deploy and easiest to setup. This is a common setup for shared environments — generally LAMP stack applications on one or more servers. Think WordPress, Drupal, etc.
By now, everyone is well aware of the rate at which deployment frequency has accelerated in the past three years. Releasing more frequently gets new features to market faster than your competition, enables snappier bug fixes, and reduces “user error” headaches.
To get a real idea of what Silicon Valley-level deployment cycles look like, take a look at how often Target, Etsy and Amazon are deploying:
Gone are the days when concatenating and uglifying your source code was sufficient. With es6 and es7 developing more rapidly than browser vendors can keep up with, typescript and flow type checking, and other aberrant requirements your project may have, the desire to use something to magically pipe and bundle in one fell swoop can be quite attractive. This leads us to build tools like webpack, grunt, and gulp. With a surgeon’s hand and an abundance of third-party modules you can carefully construct something that will spit out all of your assets with something like:
Awesome. Right? At…
This article assumes you are using (or interested in using) GitLab and GitLab CI. While the following explains how to deploy Docker containers, it can easily be adjusted to accommodate any type of project. Feel free to post any questions in the comments section below.
When we started Lev two years ago, we faced a decision that companies and organizations of all stripes need to deal with — deployments. There is a seemingly infinite number of setups but, in our view, all options seem to fall short in one way or another. When putting together a wish list for our ideal automated deployment solution, here’s what we came up with: