Everybody forced here ripping 2023 pristine a baseball hobby 4 box number 17 Random teams the results on your screen can be found anytime a late in sports cards.com Let's get to the break. Good luck You want to list that uh? Honstu fahti tomorrow right post on Instagram saying that it's available to Good luck everybody spectrum dude could be watching Clemson Duke right now ready Jackson nester Cortez Yeah, oh That's why we can't watch it It's good game to Duke is okay and Clemson's top 10. So I mean I guess that's like a mini rivalry. I'm just gonna do this kind of a rivalry It's better than this like Phillies piders is great, but like piders are out of it like Garvish got purple rookie Lengoliers. It's a 99 for the eight And just hop over to it every now and then Brett Beaty. Oh snap Or Chris Bryant, sorry Chris Bryant. Oh snap. That's my bad got Byron bucks thin a bat relic auto Starling Marta Or the Mets Can't go to Shipley every play. I mean like they probably can No, they're good on the first drive they're still going right Raza is it is this stream behind you think It's gonna be Okay, yeah, that's fine. I was I was I was more just curious. Yeah, but it's like I support down that's where we're at There attack we got a rutchman rookie bluer fractured a 75 nice one for the Orioles And I should have had a pick there. That was just that was now is definitely the wrong decision right there Swings of summer short print blue jays of Vladimir Guerrero, Jr. Nice card Aaron judge I'll probably just recap color in this too Mark grace Nola Yoshida base Now we're go we have it over on the laptop is just behind a bit nothing crazy Johnny Bench refractor gold Bogarts number 250 That goes red socks. Make sure you tag down. That is a red socks Bogarts rutchman base The fresh faces blue day Nice start on the autos blue jays here blue jays good box George Springer to 75 true Pristine blue auto there ready Jackson refractor a double raise gold Jose Kenseko. That's pretty cool 45 at a 50 a Rookie Auto Gunner Henderson Orioles doing very well Kyle M with the blue refractor of rutchman a minute ago now a Henderson auto Fantastic, we got Pee Wee Reese refractor and a blue refractor rookie for the Braves is a great rookie here Michael Harris 73 of 75 Good first box We can talk about the game though for sure. I don't know anything about Clemson or Duke I know Clemson's ranked in the top ten, so I Know they should expect to be good every single season because for Clemson Davos winnie is annoying as all hell Why is every good cholesterol coach like just super annoying? I Guess it's the yeah, they're all like There's like there's like no nonsense. They take everything so seriously. This is like probably not the person you want to like be at the bar with I Want to go home This isn't fun Find Rodriguez Gregory Soto, which guy? You can ruin it. I don't care dude. I don't care. I just want to look over and see football every now and then I Love baseball, but It's a like a nine-to-one game and like at this point in the season teams like the Padres or just like they're just out of it so it's Not quite as exciting not just crazy Crawford purple jazz Chisholm there we go for the NL or the analyst at the Marlins the 99 my Trout O snap Yeah, or girls are just are just really sick and products is your two amazing rookies probably the two top rookies overall I mean arguably I carols obviously up there. It's like that big three Smith and jigba Jersey auto Tory hunter for the twins But to have two on the same team is kind of insane Orals are gonna be so good and like high-end this year too because you're so gonna have like the Cal ripkins and like the Jim Palmers and you're also now gonna have two phenomenal rookies Salvi Perez they might be more sought after than like I like the Yankees and super high-end Josh Smith rookie blue refractor to 75 Rangers Seven wonders Mike Trout short print angels Very nice four boxer we got going here awesome seven wonders Yeah, my only games are cool That Rivera Part of that's because they're cheap Part of that I love major league baseball games, but sometimes they're not so cheap But you can also go to a minor league game and not like stress about who wins or loses a lot It's a little less Little less at steak, I guess you could say they're gold Randy Johnson to 50 for the Diamondbacks So insane to me that central Florida has no minor league Was Lakeland the closest or I think it's I don't even know if Lakeland's the closest I know they're just spring training there. Yeah, the Tigers Magic They're in a Kissimmee now Lakeland magic would be Kissimmee. That's kind of cool. Actually a blue refractor rookie auto and car now see own number to 75 They're playing in the The the Osceola that whatever arena they really yeah, that's what program. Yeah, they're playing there. Oh, just kind of weird rodeo Yeah, yeah, yeah, it's nice. It's like graduations and rodeos and stuff like that basically That's that's that kind of blows my mind 75 and cannot see on Marlins and Gil Cabrera blue refractor Killian Cubs rookie to 75 Mark a pal rookie auto Phillies Jeter refractor and a Corey Lee to 15 pink refractor rookie for the Astros nice In more Savannah bananas in the world. It's so funny going on like social media and seeing people like Just don't why would anybody want to have baseball? It's like we don't want you with the Savannah banners gaming Only go to Savannah banners game if you like fun They're literally not trying to be the MLB there's space in the world for both of those things For a super competitive baseball and for things you just want to take your kids or go to with your boys and have a few beers and just Watch something different for once. I feel like if you took like really little kids to something like that They would be super like into it They go, oh man that guy's that guy's juggling bowling pins that are on fire That's so much better Trara's Josh Chisholm Shwerver 440 feet. He did. There's no short home runs with that guy, dude. Could I sanga fresh faces? New Hampshire Fisher cats Bernie purple Paul gulch mitts of 99 for the Cardinals Allie Rochman. Oh snap Brett Beatty Ricky refractor for the Mets Jersey auto Bo Jackson cool hit Kansas City Bo Jackson, that's nice Rochman fresh faces CJ Crone blue refractor to 75 Larry Walker for the Cardinals Larry Walker really? Then we played for the Cardinals So I so I haven't ripped a ton of top scromes WWE before they switched licenses But I remember one time I worked a personal for somebody was top scromes WWE and I pulled an Oscar Super Fractor for them So that was I remember that quite well trout refractor angels Sammy Sosa that basketball Contra gold to 50 Manoa blue jays Yeah, for the most part probably green rookie auto Oswald Parazza for the Yankees Fractor Jimenez gold rookie win Kowski Red Sox to 50 Rookie auto Nick Prato pristine refractor to 99 for the Royals. Good box for the Royals Josh Cheslem refractory a blue refractor George Brett to 75 KC We're some rookie refractor for the Braves rookie refractor Velazquez Cubs. They just showed it up there He was like a man of the oak is he's Just hit 300 the other day they're showing like fastest 300 a lot of stuff Frank Thomas Ready singer purple refractor Nolan Ryan for the angels to 99 Tati so snap Yeah, I don't know a ton about wrestling, but I do my best to at least pronounce names right to know who's who's who Nolan Gorman rookie refractor Cardinals bat relic auto for Smoltz To 99 Braves Smoltz with a bat relic Probably use that thing a ton. Yeah, he was solid. Why then he was one of the better hitting pitchers at least Alvarez They would at least have good at bats sometimes Carol rookie refractor Diamondbacks blue refractor to 75 Ron Santo Cubs Look at that a gold gunner Henderson of fresh faces six to 50 for Baltimore Jim tommy Torkelson refractor if on her error key refractor Cardinals own Grissom Kronoworth orange Chris Bryant's Rockies to 25 God rookie auto Oswaldo Cabrera for the Yankees now good break for the Yankees Shorber Jersey or not Jersey, but refractor gold Larry Walker Cardinals the 50. Oh That's neat Marlins Gary Sheffield going going gone autograph 5475 Sheffield Marlins It's pretty cool Got Mauer refractor and a blue refractor rookie of Nick Vespy for the Orioles that a 75 Mike D What's up, man? Numbered in short prints. Yeah, the Vlad jr. Swings of summer and we had purples of 99 Ryan Goldschmidt Chesham Langoliers to 75. We had Josh Smith Ali Rushman Larry Walker and Ron Santo numbered cards here to 75 Michael Harris Caleb Killian Nick Vespy George Brett Golds here to 50 Randy Johnson and Alec Manoa and a gunner Henderson Also had the gold Larry Walker to 50 when Kowski and Jose Canseco as a double-ray orange to 25 Chris Bryant and pink to 15 Corey Lee Relic autos to 99 John Smoltz base bow Jackson Torrey Hunter and a Starling Marta It going going on Sheffield auto for the Marlins to 75 Cabrera Yankees Prato to 99 Royals Parazza Yankees up hell Phillies Gunner for the Orioles a Springer to 75 Blue Jays and and Karnaz Siona 75 Marlins. There was also a Mike trout Seven wonders in the break. Thanks again, everybody moving on to number 18


