Whether you’re building a desktop app, a website, or even an iOS or Android mobile app, choosing a tech stack can make or break your project. In this post, we will identify a few common tech stacks and talk about how each one works.
When selecting a tech stack, you should look for something that has best-of-breed components, not just a bunch of random technologies thrown together. Technology stacks consist of several key pieces including frontend frameworks, backend APIs, databases, and cloud hosting platforms.
To help you understand these concepts, I’ve outlined 4 popular tech stacks that you can use as a starting point for your next project. Each stack includes recommended choices for frontend frameworks, backend API libraries, database platforms, and cloud hosting providers. These stacks may seem overwhelming, but once you get started with any of them, you’ll see why they work so well together.
I also encourage you to use the table below to compare different tech stacks side by side:
Let’s start with a brief overview of some of the most common technology stacks in today’s market.
A technology stack is a list of all technologies required to build and run a single web application. For example, a typical Facebook app might include code written in Javascript, HTML5, CSS3, PHP, MySQL, and Apache HTTP Server.
This is Facebook’s “tech stack.” Developers talk about tech stacks to make it easier to communicate lots of information that describes how an application is built—for example, what programming languages are involved, what database systems are used, whether it uses RESTful APIs, etc.
Because most programming languages have well-known strengths and limitations, the tech-stack summary indicates the overall application’s strengths (and weaknesses).
Before the days of ubiquitous S…
What Is A Tech Stack? | P2 – Episode 2 | The DevOps Show
In this episode, we discuss what a tech stack is and how it relates to our jobs as developers. We talk about how we’ve changed the way we work and make sure to give some tips on how to approach working with a tech stack already in place.