Efficient and performant applications are fantastic; they keep server load, costs and response times low. We can make our web applications more efficient by removing the repetitive bootstrapping process from the request-response cycle.
"How?" I hear you ask!
By using FastCGI we can keep our application alive between requests and vastly improve their performance. The best news is that if you're using a Request-Response framework (such as Symfony) you can probably do this to your application by adding one line to your composer dependencies file.
Let us not get too excited, however! When using PHP in this way we have to be very careful about the design and configuration of our application! This talk will explain how to use FastCGI with our applications safely, providing an overview of the process and highlighting the danger areas that we must be cautious of.
Great topic! Everyone loves a little more efficiency, especially when it's easy to implement. :)
My fave para is definitely the third one ("by using..."). This one is very audience focused and lures the audience in by telling them how easy it will be (probably) to implement FastCGI.
I like the final sentence ("This talk will give..."), but I was a bit confused by the first sentence ("It's not all good news..") because I actually read it as "that's not all" on the first pass. Maybe if you started with the negative instead, then reassure people with the wrap-up...maybe something like, "Unfortunately, it's not all good news, but this talk will give you an overview of the process to safely implement FastCGI, outlining the benefits to each approach, and pointing out the areas of caution you need to be aware of to keep your applications running well."
The first para doesn't pull me in as strongly as the remainder of the abstract. In marketing-speak, you've described a feature (efficiency), but not the benefit (why I care). Is there a way to be a little more audience centric? Playing around with some ideas: "Sometimes I wish I could do less work but have the same results. Do you ever wish that? That's what efficiency is all about: doing less, but getting the same (or better) results." And then maybe a reason why you'd want to make your applications more efficient ("By making our applications more efficient the server load is decreased, and the costs to running the applications goes down." or "the performance is increased, and users of our applications get a more satisfying experience.") I don't think my language for the first para is very good, but hopefully it's enough to show what I mean?
Overall, I think it's really good. I really like the way you let the audience know what you're going to talk about is easy to implement, but that they need to attend your talk to make sure they get it right and don't screw things up by just chucking in a new setting.