All right. Let's see. This doesn't look right. I think. Let's see if I can. Do you guys see the presentation right or is something going on? Yeah, we can see this line. All right. Let's go. Sorry. Let's go ahead and get started. First of all, thanks. Thank you guys for having me present here. In this talk, I'm going to talk about Temporal, which is an open source, reliable, scalable microservice registration platform. And hopefully, but the end of this talk, you will see the parts of the reliable and scalable and stuff like that. And why does that matter and how Temporal solves those particular issues? My name is Tijku Mishordilovic. I'm a developer advocate at Temporal. Most of the project lead at CNCF Serverless Workflow Specification. Here's my tag if you want to follow or say hello. About Temporal, just a couple of links. If you're interested or after this talk, you want to learn more about it. Here's some notable links like the website, of course, docs, the meetups. We have monthly meetups. So if you want to meet the team or meet the rest of the team from Temporal and ask any questions, you're more than welcome to do that too. For any questions that you might not want, you know, kind of private or whatever if you have, you can always email that product at Temporal.io as well. In addition to, you know, kind of like things that I'm going to talk about today, you can see a bunch of different case studies by different companies who are using Temporal in production and you can go to the website and access them and read how, you know, the different use cases and how different companies are utilizing Temporal. Now, when we talk about Temporal, it's really two things. We talk about the server and the different SD case. The server itself is just a goal and binary. There is nothing to it. And you can deploy this binary on Kubernetes. You can deploy it on Docker. You can deploy it really in any infrastructure that you currently have available. In addition to that, Temporal provides a cloud platform where, you know, if you don't want to deploy it yourself and you can deploy it on the Temporal cloud and run, you know, use that for your applications as well. As far as the SDKs goes, Temporal currently has four SDKs go PHP, Java and Node. And it's just like the same thing. Since you're using a programming language approach to write your business applications, you can deploy them still on any framework that you currently have existing or tested and employed on any infrastructure you currently have available. So Temporal is not restricting you in that way in any sort of way. So we talked about the Temporal server, what it is kind of on the high level, but let's kind of like take a little bit look inside. So the server is composed of five different services. They're independent services that communicate with each other to the front-end service and we'll talk about what each one does. But the basic idea is that you have full control of your server's scalability in terms of horizontal scaling by deploying your server on multiple nodes, for example. And you also have horizontal scale, vertical scaling by being able to replicate, for example, each of the internal services of the server and that way achieve scalability of your applications as well. So let's just quickly look at each parts of the service of the front-end services, basically exposes a GRPC API that your application that you run actually can communicate with the server. So all inbound calls from your client application from the microservices you're developing can communicate with this front-end service. So the history service deals with things like workflow or your business logic state transitions. So here, the state of your current execution of your different application is stored and things like that. You have a matching service. That is the service that actually controls the execution of parts of your business logic applications. So this will be more clear here in a minute. And basically parts of your application communicate with this as well. And then we have the internal worker service which does some background processes, replication, and blah, blah, blah. As far as the database goes, Temporal supports Cassandra, MySQL and PostgreSQL for persistence. And the database stores a lot of different things like your workflow task, like what's currently happening, what should happen, what has happened so far. The data that is local to your business logic or the data of your different executions, the events that are happening during the execution of your applications, and also stores a bunch of different visibility data that we'll take a look at as well. The scaling of the database part of the Temporal server really depends on which database you use. So it's going to be a different scaling factors if you, for example, use Cassandra versus MySQL. As far as observability goes, that's always important. The Temporal server itself emits, and as well as the SDKs emit a ton of different metrics out of the box. So there's nothing really that you have to set up on the server and on the SDK side, since those are your applications, you just have to say which metrics you want to actually use or not. And these metrics, of course, especially for the server side, you can easily scrape with Prometheus and also define the different dashboards with Grafana, for example, your favorite metrics systems. In addition to metrics, out of the box when you do your work with the Temporal SDKs, you get tracing, so you can trace your execution of your applications on things like Yeager and stuff like that. Now, let's take a look, I'd like to take your approach and let's see what Temporal server really looks at from a different perspective or user perspective. So if you are a developer and you really want to focus only on writing your business logic or implement the requirements that you have to do for your application that whatever company you work at, the Temporal server really looks something like, okay, I don't have to worry about things like event handling, dealing with timers, dealing with actually storing anything in my application, transaction management, the Temporal server is fully transactional and things like that. I don't have to deal with, for example, if I'm calling multiple services in my applications, I don't have to deal with any queueing systems. And also like we saw, we don't have to really worry when we write our code about things like analytics and metrics that come out of the box for you. Now, Temporal server is not kind of like a joke and because of the scaling factor which can happen in both the server and then of course also in your application and you're actually able to execute hundreds of millions of these business logics or these workflows currently. So this is kind of like a very interesting approach that you have something so powerful that you can really write your applications and scale them on a very high level. Now, the Temporal server itself does not execute your code directly. It more like guides your execution of your code but there's still code is executing on your servers and on your deployments. The Temporal server then tracks and managements your application and also its state. Now, at the same time, if we look at, for example, the SDKs, as a developer when you write your logic, you can still use your programming language. You can still write your apps in Go, PHP, Node, Java or if you have Polyglot type of applications, you can use multiple of these languages. The SDKs with Temporal provides you, of course you have the capability of programming language but in addition to that, you have a very easy approach. We'll take a look in a second for development, testing and also writing your client applications that need to interact with your services and things that you have. Now, from developer perspective, and the reason why I showed it really is a lot of times when you're developing or adopting some sort of workflow solutions, you're a lot of times bound to the overall development environment and things of that workflow runtime. With Temporal, it's not really the case. You can still use your favorite ID in case this is IntelliJ but whatever you're using, you don't have to get out of that environment. And you're really concerned about writing three things. The first one is of course workflows, which is deterministic implementation so your business logic. You have to think about orchestration. So during your business logic, you're orchestrating for example, invocations of different services, which we'll see are called activities within Temporal. And you can write fully fault-tolerant control for logic. So he has full support of course of the programming language constructs, object-oriented constructs, but in addition for things like automatic retries, cron and time-out execution, based execution, compensation, fully sync and fully async invocations as well as of course parallel invocations of your services. Like we said, you can use all the OO features or your programming language that you're using and you also have for example, database conditional weights and sleeps and stuff like that all built in without you actually having to worry about how that happens behind the scenes. Now as far as the activities goes or the parts of your application, they're supposed to do things like file access, invocation of third-party services and stuff like that. There you can really have non-deterministic or really any code type of approach. This is your, we have people integration of temporal with different frameworks and right-headed, it's a big Java shop. So things like Spring Boot or Quarks event and stuff like that. And again, you have full sync and async approach, depending on of course your programming language used and stuff like that. The third thing is of course your workers. These are processes that host your workflows and activities that communicate to the temporal server, GRPC of course, using long polling and they provide full data privacy. So even if you have a temporal server, your application has some privacy or private information that you don't wanna secure information that you wanna share, you can encrypt it on your end. So the temporal server when it saves your state or your application and stuff like that, there is nothing there that is stored that you don't want to. Now, as far as from the app development perspective, you have a web UI where, you know, this kind of typical for anything where you can use to monitor what's going on what workflows or applications are running which ones are not. You can look their full histories as far as events would happen. You can see the stack traces and stuff like that. And also even more powerful is a CLI that you get also for free, it's all open source. And you can actually do everything that you can do in the web UI even more like execute batch commands and stuff like that as well. Now, as far as app testing and debugging, which is very important in any workflow system, this is probably the one thing that is probably, you know, differs a lot between different implementations. As far as temporal go, since again, you're using a programming language approach, you have full support to use your favorite IDs, your favorite debuggers, your favorite testing frameworks and things like that. And again, workflows can be tested, they can be mocked and temporal is the case also provide a testing API where you can test your workflows where they're mocked without actually a server running, but it has an internal built-in capability so you can even run your tests offline. Same thing for activities that can be tested independently different, you can test different timeout options and stuff like that. So we saw this from the development perspective, what about some sort of architect perspective? Or, you know, I know now developers really do everything but still kind of like this approach of thinking about building some frameworks or higher level concepts to build your applications. So the first thing we probably wanna think about, hey, can I use my existing frameworks that I use? And this is especially true if you already have an existing application and you want to start introducing temporal or as a technology into your system. And the answer is yes, because of the way that temporal is again a programming language approach, you can use it in any framework that you currently have. There's no problem with that. The second thing, hey, can I still use my existing programming language? It's a lot of workflow solutions force you to kind of do develop in a way that you're not currently doing it. Then you have to basically adopt a whole new development model in order to start utilizing these runtimes and their services. So for as far as temporal goes as an architect, you can continue using your existing programming languages or if you're thinking about new applications, you can really write them in the way that makes more sense to you given the development team that you have currently available. As far as the dev environment, hey, can I still use my IDs? Can I still deploy to Kubernetes? Can I still deploy my applications to test them on the frameworks that I currently have going on? And again, the answer is yes. There is no restrictions that a portal imposes onto anybody really in order to adopt it and start using it. And so again, of course, testing, can I still use JUnit? Can I use Testify? Can I use PHPUnit? Things like that. And the answer is again, yes. You can test the applications using a favoring testing framework in the bucket inside of your IDs as we saw earlier. So as far as adopting any technology into something that you haven't written yet or something that you knew is fairly easy, but the problem always becomes, hey, I have existing applications. And this is kind of not like how every application is, but overall is you have some sort of data models on the left in this circle, some sort of eventing platform where you're getting events from internally, you have your object model or the representation of your business requirements and the thing that actually makes your applications take or work or what they actually do that is your knowledge of your company. And then of course your code wants to communicate with some third party services, UIs and stuff like that. So from the perspective of adopting temporal into an existing applications, really all you have to worry about which parts of your applications that want to turn into workflows or the core orchestration of your business logic that it does and which parts of your applications you want to turn into activities or as we said, parts of your applications which are responsible to communicate with third party systems, UIs, file access, database access and stuff like that. So now that we've seen all this now, what's still the core value proposition of temporal? And the core value proposition is really as if you're a developer, if you're an architect, whoever, it doesn't really matter, it's all really mixed, we want to write our application service services the way we want to write, right? And the value proposition of temporal is that by using temporal, you can have your services or applications that you run fully durable, fault tolerant, they can, even if you have some outages for five minutes or five months, you can still restore your applications to the state where the failure happened and continue their execution. You have fully distributed way of writing services without even thinking about it. You don't have five frameworks and whatever, you can choose what you want, you still have fully distributed applications. You can scale your applications, like we said, to execute millions of workflows concurrently, so it's very high scale. And of course you can write your services polyglot and the reason I put that is again, a lot of run tests restrict your single way of developing the single way of a single programming language or approach but polyglot, we saw it temporally, it can use currently for and I'm sure in the future, there'll be even more programming languages that will be supported. Now, again, let's take a look a little bit about how this works. So on the left-hand side, we have some sort of business class, this could be any classes, again Java, it could be a game go or PHP or whatever, where I have some my customer class and this is my current code that having my application, it needs to update some account and we have a get customer method which returns, so some sort of way to return some information and we have some exit method here, which it typically could be triggered by a signal, for example, from some sort of messaging service. Now, we have some, of course in Java, but this will be a little different in Go, for example, we have some sort of interface, again, this is our code that we currently have, there's nothing to do with them, portal that describes the methods of our business class that we have. So basically, first thing we have to do is we want to turn this into a workflow interface. So just with a couple of annotations at workflow interface, at workflow method, query method, for example, the get customer that returns could become a query method where, and also we have a signal method, meaning that our exit method can receive signals from different sources. And just with that, we've turned really our my customer class on the left into a temporal workflow. Now, of course, we have to still think about what did we gain with that?  So if something breaks during the middle of execution, you can easily replay the state and continue its execution, it can be invoke sync or async without us even thinking about using some sort of frameworks for that, can be fully versioned and also fully tested. But of course, we still have to say, okay, how do I interact with this thing once I have my workflow? And how can I actually write my business logic so it's deterministic? And we'll talk about the deterministic factor of the portal here in a minute as well. Now, the next thing, okay, now I've written my workflows, how can I actually interact with them? On the left-hand side, we have like a box to represent our client application. Our client application wants to start some workflow, stop and interact with them. On the right-hand side, we have the temporal server. So the temporal SDKs provide APIs to send commands to the temporal server. That can be, for example, start command, there is a bunch of other different commands and there is many, many more. So let's say through the code, we have here workflow kind of start, so we want to start a particular execution of the workflow. This command is sent to the server, which is then going to schedule actually the execution of our workflow by placing on the right-hand side, a little dot task onto the task queue. Now, on the bottom right, we see our application code, which again is a combination of your workflows and activities and your workers. Our worker is going through a long poll for this task, wait for it when he receives it, is going to get any information out of this task and he's going to then determine what to do, should we execute a workflow, should we schedule an activity, should we just go ahead and do nothing? If we have a long sleep or a wait in our workflow execution and things like that. Now, once this task has been completed on your application code, your application can send again commands to the server. The server figures out if it needs to, for example, create timers, if it needs to persist, things, whatever it needs to do, make it put another task onto the task queue, which is then again consumed by the worker and then continues the execution of your workflows and activities. Now, on the right-hand side, we see kind of like the continuation of the previous slide. So let's say a task arrives, our worker has pulled the task queue, has received a new task onto whatever task queue it's listening to. Now, important thing here is that temporal is a fully distributed system. So this particular app code could be something completely different. Or in case, let's say your application code crashed and you redeployed somewhere completely different, again, this application and the worker can still listen to the queue when it comes back up and receive the workflow task from the server and continue execution of your workflows. So the workflow task itself includes things like, okay, what are we supposed to do next? As far as the execution where application goes, but also includes information about past events and what has happened so far. And especially these past events allow us to replay our current execution to the point of where it either needs to proceed further. Or for example, in case of failure where it has crashed and now we have fully preserved the workflow state, let's say on the left-hand side, we see customer activities update customer account. This is kind of either where we need to continue execution or let's say in case of failure, we recovered from it and want to continue execution as well. So the replay really allows us to preserve what has happened so far without re-executing everything twice. So temporal provides at most once execution of your activities, for example. So the replay doesn't call your services five times and you have unexpected results. But anyway, so if so far the past events match the execution of your workflow execution so far, the workflow is deterministic, which means everything that happens so far matches with the event history of what happened and the workflow can continue execution according to the what's next information. If it's non-deterministic, that means you either introduce some change and things like that and the workflow is going to fail in this case. So what about microservice orchestration? Well, this is kind of like the typical part where how do we write our microservices? Well, I'd say we have a food delivery service in the top left part, which again can be polygonal completely and our application orchestrates third-party services that we don't really control, such as dispatch, restaurant, payment and blah, blah, blah. And the typical, this is kind of like the typical way of writing things. Well, you can still use this with temporal and you still have the ability out of the box to deal with intermittent failure with, for example, automatic retries of your activities. So let's say dispatch service has an intermediate error. It's down, you'll get automatic retries. You can also configure those retries and stuff like that and retry until the dispatch service comes back up. You can also deal with continuing failure. Let's say our payment service is down for weeks and we just can't recover from it. You can easily configure things like some sort of saga patterns or something to compensate. The work that has been done so far. Another thing that temporal allows you to do, which is really key is rate limiting. So for example, you don't want to write your food delivery service to bomb, let's say the payment service or the dispatch service. You can easily configure rate limiting, which can also save you, for example, cost in the long run if you don't wanna hit some service over some amount of time per, numbers of times over some period of time. Now where temporal really shines is a microservice orchestration where multiple microservices that you write are connected to the temporal server and using the temporal server. In this case, we have on the left-hand side our food delivery service, which has a workflow and its worker, sorry, talks to the temporal server. On the right-hand side, we have a dispatch service. Now dispatch service can be written by different company, it can be different department in your company, whatever. It's a completely separate team, for example, the rights to dispatch service, but they can together using temporal and its SDKs communicate with a single server. And what that allows you to do is again, you can, for example, rate limit each service individually rather than, as we've seen before, your food delivery service having to deal with rate limiting third-party services. You have full error handling and propagation between, for example, the dispatch service and the food delivery service. We'll take a look at that in the next slide. And again, the polygon aspect, you can write one application or the food delivery service in Go, you can write the dispatch service in Node.js if that's what your teams are working on and you can still communicate with each other without any issues. Now, one thing about error propagation chain in cross-polygal microservices, this is super hard to do, typically. You usually, when you have polygal services, you have to deal with either some sort of JSON or you have to deal with error messages being in some sort of string format and communicate with that with temporal. It's not really like that. Let's say we have a food delivery service again on the top left, which is written in Go, and our workflow, let's say, invokes an activity. And this activity, of course, through the temporal server invokes no restaurant service workflow, which is written in Node.js. That thing calls its activity and then again invokes just an activity of our payment service, which is written in PHP. Now, what happens actually when the payment service goes down or it has an error? Well, at this point, what do you do typically in your applications right now? The temporal, especially if all of them are using a temporal SDKs and communicating with a temporal server, you can easily propagate these errors back. So for example, the activity in our restaurant service can catch this exception in the PHP workflow. You can add some data to it, then you can propagate it back to the restaurant service workflow execution. This can propagate back, again, this is Node.js now that we're talking about, back to the activity of the food delivery service. And finally, our initial workflow which started the orchestration of this particular microservice, different microservice who can get the error. And when it gets the error, it's not like a four or four. It's not like service not available. It's a full error that has the payment service error includes things like the original error from the PHP payment service, the account information from the restaurant service, the amount paid from the restaurant service and things like that. And it can, you basically, you have full control at this point with this error, what you can do. And then again, this is polyglot across different microservices as well. So that's kind of it for what I have. I have also a short demo but I don't know if you're out of time or not. I apologize if we are moderators, please let me know. And for more information about Temporal, if you're interested, go to docs.temporal.io and get in touch again on the community side and Ruma if you're interested in meeting the team and then joining the monthly meetings. I do have a demo, but again, moderators, let me know. Yeah, so the time slot is up but I don't think we have any other talks in this track at 10 a.m. So if you want, you can go ahead with the demo and if people want to attend a different talk, they might head off. Before you do that, do you want to answer some of the questions? Yeah, are they all in chat? Sorry, I'm trying to. Yeah, I can just read out to you. So our question is, are workflows meant to supersede web frameworks? That is instead of writing application code in a web framework like Laravel, PHP, I read a workflow that runs some business logic. If I understand the, no, the workflows are really just the core implementation of your business logic. You can still use a web framework to expose them to your customers. So a lot of times when you use things like some web frameworks, whatever the web framework would be, you can still use it. You can define REST endpoints that make sense to your application that you expose to end users. And when they hit that endpoint, they can actually invoke different workflows or the core implementation of your business logic. And again, with Temporal, if you have some sort of web framework where you just get some requests from a customer and run some code, you have that still, but also with Temporal, you have full fault tolerance. You can deal, again, like we show with being completely resilient. And even if your web request fails, you can do automatic retries and recovery and stuff like that. And then finally be able to respond back to your web framework to your users. Does that answer your question? All right. You mean yes, they don't say anything in the chat. So they also have another question, which is how does Temporal fit with container orchestration or management tools like Kubernetes? All right, thank you for the question. That was very nice. It, as we said, the Temporal server does not really restrict the frameworks that you use. Temporal does have out-of-the-box Helm charts support for the community so you can deploy your servers on Kubernetes if you wish to.  It is one way of deploying it. I think most of the companies that we have seen that they use Temporal yet, they probably deployed on Kubernetes or some other sort of system that is similar. All right, and I think the last question is, can we able to do a micro front-end app structure using Kubernetes? I have to be honest, I don't really know what the micro front-end app structure using Kubernetes is, but again, with Temporal, your applications or your applications, as we said, you deploy them any way you want to. The only thing you have to do is make sure that you can, of course, communicate with the portal server or cluster of Temporal servers that allow you to have all these benefits of using it. So I just see another question come in. I'm not sure if this is gonna be something related to temporal, but why does Windows have issues with Kubernetes? In handling load balancing pods? I'm not really sure. That's probably a Kubernetes question more than Temporal question. I'm not really sure how to answer that one. That's fine, that's fine. And just a clarifying question. So workflows are more like task runners, is that correct? The workers more than anything. So basically, like we said, Temporal server does not execute your code. Your applications are still executing the code. So what happens is, let's say you have a weight in your business logic. So let's say what you wait for a week, right? Your worker is going to make sure that the timer is actually created on the server and it's going to hold the execution of your workflow or your business logic for as long time as you specified, of course, in your code, in the end. During that time, there is not going to be any resource utilization. So this is kind of like this whole Kubernetes and scaling to zero thing. While let's say your workflow and your applications, again, waits on something, perform some sort of timer work where you either wait for an event for a certain number of time or there is just simply no execution for a long running workflow, there is nothing going to be utilized under your application resource set. So that's kind of like, hopefully answers your question. So in a way, yeah, it would be kind of like a task runner, but that's more of the part of your worker part.  And we see that all the time where it's scalability is not only on the server, Temporal server side, but for example, you can have a whole fleet of workers for the same application. And you can really say, okay, I want this workflow to run and this worker, these workflows and activities of this worker, and you can scale your applications and a very high level in order to utilize or have high performance or throughput for your customers. All right, I think that was all the questions. Thank you so much for answering. And yeah, if you want to go ahead with the demo, I think we can do it, but there is a keynote starting at 10.30. So, what I'll do then, I apologize, but what I will do, and I'll do the demo next time, apologize, I didn't know and thank you again for allowing me to talk over the time. I did want to show you, the demo is basically that I wanted to show is a polyglot application using the Temporal, Java, Go, and PHP as the case. And it's just a game. I like to do kind of... Sure, sure. When I do things. But it is on GitHub, you can go to this URL here on the GitHub. We cannot see anything on the screen, by the way. Sorry to interrupt. Oh, am I not sharing it? Let me try to share it, yeah. I'll put it in the chat. Is that okay? Yeah, that's perfect, yeah. So here you go for anybody interested. This is GitHub repo for the demo, and it has clear instructions. And also if you go to the Temporal YouTube channel, I do have a video that shows the demo off as well. So you guys will not missing anything. So yeah, thank you so much. Appreciate it having me. I'm happy to be here again. And yeah, if you have any questions, let me know if not, have a great day and great rest of the conference. Yeah, thank you so much.


