Every Developer NEEDS To Know 12-Factor App Principles

When I was a new developer, I didn't know anything about a "12-factor app."

I eventually learned these principles by experience, but if I had just gone over them from the start of my web development career, it would have made EVERYTHING clearer for me.

In this video, I'll go over the 12-factor app methodology and work step by step through them so that you can add them and compare them against the apps you are working with.

*This video was sponsored by PropelAuth

Timestamps
00:00 Intro
00:37 What is a 12-factor app?
01:10 1 Codebase
01:53 2 Dependencies
02:26 3 Config
03:13 4 Backing services
04:00 Sponsor
05:28 5 Build, release, run
06:19 6 Processes
06:43 7 Port binding
07:22 8 Concurrency
08:28 9 Disposability
09:28 10 Dev/Prod parity
10:37 11 Logging
11:38 12 Admin process
12:05 Outro

Video resources

** Career Path Coding Tracks **

** My Coding Blueprints **

** I write regularly **

** FREE EBOOKS **

LET'S CONNECT!

#12factorapp #seniordeveloper #selftaughtdeveloper

** Some of the links in this description may be affiliate links that I may get a little cut of. Thank you.

[lalithmahadev]

12 factor app in 12 minutes.Precise and Concise.Noice!!!

[amirghandehari]

I think what is really good for people like me is a project review.Currently I'm working alone, not in a team. And as a junior full stack developer, I feel I need to get familiar with PRs and what rules apply to an application When written by a team or in a company. I also Feel like github itself doesn't recognized as it should be. I would love to have a review about such things from an experienced developer. Like how much important is CI/CD and github actions or how deep should I become in algorithms and data structures or is it better to learn a new technology. After all I learned lots of things from this channel. Thank you for your content.

[jwill]

I've been doing web development since the late 90s and this is the first time I've heard of 12-factor. It has some overlap with other "manifestos" I've run into over the years. I think it's important to think of this as a gold standard - if you can implement 6 of these then great! If you can only do 2 then great! The most important thing is to keep improving. Great video!

[danielpetcov]

Very nice explanation. I read about it today and you helped me to organize my knowledge.

[colbr]

In my experience, these are good principles but also depend on the organisational structure involved. Especially in large projects where your deliverable has to meet a specified requirement. Using these principles to check what is appropriate within your team is a good starting point. Often this can bring about a review of what is needed, as needs change and managing costs should also be a factor.

[laser]

We followed many of these principles, but did not refer to them by name. A couple of these are interesting: 1) stateless - most of my time was spent building stateful apps with session data stored in memory. I usually saw stateless as an architectural choice rather than a best practice. 2) Dev/Prod disparity: We try to keep as many things similar as possible, but licenses and costs don't permit that for some things (e.g. monitoring tools). I wonder if there is empirical evidence of "it costs more", and if so what is the data?

[cs]

amazing explanation, it'd be great if you could make a video of an app that uses all these principles in AWS with CICD, Containerization

[PatrickMwachugu]

Awesome review.. Learning alot from this channel.. You should consider forming a group where we can discuss in depth various software development related topics..

[markeggers]

My only issue is logging. That should be configurable per environment (attached service) much like a database or SMTP provider is.

[aryanrahman]

Really good explanation but didn't quite get the reason behind the last point.

[JJGuardian]

This is kind of like documentation isn't it? People know they should and say they do but they can never identify who wrote some or where it is. My last job was a major Canadian bank. They had 5 different versions of the same app across their Dev, BAT, PAT, Prod and code repository. I didn't dare touch anything until I investigated and synced them up making me look like the slow guy. A month later they rushed changes and the synchronization was ignored.

[hlubradio]

Thanks. During my software engineering courses in college we never heard of these but yet, my apps were well crafted if that's the correct word. Thanks for giving me a reference to rely on.

[Snooze_Addict]

Is it even worth it to learn how to code anymore? Ai will cause even more layoffs. 😢

[HKnSLK]

You've got this auto-micro-skips thing set up that is really annoying. I don't normally notice this on your videos, but it's anti-helpful. Check your settings?