text
stringlengths
0
2.35k
[1053.68 --> 1060.20] Or you can just use senior PHP engineers, which is much higher, like, availability since it's so old language.
[1060.58 --> 1064.04] We're going to do the same thing, which is going to work the same on the same performance.
[1064.26 --> 1067.50] Well, it's just going to be done easy because you can source people easier.
[1068.34 --> 1068.74] Yeah.
[1068.74 --> 1085.92] And at the same time, if you wanted to do some pretty hard work or some low-level stuff, you can easily write a simple plugin and plug it into Roadrunner, compile it, and solve your needs with that.
[1085.92 --> 1089.38] So, we also write our own plugin system.
[1089.60 --> 1094.58] Because, so, initially, we wanted to use, like, Golang native plugin system.
[1094.68 --> 1097.14] You know, it works only on Linux at the moment.
[1097.14 --> 1103.82] So, we waited a little for the Windows support, but I guess it doesn't seem to happen.
[1104.16 --> 1107.16] So, the Windows support for Golang native plugins.
[1107.16 --> 1121.86] But we wrote our own plugin system called Endure, which is suitable for, like, plugging all of the pieces of Golang, combining into one part, like, initializing it, starting to serve it, stopping.
[1122.18 --> 1125.26] So, building a tree with all of those plugins.
[1125.26 --> 1141.84] So, you can, for example, if you write once a configuration parser, for example, if you write, like, a parser from the YAML, for example, you don't need to write or copy or create some SDK to bring this part into every plugin.
[1141.84 --> 1145.00] So, you can just request this init function.
[1145.72 --> 1155.80] And Roadrunner will take care about finding this dependency, initializing it, topologically sorting the graph, and providing this initialized dependency for you.
[1156.04 --> 1162.48] You only need to just, okay, configuration, please give me the gRPC section or give me some other section.
[1162.48 --> 1178.52] So, if something goes wrong, Roadrunner will take care about this, of course, and, like, provide you, like, nice but unreadable for PHP users message about, like, going to some panic or some errors, something like this.
[1178.90 --> 1187.46] And for the PHP, all complexity for the PHP user is to properly define what do you need in the configuration.
[1187.46 --> 1197.50] Like, you have a configuration, you need HTTP, so you just enable HTTP section, put your configuration, and Roadrunner will remove all other plugins from the tree.
[1198.02 --> 1199.86] Like, it won't even start.
[1200.50 --> 1204.02] It just runs your section for your needs, like HTTP.
[1204.56 --> 1205.30] Or gRPC.
[1205.46 --> 1211.46] Or you can write your own plugin, put your section in the configuration, build with our tool called Velux.
[1211.46 --> 1218.30] Velux is a tool which helps you to build Roadrunner with your own custom plugins based on GitHub.
[1219.38 --> 1232.20] So, it's all of this heavy, complex stuff was moved to the GoLang part, and the open, nice things moved to, like, PHP.
[1232.20 --> 1240.82] That's actually quite an exchange of knowledge, because this first container actually came, like, as architectural pattern in most of the PHP applications.
[1241.40 --> 1246.56] Because if you've seen .NET, Java, PHP applications, you have a ton of classes, interfaces that inherit each other.
[1246.94 --> 1249.78] They, like, use class declarations and etc.
[1249.90 --> 1251.98] So, like, you can't work without container.
[1252.20 --> 1254.80] And it being dependencies, you need to manage all of this stuff.
[1254.80 --> 1260.80] So, like, essentially, we use this idea inside of Roadrunner, but obviously, it's the GoLang favor tool.
[1260.92 --> 1263.46] Initiate it, lays it all correctly in the correct order.
[1264.10 --> 1267.30] And answering the question, like, how, like, it's a large tool already.
[1267.70 --> 1273.04] Well, it's kind of not, because it's just a container with a bunch of, like, CLI tools and instruments.
[1273.52 --> 1276.80] And the rest is just kind of, like, independent projects and plugins.
[1277.08 --> 1282.80] So, we can add them without kind of influencing on each other or worrying to break the tool.
[1282.80 --> 1284.76] Do you want Roadrunner with HTTP layer? Sure.
[1284.92 --> 1287.48] If you don't, well, disable the plugin and build it.
[1287.58 --> 1290.98] It's going to be exactly the same thing, just less memory to manage.
[1303.92 --> 1307.74] This episode is brought to you by our friends at FireHydrant.
[1308.04 --> 1310.80] FireHydrant is the reliability platform for every developer.
[1310.80 --> 1315.02] For incidents, they impact everyone, not just SREs.
[1315.26 --> 1322.90] They give teams the tools to maintain service catalogs, respond to incidents, communicate through status pages, and learn with retrospectives.
[1323.26 --> 1328.68] What would normally be manual, error-prone tasks across the entire spectrum of responding to an incident,
[1328.94 --> 1332.18] they can all be automated in every way with FireHydrant.
[1332.18 --> 1337.52] They have incident tooling to manage incidents of any type with any severity with consistency.
[1338.04 --> 1341.18] Declare and mitigate incidents all from inside Slack.
[1341.56 --> 1347.90] Service catalogs allow service owners to improve operational maturity and document all your deploys in your service catalog.
[1348.48 --> 1355.86] Incident analytics allow you to extract meaningful insights about your reliability over any facet of your incident or the people who respond to them.
[1355.86 --> 1360.18] And at the heart of it all, incident runbooks, they let you create custom automation rules,
[1360.40 --> 1365.64] convert manual tasks into automated, reliable, repeatable sequences that run when you want.
[1366.02 --> 1370.02] You can create Slack channels, Jira tickets, Zoom bridges instantly after declaring an incident.
[1370.50 --> 1373.08] Now your processes can be consistent and automatic.
[1373.08 --> 1375.22] The next step is to try it free.
[1375.36 --> 1379.74] Small teams, up to 10 people, can get started for free with all FireHydrant features included.
[1380.06 --> 1381.48] No credit card is required.
[1381.92 --> 1384.10] Get started at FireHydrant.io.
[1384.42 --> 1386.38] Again, FireHydrant.io.
[1403.08 --> 1406.02] Let's dive in a little bit into the weeds, if we will.
[1406.36 --> 1408.66] Are you shipping a binary?
[1409.04 --> 1410.88] Are you interpreting PHP?
[1411.40 --> 1415.92] If I'm a developer, what does my experience look like?
[1416.06 --> 1420.66] So from a PHP perspective, we're trying to do the less invasive work possible.
[1420.86 --> 1424.08] You literally don't need to do anything to make it work from a PHP side.
[1424.44 --> 1425.22] There's no extensions.
[1425.58 --> 1428.20] There's no special CLIs, interpreters, nothing.
[1428.20 --> 1435.84] What we actually do, we do the 20, 30 years old approach, which still drives all of the applications.
[1436.38 --> 1437.62] We manage the worker pool.
[1437.90 --> 1443.38] So what WordRunner does, it actually uses the default PHP interpreter, which is a binary,
[1443.94 --> 1449.08] invokes it with your application, and then keeps it in memory in a pre-warmed state.
[1449.08 --> 1457.48] And when the request payload comes, which can come for HTTP endpoint, task queue, temporal workflow,
[1458.04 --> 1463.14] gRPC, whatever, you name it, you just send this payload to PHP and wait for it to complete.
[1463.46 --> 1468.76] But over the lifetime, the only main difference for the engineer, which is, well, for some engineers,
[1468.86 --> 1474.38] it's quite hard, is to realize that your application leaves longer than just a single request.
[1474.38 --> 1481.24] And you can't just have a global variable counter, which is going to plus plus and expect it's going to be zero on the next request.
[1481.84 --> 1482.80] That's the only difference.
[1482.88 --> 1489.22] But besides that, it's just the same exact PHP, same exact extensions, configurations as you typically use.
[1489.54 --> 1491.56] It's just managed in a bit different flavor.
[1491.90 --> 1495.98] But surprisingly, WordRunner knows nothing about the PHP.
[1496.66 --> 1500.04] So WordRunner is not binded especially to a PHP.
[1500.04 --> 1504.80] It just runs some command you specify in your configuration.
[1505.02 --> 1506.64] So you can do it in Python.
[1507.22 --> 1513.16] You can even run Golang inside the Golang, like Golang inside the Golang workers.
[1513.50 --> 1517.48] So the main purpose for the WordRunner is to manage the process.
[1518.06 --> 1519.52] Who will be in this process?
[1519.80 --> 1522.40] So for the WordRunner, it doesn't care about it.
[1522.54 --> 1524.30] It cares about the protocol.
[1524.74 --> 1526.84] So protocol is language agnostic.
[1526.84 --> 1532.60] So I saw a project, some guy wrote this, implemented this protocol in Python.
[1533.04 --> 1536.02] Anton showed me like some time ago.
[1536.22 --> 1539.08] So it's like Python running inside the WordRunner.
[1539.36 --> 1544.42] So because it's the same, pretty the same model, like the one-threaded model in the Python.
[1544.60 --> 1548.16] So some guy wrote this in and yeah, so it works.
[1548.62 --> 1551.30] This sounds like a process manager, if you will.
[1551.30 --> 1561.74] So if you wanted to, you could have Python, obviously, as you just mentioned, Ruby, obviously, PHP natively, and whatever else other sort of interpreted languages you want.
[1561.88 --> 1567.00] Like even like pre-compiled things, it sounds like you can just have in there and then basically just invoke it.
[1567.26 --> 1571.42] In theory, you can take 20 years old Perl file and run it in the WordRunner.
[1571.42 --> 1574.96] But if you want to do it, obviously, that's a good question.
[1575.34 --> 1580.36] But yes, I mean, I think the only mention, main mention of PHP is actually the title of WordRunner.
[1580.46 --> 1582.02] It's a PHP application management server.