Hey, good afternoon, everybody. Tom Stewart here on with Liz Trotter. And our guest today is Dom Williams. And this is Smart Business Moves. Yay, we're here. You know, we're like T minus less than seven days from the QDS conference, aren't we? Yeah. So I was going to say, maybe we could talk about some announcements. We have a whole bunch of stuff going on right now. QDS top of the list, of course, with it being less than a week away. Martha Woodward's event in San Diego. So if you are not going, try. Try to go if you can. It's an amazing event. Yay. Yep, it's February the 24th through the 26th. Well, actually, it looks like it's something starting as early as the 22nd. Yeah. Those are like the previews. Yeah. And the 27th also, they're doing fun stuff on the 27th. These are like pre-season games? Kind of. They do stuff in advance and after. They are. There's things that are done prior to. Yeah. Although if you're a service autopilot member, I think that they're doing an event, a full day service autopilot event on the 22nd, maybe? Yeah. Here you go. Well, 23rd, actually. That's on the website. I think Mike Callahan's doing that. Yeah. Go to the 22nd, though. I think Kurtz is on the 22nd. Oh, responsive? Sponsor bit? Yeah. I don't see anything. I don't see anything here for the 22nd. Not to say that they might not be, but it looks like. Let's focus on the meat and potatoes of the event. I said, yeah. That's good. The meat and the potatoes are going to start on Thursday. And they're going to do the welcome. And then I think they've got a tech panel, which actually says that. I'm sorry, but you cannot gloss over the amazing race. So I've never seen that. OK. Well, then that's why you're glossing over it. Have you ever seen that? You would not be. And Martha has put so many oodles of hours into this that it will be fun to even watch. So even if you're not participating, it's a great thing to watch if you get there in time. I must admit that I haven't paid a whole lot of attention to that. But I clicked on the More Information, and this modal pops up and says that you need to register your team. Yeah. Have you registered your team yet, Liz? I'm actually a sponsor at that event. So I will have a table, and they have to come to my event. They have to come to my room and do a challenge to be able to move forward. OK. Well, I haven't been handling that part of it. I might be a sponsor too. I mean, I know we're sponsors. I don't know anything. Yeah, you may very well be a sponsor. It's very fun. If you've never watched The Amazing Race, you should try and at least, well, you will be there in time, Dom. So you need to at least check it out. And you need to be at the finish line clapping for the winners, because they work hard to get through this. It's fun. All right. So now we can go ahead and blow past The Amazing Race. We can pass that out. OK. So we've got a tech panel for a few hours. And then there's an 80s night dinner and welcome party. So I've got my costume planned. Me too. Me too. I'm silent. Dom, do you have your costume yet? Oh, you're not sure you're going to wear that on? My daughter lives in San Diego. And Thursday night, it's the only night I'm going to be able to see her. So I'm going to slip away and have dinner with her. I'm a good dad, OK? Give me a little something. I am. I'm saying that's solid choice, Dom. Solid, solid choice. Absolutely. All right, then Friday is a full day. Full day on Friday. Yeah, I'm going to 7.45. That's going to be awful early for the folks at the party. Yeah. OK, I'm a little confused, though, because breakfast is at 7.45. And then it starts at 8 o'clock. That is a quick breakfast. You've got to eat fast. Probably eating in the room. OK, maybe that makes sense, OK? And then creating other streams of income. Oh, Gosha and RJ, who doesn't love them. And stop on Mike Callahan. Talked to him recently. He was on Smart Business Moves Monday. Yeah, yeah, yeah, yeah. And then we've got, oh, I don't know if anybody else can see this. It's even small on my ginormous screen. Let's go through acquisitions with Kyle and Marvin. That's going to be great. Yep. Who doesn't love to watch Meghan likes? She's so entertaining and informative. Is Marvin from like the green space? He's not in the housecleaning world, is he? Ask the wrong person. Here, come on. Marvin, I don't know Marvin. I don't know him. Because one of the cool things about this event is it's not just housecleaning companies. So you can learn something from other field service vendors. You've got the window washers, the soft and pressure washer type folks. You've got some landscaping people. So people in other industries learn tricks that housecleaning companies can learn from. But we all know Kyle's in the house.  That's an enchant. He's a heavy hitter. So that would be fun to watch him go at it. We knew Kyle back when he went through foundations, but we do it's like 17. I think he was, was he that young? I think it was 19. Seriously, I don't think he was 20. No, he was 19. He was running for mayor. That's when he went through foundations. Remember? I remember clearly. Oh, that's crazy. Yeah. We went on a cruise together. So I remember that really, really well. He was young. And we put him on the cover of Cleaning Business Day. And this was back when we actually did the whole, you know, magazine style.   I remember that. It was awesome. All right, well, we're going to have a couple of opportunities to see Kyle, because look, down at 130, he is doing great, which is a growth opportunity again. And yeah, we mentioned Megan. She's like one of our favorite CPA accounting types, you know? She makes accounting fun. That's an easy thing to do. She makes it really easy for people to understand. I love that about Megan. All right, and lunch is provided. That's awesome. People like me who love to eat love that. And then gosh, I haven't seen Jason in forever. But Sarah, ooh, right? She's definitely a little better. Pretty solid lineup there. Very good lineup. Everybody needs to be there. I love that they have that group of people directly after lunch because they're going to wake people up. It's not, that's a hard position, but they will absolutely wake people up. Everything happening this afternoon, every speaker up here has got so much game. Yeah, absolutely. Can't wait to see Paul and Libby. That's going to be fun. Hey, got breakfast going on. Starting a little bit later on, Sarah. Yeah, look how long breakfast is. 45 minutes for breakfast there. Yeah, that's crazy, right? 45 minutes. All right. Look at the lineup leading us off Saturday morning. Whoa, there I am. There you are. Here's the meat potatoes. That's what we've been waiting for. Yeah, we got you and Olu. All right, we're going to have you both. I'm excited. Looking forward to hearing that. Let's see. Who do we have for systemizing customer service? Is it a secret? It's probably you. No. It's you.  Oh, no. All right, so maybe that's a secret. Maybe this is going to be Martha, right, popping in there for us, which would not be surprising. All right, and then we've got our closing and then the after-party luau and dinner. Well, I think I'm leaving before the luau. I'm leaving directly after the closing, I think. Oh, that luau looks like it's going to be fun though. I'm going to be missing out. Looks like my costume plan for that as well. Oh, gosh, I am going to be missing out. I knew it. I got a plan. Dang it. All right, and then Sunday. So if you're staying, they've got the Sunday brunch. And I think they're planning on going somewhere too on Sunday, but maybe it's just going to be sort of ad hoc. Probably have to go to her Facebook group to find out about that. All right, well, you guys saw the price. Saw a great pricing on this event. Is that? Oh, I didn't see. Oh, I don't even see everybody. Where are they showing up? There they are. Hi, y'all. Oh, didn't eat. You're already pickled. Oh, my girl. All right, we're going to help you out of that. All right, so, but today. Oh, wait, no, I had a couple more announcements that I wanted to talk about, Tom. You have the Made Central event coming up. The first one is in March. Right, maybe talk to people about that real quick. This is... Tom, are you thinking, hey, I thought they wanted to talk about hiring automations. We do, I swear. Yeah, we're doing an event for Made Central partners. If you're not a Made Central partner, I guess you can come along, but it's going to strictly be about workshops on how to deploy Made Central in your business. It's really easy to get to, just go to Made Central dot Academy and it'll bring you here. I'll drop that. I'm so glad you shared that. Somebody was asking me the other day. Tom, are there still sponsor things for the March? There are. Had some people moving around. Liz is actually doing an event with her group on the end of the April event. We had some people signed up for March and wanted to move to April so they could kind of flow through and do that. So we've got some spots in March, April and May. We've got spots on all three. And it's the same event for all three dates. We just broke it up because we wanted to do workshop style exercises and that's really hard to do when you get a large group of people. So it's more personalized attention but we're going to have our Made Central staff there. I was just going to be there. Rebecca's going to be there. We'll even make Cameron come out of his conclusion and he'll be helping us with some things and Victoria and Matt, Matt's going to be coming. Liz, you might even be showing up for some of these. I don't know. You never miss a message from Charles, right? I'll be there in April because my office gal is coming also in April. We just registered yesterday. Not sure if I'll be there for any of the other ones. I got a tight March. If you're there on March, we're going to put you to work. Oh, well, I might come for that. You know, I do love a good work day. All right. And then another thing in March is happening is on March 10th, from 10 to one, is a hiring boot camp through ArcSea. So it'll be Debbie Sardone, me and Sean Day. You know what I mean? You're going to start- I've heard of this one. What day is this? Well, you know, I'm going to get insider information here. What to, what to, what to, what to, what to, hey, you know, you can say, hey, Tom, heads up. Sorry, Tom. I just now realized it when I got the confirmation today. So it's March 10th, and it's 10 to one Pacific time. Is there a URL or something, anything? It's so new, it's not even on the internet. I'm giving you guys insider info here. Cost? So, no, no cost. Huh. Yeah. Just get my lockout March 10th, and it's up from when to when? So a 10 to one Pacific, a one to four, five, four, yeah. Is that right? One to four. It's actually four hours. So I have that one. It's actually four hours. So. Also, it'll be. 10 to two. Yeah. 10 to two, not 10 to one. I'd probably put it on. That's all the 10th, and the 10th is a Thursday. I'm sure we'll see some marketing for that. Oh, yeah. You'll see a lot of marketing coming through for sure. You guys want me to tell you what it is? So it is, it's one to five. The first one, Debbie is going to be up with how to find and hire a player. That's what she'll be talking about. And then we'll have a quick Q and A. And then Sean, his topic is the secret to how we hired over 100 employees last year. So that, I can't imagine that people are going to want to miss that. I know I'm not. And then we'll have a quick Q and A. And then I will be up with using disk to recruit, interview, hire and onboard. We'll close out. We'll close out the day, the boot camp. So I think it's going to be a great event. We're all really looking forward to it, working together to try and make it all a nice cohesive event. And then the last thing that I wanted to talk about was other than my cruise in Mexico. Yeah, y'all, if you aren't going on a cruise in Mexico, be jealous. But other than that, my... How do we sign up for a cruise? How do we sign up? I'll send you a link, Tom. I know, I know better. There is no chance you're going on a cruise. All right, the ELC event, Employee Life Cycle event. 15 points in your employee life cycle that you need to nail down and know exactly what you're going to do at every single point. That workshop is on April 24th through 21st through 23rd directly after comms event. Same back, place, location. Same exact thing. Do we have a URL for that? We do. I'll pull it up and send it over to you. All right. That's open for everybody. It is. It is a paid event, though. It's free for people in some of our groups. So Liz, it's open for everybody that has a little bit of money. Well, and it's free for people that are in the circles. Yeah. All right. So I'll give that to you at the end, Tom. But we should probably... Nice. March 10th, look forward to it. Hey, Denit. I didn't see it earlier. But we should probably get started. It's already 2.18. Yeah. Give everyone what they want to hear. Good thing we started. I mean, how long was today? He wasn't, you know... The purpose of being here isn't to listen to us ramble about news of the day, is it? No. Probably not. I probably could have just stayed out for 18 minutes and... Hey, you know, all this is important to me because it all relates to, you know, my business. So I appreciate it. Yeah. Absolutely. What's been going on in your world, Tom? Not much. Like I was telling Liz before we hopped on here is real estate, doing things like that. You know, just constantly growing all of my businesses. So... So yeah. Tell us a little bit about your businesses, Tom. I think that people will be interested to know what exactly it is that you do. Yeah. So when I was 18 right out of high school, I started a maid service cleaning company. So we've been in business around, I think about 11 years. We do residential and commercial cleaning right here in central Indiana. Our main focus now is to keep branching off into more commercial and larger, you know, commercial contract accounts. So that's our major focus. And then last year or three years ago, I started a applicant tracking system for small to medium-sized businesses called Hire Who, which is really what I talk about a lot more now. And that helps people automate and streamline their hiring process. Last year, I acquired a two-drink barns by the name of Lexi's Drink Barns. So we sell pretty much soda fountains, stuff like that, you know, really quick snacks too. It's just pretty much a drive-through. We have two locations right here in Kokomo, we're at my hometown. And that's a really great business. I love that business. It's fun. And then also, I pretty much take all my money and I invested in multi-family homes. And that's what I really love to do, which is why I told you, Liz, we need to talk real estate. Yeah. So that's what I do. Yeah. We do all multi-family too. 98% multi-family. Yeah. I do love that.  So we're just now getting to that point where we're at like 30, we're only at around 30 units or so. So we're to that point where like now we're going to start handing all of them off to the property management company. So yes and no, some are, some aren't right now. But the goal is to, yeah. Only it can be cool. You know, getting that phone call at two o'clock in the morning that the hot water heater busted is not fun. Nowhere near as fun. Absolutely. Every time you have someone say, oh, I would hate, I love, late Lord sounds fun. I would hate those late night. Everyone goes to like the extreme. It's going to, you're going to get those three or four minutes. I have never got one of those calls yet. But I believe. Okay. I hope, I hope for your sake that you are currently knocking on wood somewhere. Yes. Right. I'm knocking for you. But yeah, that's what I do. Well, yeah, you're, you're a busy little guy there. You're doing a lot. That's for darn sure. That's like, you know, that's true entrepreneurial spirit. You know, it doesn't really, you know, it's not so much about the industry. It's about the opportunity. You know, part of, part of being an entrepreneur is being opportunistic when something falls in your lap.  The drink bar thing is a concept that I'm still can't quite get my mind around. I need to go to Indiana and check that out. Yeah. Yeah. We just recently heard about this. Super interesting. You only drink soda. You only drink water lives. And coffee. Well. And my deep black coffee. Wow. Coffee. So that's not even real coffee. Oh, it is. It is. It's a great, it's a great way to drink coffee. I think. Okay. My cat coming to harass us. You guys. All right. So we're talking about higher who today.  And she recommended that I get you on here. Megan likes. She was like, no, you need, you need Dom. I love what he's doing for me with higher. She's such a star. Yeah. You know, it's. Automate as much stuff as possible. For her company.  Implement practically everything to a T. You know, maybe. She's like one of those people that just implements practically everything with them. I love it. If there's a, if there's a button in the menu that need to click on it and figure out what it does and put it to work somehow, because they wouldn't put it there. If it didn't do something to help you. Yeah. Yeah. So, so yeah. So I think we can, we can go into, you know, sharing with automations and things like that. I actually, I have a list in my head here. Okay. Of certain things. I've got that where we can really talk about, you know, what, you know, business owners and small businesses can really start out of automating in their hiring process to save them tons of time. And, you know, to keep their applicants engaged because I think a lot of people forget about that, especially like right now in the world where people are job hopping and it's very difficult to get a player. It's because we're not really engaging with our applicants as much as we should. So. Good. I'm super excited. So, so one of the things that we can touch on for, that's a hiring automation. And this is a very simple one is scheduling interviews. So, you know, this is when, when you have a qualified, candidate and, you know, you want to interview them. Why don't we automate that process on scheduling their interview. So everything that I'm going to mention, obviously you can do this in hire who, but I don't want to make this a sales pitch. So I'm going to also give some examples of how you could do this with other softwares as well. And one of the ways is Calendly. You know, so if you have a free account, Calendly, I think they still have a free option. I'm not sure. But you can set up, you know, your own calendar of when you want to do in-person interviews or whether that be phone interviews. And you could send those links to your applicants. And that prevents you from calling every single person and, you know, going back and forth and seeing when they're a bit. I mean, that's just so much time. That's just not needed. You know, so that's a very simple automation that you could set up in your business for scheduling your interviews. Do you guys do that now? We do. We use Calendly. I love Calendly. Super, super nice. I think that's a great suggestion. I just said for everything too. Once I, once I learned about Calendly, I'm like, oh my gosh, how do I do this? I'm like, oh my gosh. I, once I learned about Calendly, I'm like, oh my gosh, how easy is that to schedule all of my appointments. My poor husband every once in a while gets a Calendly link. Yeah. Look, I'm busy at that time. Yeah. Another thing which I probably should have mentioned this prior to the schedule interviews, automation is the screening process. Right. This is another just basic function that every business should be doing. You know, for us with owning cleaning companies and a lot of the people that we're talking to, you know, there are certain requirements that like a cleaner needs to have before their L's would have worked for us, whether that's a vehicle or driver's license or they need to be 18 or clean back, whatever those things are, those should be, that process should be automated. And you know, if they're a good fit, they should move forward in your hiring process. And if they're a bad fit, they should drop off of your hiring process. I like to call those knockout questions. Right. If they're not a good fit, they're knocked out of the hiring process per se. That process should be automated. So we do that as well. Within the first stage of our hiring process, we asked those initial questions on, you know, are they, you know, are they willing to take a background check? Do they have a vehicle? Do they have a driver's license? Those are things that that's a really another basic, basic function that should be in everyone's hiring process as well. And so when you say, say ask, I mean, I guess this is, is obvious, but just, you know, the actual application process is done online.  I mean, I don't know if there's anybody out there that still has a paper application, you know, there are, there are, I ride by, I'm telling, and maybe not for cleaning companies. I'm not really sure for us. We're a lot more advanced than, than I think we give ourselves credit for. But like when we're, when I ride by like restaurants and stuff, there's literally signs out that say, apply with them, like come in and apply. I'm like, whoa, what's coming in just to fill out an application no more. Those days are over. So actually we have, you know, we're, we're, our office is in a location where people are walking by and we say apply with them, but we've got a couple of kiosks that are set up. They're just the little, you know, bricks that chrome, you know, bricks with a keyboard and a monitor on it. We set them right down there. Oh, in your office? That's good. Yeah. We have people walk in, but you know how we have workstations set up in essence to allow them to fill out an application. And then, you know, it's done online. Yeah. So, so my office is in a spot. We do get cars coming by, but it's not like we're in our own private building. So like you literally have to pull in our lot. And there are people that come in and they're like, how do I apply to work for your company? And then we either provide them with a, a text line where they can text and start the application process or they can obviously just go to our website. So we refer them back. I do like that idea of having a, kind of like a little workshop in your office lobby where they can come in and use your resources. So I do love it. Do you have those in your drink barn yet? No. We don't. That's an opportunity. And you could be recruiting for your cleaning businesses and property management, you know, property management help. I mean, it's like recruiting for your whole empire. Cause you got a lot of drunk and then I wake up the next day and sober up and say, gosh, I guess I have a job now. Yeah. Oh, I like that. I like that. I'm going to take, take that note down. Take that note. Yeah, I do too. I love that. So. Here's a real one more question real quick. So like if somebody is using hire who at this point in the process, uh, the knockout questions and, um, what was the other thing that we already talked about or you forgot? Um, the knockout question and the scheduling of the interviews. Yeah. And the scheduling of the interviews at this point in time, if somebody's using hire who they have not had any, they haven't done anything, right?  If you're setting up your process, like what, like how we're mentioning, there's no physical interaction or any manual tasks that one has to do, right? Yeah. You can bottom that from the point that they complete the application, they fill out the screening questions. And then the other portion too, before the scheduling the interview, some may add it like an assessment test that they wanted there. And then we could say, okay, Liz, if I send you an assessment test and you get an 80% or higher, I want to interview you now. And then the next step is, okay, let's go ahead and get that person scheduled for an interview. So you can automate that process 100% if you choose to be hands off like that. Okay. And the value to people here is just, just think about that at that point in time. You haven't done anything yet. And you already now have pre-screened people scheduled on your calendar in your openings to interview. I mean, I feel like that is so many people spend hours upon hours trying to sort through all of the people and screen everybody and reading every single, you know, resume and application and doing all that. I know I have people that say, hey, Liz, I'm not going to be able to be on a meeting today because I'm hiring. Yep. I like that's the last thing. What do you mean?  That makes no sense to me. Can I share my screen purchase? Absolutely. Absolutely. This would work. So here we go. So this is kind of what my process looks like for our solo cleaning tech. So when someone comes in, they come into the applied field here. Okay. Then, you know, we do a phone screen depending on the, what's the phrase I'm looking for? Depending on how serious we're recruiting at the time. Okay. So there's going to be times where, you know, we've got enough staff for where we're at and we want to put things on autopilot and we don't got to watch it every day, but we're always recruiting. We're always still recruiting. But there are going to be times when we do phone screens as well. And then there's going to be times where we try to reach someone and we didn't get them on the line. So then they kind of go in this attempted communication field, right? And something happens on the back end for that as well. And then we have the interview stage as well. And then from the interview stage, we'll give them the offer and then we'll have the, the higher field as well. So we, we pretty much can put as many stages here as we like. And we can customize this for every single job that we have for our company. Oh, great. Yeah. All right. So this would be for a solo cleaning tech. You might have another entire funnel that is for a commercial cleaner. Yep. Regional sales executive or, you know, so in my account, I've got a lot of Gooberish because I use it a lot for demos and whatnot, but like, this is a real one. So this solo cleaning tech, I got a hundred and ninety five applications for this specific job. So if you think about that, if you don't have a process, that is truly doing a little bit of automations for a hundred and ninety five people, that's not this field is falling through the cracks.  Right. Yeah. If you're not automating some of it or if you're not, you know, engaging with them, then you're losing out. You're missing out. Yeah.  And then you're just letting them go. Right. We wouldn't, we wouldn't spend money toward a marketing source for clients and then not answer the email or not answer the phone call. Well, some of us would. Yeah. We have seen that happen before. Yeah. So one of the things that we also automate there, since we're talking about it, is we automate the first engagement. With the applicant. So, and we do it differently because, you know, if you're using indeed mostly for your, for your hiring process, which most of us are, the only method they have is you can, you know, send like an email that says, Hey, thanks for applying and stuff like that. We'll see in 2022. A lot of us are not checking. Like we're checking our emails because we're in business, but the people that we're trying to attract do not check their email. Right. Right. So what we do is we hit them with a text message. And we make it personable. So we say, you know, Hey, Tom, thanks so much for applying for CNC cleaning services. You know, we want to get to know you. Tell us a little bit about yourself and why you applied for our company. And then they, those people start to plot. They start replying and saying, Oh, you know, I'm a single mom of two. And I just moved to the area.  And I just moved to the area. They give us all this information. And it's completely automated. Yeah.  Are they doing it through a text or do you take them to a form to fill out? No, no, no. This is all a text. This is all text communication. Okay. I love that it's all text because I can see how people are going to be so much more casual. And they're going to, they're going to give you overshare. Yeah. They're going to give you different info. Yeah. So, you know, so that's a really, that's a really cool thing that we do. So we definitely automate that first engagement and we ask them to do something. And that's, that could be just as simple as just tell us about yourself. You know, we make it very open-ended so they can give us as much as they want. So is this like a chat feature on your side that you've got somebody once they start telling them about themselves? Do they engage in a conversation? How's that process? I'm going to share my screen again. So there's a couple ways that you could communicate. So we have this communication tab here. And if you just look at my screen, because I've been using hiring for a long time. Yeah. So look, I'm scrolling down. These are all texting conversations. No. I mean, it's crazy. Okay.  So my operations manager must have texted her and asked her to respond and she didn't respond. Right. But if we have a text conversation, this is what it's going to look like. Oh yeah.  And there are businesses that are doing this without hire who and without softwares, they're doing it with their cell phone. You know, they're doing it with their cell phone, but it's, it's too, it's too complicated to do that. There's two more engagement with texts than what you will with a phone call. And how many, how many texts can you keep going at one time? Oh, like conversations. Yeah. Conversations. Oh, Tom, we can, first of all, we can text all these people and have multiple conversations. I can be having a conversation with Jaila here and my manager will be having a conversation with Holly. We're all going to see that conversation. You know, nothing's going to fall through the cracks at all. It's time, it's time more productive and trying to deal with it. Yeah. He's going to fall through the cracks there. Um, another automation that we have. So you guys hear the conversation a lot about people trying to stack their bench, right? Like even when you're fully snap, let's stack our bench. Well, here's the key that people miss out on. They stack their bench, but they don't engage with that bench. Right? So, you know, the way that you guys would do, so I think I got an email from made central today about a, a live demo tomorrow, right? Because you, I'm assuming you guys have a list of all of your leads or actual clients or partners. That's what you guys call them.  Well, again, for my business, we look at our applicants just like leads. We have to treat them accordingly. So when you have a bench, let's say, of 10 or 15 people, why aren't you touching them every single month? Just check it in. It's been, I know it's been a month since you, I know it's been a month since you applied for, um, CNC, you know, we're still around. Let us know if something in your situation is changing and you want to have another conversation. You want to have another chat. Okay. So just basically reaching out and saying, Hey, are you still interested in the job? If you are, let us know. Let us know.   You didn't even interview most of them engaging with them. Keep touching them. So, um, so that's what we automate that as well. You know, drip campaigns and setting up some of those campaigns for engaging with those applicants. So nice. So it just keeps going. Is there an end to that? Is there, is it, you just keep doing it until they ask you to stop or. So, so you can set that up based on, you can set that up based on the, um, the job that they apply for. So maybe you only want to do it six months or you can base it on the talent pool. So people call it binges. We call it talent pools. So you can base that on, okay, we want to set this automation to last for six months of when they entered that talent pool per se. Okay. And I want to follow with them every single month for six months or whatever that looks like. That feature works really well for, um, for lawn service companies, people that are seasonal, you know, they can actually do a lot of recruiting in December, January, February, when it's winter. And then when they get that application, they can market to them and say, Hey, our season's approaching our season's approaching. And then when spring hits, they can actually do the hire. Yeah. They've got like, bam, now they've got a huge list. Yep. All right. That's my way. Um, another thing, um, is, and here's a, here's a quick fact is 40% of candidates will lose interest in a job if they don't hear back from the hiring manager within a week of the interview. Okay. So, you know, get an interview. Let's say they're good, but then like you take forever to respond to them for whatever reason, they're already looking for another job. Right. Um, and they might already think that they didn't get the job with you. So, you know, you can set up automations as well to where after that interviews taken place, Hey, let's send that person a text message and just say, Hey, thanks for interviewing. You know, here's what our process looks like from here. You know, sometimes you just don't know, Hey, it's going to take me a week to get through the rest of my people. We'll be in touch. And this is how we're going to get in touch with you. We automate that, that process as well. So what does that look like on, like on your customer side? Is it like, okay. So you've had an interview.  You want them to get the, the, the texts that says, thank you so much for applying. We've decided to go another route or so they just sort of pick which, which funds are going forward. You're able to create templates and you're able to create separate automations as well. And then you're also able to create specific stages. So remember that screen that I shared where you could drag people from different stages where you set up automations to go for every single stage. Okay. Okay. And you could say, Hey, when they moved to this specific stage, I wanted to send this specific template. All right. So it's customizable for each hiring process that you have. And, and so when you say it's completely customizable too, and things are going out, can, can people use images? Or is it just text or how does that work? Yeah. So we don't have the option where you can add an image into the text message right now. You can do that in an email. Okay. Cause you can also send out automated emails as well through it. But we don't have it to where you could send a picture through the, through the text right now. Yeah. All right. So the automation that works with the email, if I decide that, you know what, I'm old, I like email. And can I do email and texting or do I have to pick? Nope. I would always do both. Okay. Awesome. I would rather do both. Yep. And then the, and the other thing too is what, you know, those, those both forms of communication don't necessarily need to look identical. You know, the, the email needs to look a little bit different than what that texting is, you know, for message. It needs to be a little bit more relaxed than what that email should look like. Yeah. Yeah. For sure. Yeah. So, so yeah. Another auto. So this is a really good one. I think the, the, the, the best thing is, so LinkedIn does this really, really well. If you applied for a job on LinkedIn, when the, when the business reviews your resume, it lets the user, it lets the applicant know that. Oh, I do like that. That's awesome. So they see that there's activity and that. That's all they want to know. They want to know that they're moving through the process of your hiring. That's so funny, Don, because that is so simple, but so impactful. Yep. Right.  I can see how that's like, oh, okay.  Oh, cool. I'm still in it. Yeah. I'm now, I'm still getting hired right now. I don't know. I'm still getting hired right now. I don't feel like I need to keep looking for another job, especially if I really want this job. Yep. The other thing is too, and what I've realized in the past years is when your hiring process is so amazing and like someone, like, like I'll ask, you know, people that I interview, I'll say, Hey, you know, how was your, how was your, how was, how was it applying just because I want to get back on hire? Yeah. And they'll say, you know, oh, it was great. You know, I got this text message and stuff like that. And they're already wowed about the experience of just applying for your company. Yeah. You know, so they already have this good bubbly feeling about coming to be an employee now, you know. Yeah. So it changes that, that experience for sure. Yeah, absolutely. And it feels like a real company because like it or not, our industry still gets stuck a lot of times with, yeah, but is it a real company? You know, is it like really a company? They're getting all of this stuff coming there. They're not dealing with that with their family getting like, Oh, why do you want to go do something like that? It's not even like a real company. It feels like a pretty real company to me. I'm curious with today's labor market if, you know, under normal times, you know, after a week, somebody loses interest in today's market. I'm thinking, you know, if, you know, hire a good candidate within a day or two, they're going to have a job somewhere else. I mean, is that what, is it, is that what we're actually seeing? I guess is what I'm trying to ask. So here, I don't, first of all, I don't have any facts for this before I answer this. I want to be very transparent. Okay. Here's my, here's my opinion. And here's what I think I see in my businesses. You're right. There are people that, you know, will, will, um, you know, make a decision within two or three days of applying for a job. But have you guys ever hired people and you hire them and they work for like three or four days and then they quit? No, that's never, never. Liz, I know your business is amazing. So I know it doesn't have to be there. Okay. Here's the reason why though. The reason is, is because hired that person, but they still never taken themself off the market. They're still out looking, right? Whether we want to believe it or not, it's because we made that decision to hire them way too quickly. Right.  Sometimes we're making, we're making that, that they're, they're making the decision to choose a company too quick. They really need to see, they need to look at their options. I look, one of my interview questions is, hey, where else have you applied at? Okay. So what you want to do is be slow, let them take another job and you're the one that steals them away three days later. Could be, could be, could be. I don't think that's what he's saying, Tom. That'd be one way, that'd be one way to look at it. But like ask them, you know, what other, what other companies are you looking at? You know, what other companies have you applied for? And people will come in. I've applied at Target or I've applied at Meyer. And I've had an interview with this one. Oh, what did you like about their companies? You know, and let's be honest here, what company are you hoping that they're going, that they're going to offer you a job? What are you looking for? You know, and when, when they say those things, it gives me an idea. Okay. Who am I in competition with? You know, because we're in competition. I mean, that's truly what it is. So I would say you're right, Tom. You know, you do got to move fast, but I would also say it's about making sure that you're communicating with them about what your process is. So anytime someone leaves our interview, we're going to let them know, hey, if we want to bring you on, here's what's going to happen next. It was a really good idea to say, and by the way, if anything changes in your stunts, let us know as well. So if they have that other offer, at least you have an opportunity to have a discussion with them before they say yes. Yep. Well, I really like this. I haven't ever thought of this before, Dom. You brought up a new way of looking at things. Sometimes when those people are leaving in those first two, three days that they may have committed too quickly. And I don't think that we've ever looked at that. Have we ever talked about that in that way, Tom? I don't think so. You know what we think happens, Liz? What? The job's too hard. Well, they couldn't do it. They couldn't do it if the job was too hard. No. They just got the job. They probably didn't wait for it. Yeah. I mean, and that totally makes sense, right? That they never took themselves off the market. Now they got this better job. And sometimes people will tell you, you know, I got this other job. I thought that I didn't think I had a chance, but I'm super excited that Target called me. Yep. I got that. And we're pretty blunt with them too. That's a question we'll ask. Like, hey, if we were to hire you, you know, if we offer you the job, are you done looking for a job from this point? Yeah. You know, some will just say, well, I like to keep my option, but I'll always be searching. Yeah. Yeah. Moving on. It's still open because you're not getting an offer here. Yeah. Yeah. So yeah. So those automations that I went through, like seven or eight automations, I don't have any more freebies. The thing about this that I'm also hearing though is, you don't necessarily need to hire them two hours after they apply, but it's a pretty good idea to acknowledge that you've got their application. They're in the pipeline and, you know, you're interested in pursuing the discussion with them. Give them encouragement that they're in the hunt. Yeah. I have another motto to another saying, and me and Paul are actually going to talk a little bit about this in San Diego is the reason why we don't try to hire people too quickly is because they'll leave you just as quick as they came as well. Like, like for us, we want, you know, when someone, when we hire someone, we want them to feel as if it is a privilege like to be a part of our team. Like we don't just let anyone come here. You know, like we don't let anyone in this circle. So, you know, if you're interviewing and you're hiring them within an hour, it's like, oh man, they're pretty desperate to get some people in here. You know, they're pretty desperate. So there's all those things I think about when it's like, how quickly do we offer them a job? How quickly do we give them an interview? Those are things. And I know, you know, us being in, in, you know, a high turnover industry, you know, we make decisions based on our situation sometimes. You really do. But, you know, those are things that I, that I always look at with, for our hiring process. Yeah. I, I love this. You know, I think that a lot of times people don't, don't recognize how many parts of the process could be automated. Like they might even automate, like you said, you gave us what seven different automations in there. So, and I know you're not even giving us all of them. So, I mean, there's a lot of different things that can be automated in, in this, just, just in this one hiring process. So I think that's a great way for people to look at, even if you can't do everything, right? Start. Start with something. Do, do something. Automate what you can to get started. I'm guessing that what you run into all the time, Dom, is people are like, Oh, I can totally do that. And they get started. And then they recognize how much work it is to actually do all of this themselves. And to keep it all running smoothly. I know quite a few companies that start. They, they'll use like, what's the name of that one program, Trello, right? And they'll put everything in Trello. And then here they are, a fairly big company that I know of right now, was doing something along those lines. And everything keeps breaking. It breaks constantly. And just had this conversation probably last week. So when are you going to hire someone? Yeah, yeah. Is there time to stop? I'm guessing you have that where people are like, okay, now I get it. Now I get why I'm paying for this. Because it saves so much time. The other thing too, the other thing too, that we haven't launched this yet, but it should be coming within the next two weeks. So you guys are getting a, a very, a release. So whoever watches this video. Another inside stream. Yeah. All right. So digital interviews. Okay. So what this means is we're going to be able to automate. So Liz, let's say you go through my process and I like you based on your screen and stuff. We're going to send you a digital video interview where it will ask you the questions and you answer it in video format. And then all that data pulls right back into higher. Ah, interview people see their face, hear their voice without even being there. It's amazing. So you're, you're getting a much richer communication. They, you know, more than just the written word, you're actually seeing the passion or seeing the indifference or whatever. The part for me, the reason why I'm so excited about it is because with me owning the company, I can interview everybody. I can have unlimited interviews. I love it. Yeah. No kidding. And actually I love that too because you can really test some of your data, right? So before you have everybody, you know, you're screening them, you're pushing them through and you're, you're leading people out. If you and you know how what your numbers are, right? Like I bring a hundred people in that spits out one really, really good hire. But with this new system that you're talking about, you bring a hundred people in, you can actually interview 100 people and find out, does it have a similar amount? Yeah. Do my screening questions really filter out those people that aren't there? You know, oh, for sure. Let us be clapping for digital interviewing. Yeah. Using this type of technology really isn't even, you know, having the discussion, do I want to, you know, automate really isn't even an option. I mean, it's like, do you want to be competitive or not?  All the more reason to, you know, if you can have a piece of technology that's going to save you some hours of work. I mean, that's gold. And plus you get an outcome. You're just able to volume of work you're able to produce with the automation. One of the things that I tell a lot of people when I'm doing like demos, because they're like, oh my gosh, I'm, I'm sick of, you know, people not showing up for interviews and all of this stuff. The only reason a business owner is so upset that they're having these no shows is because they spent too much time setting up the interviews. Yep. Yep. When I have it all right. Yeah. Money is money. Time is money. But like when I have 10 interviews scheduled and only four or five show up, we clap for that win. That's a win. Yeah. It's a win. It doesn't matter because we did not spend time on those 10 interviews. Yes. Yes. So, you know, so that's the, that's what you have to think about it.  And not spending. You're wasting waste. It is a complete waste of your time. It's almost like an email marketing campaign and getting mad that every email wasn't opened and somebody purchased something. I mean, it really doesn't matter. You're, you know, sending out invitations to a lot of people and the ones that, that, that respond and interview is a win. Yep. Yeah. We are at the top of the hour. Are they're pretty close to it? Wow. Tom, I thank you. I thank you the link to. You did. ELC. So, yep. What do we got here, Liz? So this is an employee life cycle workshop. This is talking about hiring, onboarding, pay structure, orientation, training, reviews, all of the different things, the stages of your employees life cycle. Right. They, they get hired and then they're terminated. All of the pages in between. Do you have, and hopefully automated, right? Do you have automated systems in place for managing every single one of these things? And do you have your philosophy nailed down? Do you know what, what is your philosophy? What around the idea of promotions? Do you do promotions? How do you do them? In what way? Who gets promoted on what time, time frame or at what pay range? All of these things have a lot of decision points that need to be made. And this is where you're going to make them. So it's coming directly after Made Central because a lot of this stuff can be automated through Made Central and you can use the Central to do a lot of this stuff. But bottom line is you need to create this before you automate it. You would agree with that, right Dom? Before you automate anything, you have to make the decision about what it is that you are doing. So. You got to make sure the flow is good. The system is good. Absolutely. Absolutely. So. It's in Charleston. Yes. And it's at, it's actually at Castle Keepers. Same exact place that Made Central is doing their event. Ground zero for the residential cleaning industry. One last thing I wanted to say about Dom, what you were talking about. I think that a lot of times we forget that, yes, we think things are expensive. Oh, do we have Dom's? Oh yeah. You did put it up there already. Some people think that something's too expensive. I can't afford that. Just a reminder that the only, only, only, only non renewable resource is time. You can get more money. You can get more people. You can get more of everything. You cannot get more time. So look for, find, Linda, we were talking, right? Find ways of automating before you hire new people. Don't spend more time when you can automate. Yep. And when you're hiring for your support staff, your office staff, you're hiring people who can drive your tech stack as opposed to, you know, 10 years ago where you had people working in your office and you were kind of throwing some technology in there to help them. The tables of turn where your office staff is running your tech stack rather than the tech stack helping your office staff. This is good. And it is at the top of the hour. And Dom, I'm looking forward to seeing you in person next week. Yeah. I'll see you guys next week. Hopefully it'll be a little bit warmer. Yeah. Well, can't, can't be colder than here. So I shouldn't say that. Knock wood over here again. So yeah, I'll see you guys next week. I'm looking forward to it. Sounds good. Thanks everybody. And we're done for the week. Monday. I've got a guest on the, on the schedule. Is this, is, is he solid? Yeah. Yeah. Kurt Kirk is going to be here Monday. So it'll either be Kurt or John. Right. It'll be one of them. So it's going to be here Monday. That's right. Okay. We'll see you next week. Take care. Bye. Bye. Bye.