Building a PHP Framework: Part 1 – Why? Seriously, Why?

There are a lot of great PHP frameworks. Why would I want to build another? The answer is simple: building a framework will provide an opportunity to learn about many different subjects.

I’m know there isn’t a need for another framework. This isn’t an attempt to reinvent the wheel. My goal is to learn; a framework is the tool I’ll use to accomplish it.

What I Want to Learn

• Application Architecture
• Design Patterns
• Routing
• Cache
• Database Abstraction
• IoC
• Code Organization
• Testing

What This Won’t be

It is not my intention to make a production-ready framework. It would be awesome if there’s interest in using the framework when it’s “finished,” but let’s take it one step at a time. Remember, the goal is to learn; anything else is just gravy.

What’s Next

In the next post I’ll discuss what a framework is and what goes into building one.

Wait! We Need a Name

Rather than referring to this project as “the framework,” I’ve given it a name, one that seems appropriate: Analyze PHP Framework.

Update: Building a PHP Framework: Part 2 – What is a Web Framework?

This post was last updated on August 23, 2018.