[{"data":1,"prerenderedAt":108},["ShallowReactive",2],{"tv-buzzword-wilderness":3,"tv-buzzword-wilderness-seasons":15,"tv-buzzword-wilderness-episodes":26},{"id":4,"title":5,"logo":6,"cover":7,"tile":8,"announcement_text":9,"description":10,"slug":11,"one_liner":12,"card_text":9,"status":13,"sort":14},"f592985a-aadd-4573-94da-7778b758d78a","Buzzword Wilderness","94324d0f-aa52-4f96-872f-eef5c2680010","5e6b3794-e870-4d95-8768-6809164e2a7b","702096c6-c4c2-48f3-9ec3-56539b1fd621",null,"Matt is a non-technical marketer. Since joining the Directus team, he’s been confused, bewildered, and betwixt by the terms and technology of the dev tooling ecosystem. In this series, Matt wanders into the wilderness to ponder these buzzwords and their meanings and origins. Are they real, or are they just marketing? Let's find out together. ","buzzword-wilderness","Matt asks are any of these terms real, or is it just marketing?","published",8,[16],{"year":17,"show":4,"number":18,"id":19,"episodes":20},"2024",37,"e09fe5f4-2319-48aa-b211-898b0b896829",[21,22,23,24,25],"bfa56eb0-8caa-4561-9bca-6899379e3f22","17b03db0-01cb-44ba-9fe3-927f39adac45","03ae6f72-5aee-4d8d-b924-7494c9fe947d","1bf494ec-1cae-4017-9231-81aa9f82cfe2","63108e0e-f091-4419-8086-3912f481aea5",[27,44,61,76,92],{"id":21,"slug":28,"vimeo_id":29,"description":30,"tile":31,"length":32,"resources":9,"people":9,"episode_number":33,"published":34,"title":35,"video_transcript_html":36,"video_transcript_text":37,"content":9,"seo":38,"status":13,"episode_people":39,"recommendations":41,"season":42},"wtf-is-a-dxp","941233406","Lately, it seems like DXPs, or digital experience platforms, are all anyone can talk about. But WTF are DXPs (other than a fancy acronym), and why should anyone care about them? Touch grass with Matt as he shares his POV on the origin, meaning, and application of DXPs.","d9230c33-76b6-44e4-a4ec-c8d50f890f04",6,1,"2024-04-30","WTF is a DXP? ","\u003Cp>Matt: Hey there. I'm Matt. I'm on the marketing team here at Directus. As somebody who's nontechnical and someone who's fairly new to the world of developer tooling and open source, I find myself completely lost when trying to learn, like, new terms, concepts, and a lot of the buzzwords that I've seen a lot lately. You have too.\u003C\u002Fp>\u003Cp>You know, things like DXP, CMS, DMS, BaaS, SAS, composability, mock. I mean, what does it all mean? And as a marketer saying this, is any of it real, or is it just marketing? So, having some discussions with folks in the same position I am, turns out I'm not the only one. So I figured why not film a new series on Directus TV discussing each term, its origin, application, and, to switch things up?\u003C\u002Fp>\u003Cp>I figured I'd touch grass, by filming out here in the in the woods of Virginia. This is real, not a green screen. Sometimes it does feel like you can get lost in the wilderness. First episode, we're discussing a fairly popular acronym I've seen a lot of recently, which is DXP. So in this episode, I wanna dive into WTF a DXP is.\u003C\u002Fp>\u003Cp>What is a DXP? So a DXP is shorthand for digital experience platform. A digital experience platform, or DXP, isn't just a tool. It's a suite of tools. So think of it as, something that's engineered to construct and manage and optimize digital experiences across a bunch of different channels, web, mobile, even in store.\u003C\u002Fp>\u003Cp>But what does that really mean when you get to the core of it for someone like you or me? So imagine you're using an app on your phone or you're browsing a website or you're interacting or kicking a malfunctioning digital kiosk, every smooth interaction, every personalized advertisement, every transition from one platform to another, that's the handiwork of a DXP. It's really about making your digital life as intuitive and enjoyable as possible. The goal is to cater your digital experience exactly to your preferences across every channel, which really isn't a bad thing. I would prefer to get things that I'm interested in as opposed to things I don't care about.\u003C\u002Fp>\u003Cp>So some examples of things in the suite that I mentioned of, like, tools. Obviously, content management system, sees what you sees what you buy or the things that you prefer and changes what you see to suit you better. Analytics tools, obviously, that kind of power everything and let the person know that's running it, what's working and what's not. CRM, where everything is kinda stored, as creepy as that is about you. And then marketing automation tools, you know, email, SMS, things like that.\u003C\u002Fp>\u003Cp>It's a lot like microservices in that, everything is kinda put together, but every touch is about providing you a great personalized experience. Origins of DXP. DXP. So why did DXPs even start? Well, back when the Internet was younger and more naive, websites were pretty simple just like a digital brochure.\u003C\u002Fp>\u003Cp>Shout out to my favorite childhood website from 1996, Space Jam. Still one of the best ever. But as technology evolved and our expectations grew, just having a static website wasn't enough. We wanted more interaction, more personalization, more more more more more, and that's where DXPs came from. They came into play as, like, kind of a beefed up version of the traditional CMS.\u003C\u002Fp>\u003Cp>They provide a rich interactive digital experience, kind of like going from a Nokia phone to a smartphone. Like, suddenly, there's so much more you can do. Real words real world scenario. So let's consider a real world scenario. A university using a DXP to manage its digital footprint.\u003C\u002Fp>\u003Cp>Right? The platform enables them to provide, personalized learning environments, student portals, community engagement platforms, everything across different devices. It enhances the student experience, but also simplifies the back end processes for administration. So imagine having a personalized dashboard that knows your study habits, it recommends resources based on your course load, and connects you with, you know, fellow students in your major. That's something that would be powered by a DXP.\u003C\u002Fp>\u003Cp>So benefits and drawbacks. The the advantages of a DXP are pretty clear. Right? They offer a smoother, more integrated user experience tailored to individual needs. They also allow organizations to manage all their digital stuff from one place, cut down on the chaos, keep things streamlined.\u003C\u002Fp>\u003Cp>But really, it's, as you can guess, like, very complex. It requires a significant investment in time and money. Plus, you need the right skills in your team to keep everything running smoothly, or you have to find an agency to run it for you, and we know those don't always work out. But, yeah. I mean, those are just some of the drawbacks of using a DXP.\u003C\u002Fp>\u003Cp>And, really, that's the lowdown of DXPs. They're powerful platforms designed to make digital experiences, like, really rich. So, hopefully, that was helpful for you. That's what I've learned so far. Obviously, I'm still learning, so I'll probably do another episode of this, once I learn more.\u003C\u002Fp>\u003Cp>But, yeah, hopefully, it was helpful. I appreciate you joining me out here in the woods in this 90 degree Fahrenheit weather. If I'm sweaty, I apologize, but I appreciate the time today. I'll see you next time.\u003C\u002Fp>","Hey there. I'm Matt. I'm on the marketing team here at Directus. As somebody who's nontechnical and someone who's fairly new to the world of developer tooling and open source, I find myself completely lost when trying to learn, like, new terms, concepts, and a lot of the buzzwords that I've seen a lot lately. You have too. You know, things like DXP, CMS, DMS, BaaS, SAS, composability, mock. I mean, what does it all mean? And as a marketer saying this, is any of it real, or is it just marketing? So, having some discussions with folks in the same position I am, turns out I'm not the only one. So I figured why not film a new series on Directus TV discussing each term, its origin, application, and, to switch things up? I figured I'd touch grass, by filming out here in the in the woods of Virginia. This is real, not a green screen. Sometimes it does feel like you can get lost in the wilderness. First episode, we're discussing a fairly popular acronym I've seen a lot of recently, which is DXP. So in this episode, I wanna dive into WTF a DXP is. What is a DXP? So a DXP is shorthand for digital experience platform. A digital experience platform, or DXP, isn't just a tool. It's a suite of tools. So think of it as, something that's engineered to construct and manage and optimize digital experiences across a bunch of different channels, web, mobile, even in store. But what does that really mean when you get to the core of it for someone like you or me? So imagine you're using an app on your phone or you're browsing a website or you're interacting or kicking a malfunctioning digital kiosk, every smooth interaction, every personalized advertisement, every transition from one platform to another, that's the handiwork of a DXP. It's really about making your digital life as intuitive and enjoyable as possible. The goal is to cater your digital experience exactly to your preferences across every channel, which really isn't a bad thing. I would prefer to get things that I'm interested in as opposed to things I don't care about. So some examples of things in the suite that I mentioned of, like, tools. Obviously, content management system, sees what you sees what you buy or the things that you prefer and changes what you see to suit you better. Analytics tools, obviously, that kind of power everything and let the person know that's running it, what's working and what's not. CRM, where everything is kinda stored, as creepy as that is about you. And then marketing automation tools, you know, email, SMS, things like that. It's a lot like microservices in that, everything is kinda put together, but every touch is about providing you a great personalized experience. Origins of DXP. DXP. So why did DXPs even start? Well, back when the Internet was younger and more naive, websites were pretty simple just like a digital brochure. Shout out to my favorite childhood website from 1996, Space Jam. Still one of the best ever. But as technology evolved and our expectations grew, just having a static website wasn't enough. We wanted more interaction, more personalization, more more more more more, and that's where DXPs came from. They came into play as, like, kind of a beefed up version of the traditional CMS. They provide a rich interactive digital experience, kind of like going from a Nokia phone to a smartphone. Like, suddenly, there's so much more you can do. Real words real world scenario. So let's consider a real world scenario. A university using a DXP to manage its digital footprint. Right? The platform enables them to provide, personalized learning environments, student portals, community engagement platforms, everything across different devices. It enhances the student experience, but also simplifies the back end processes for administration. So imagine having a personalized dashboard that knows your study habits, it recommends resources based on your course load, and connects you with, you know, fellow students in your major. That's something that would be powered by a DXP. So benefits and drawbacks. The the advantages of a DXP are pretty clear. Right? They offer a smoother, more integrated user experience tailored to individual needs. They also allow organizations to manage all their digital stuff from one place, cut down on the chaos, keep things streamlined. But really, it's, as you can guess, like, very complex. It requires a significant investment in time and money. Plus, you need the right skills in your team to keep everything running smoothly, or you have to find an agency to run it for you, and we know those don't always work out. But, yeah. I mean, those are just some of the drawbacks of using a DXP. And, really, that's the lowdown of DXPs. They're powerful platforms designed to make digital experiences, like, really rich. So, hopefully, that was helpful for you. That's what I've learned so far. Obviously, I'm still learning, so I'll probably do another episode of this, once I learn more. But, yeah, hopefully, it was helpful. I appreciate you joining me out here in the woods in this 90 degree Fahrenheit weather. If I'm sweaty, I apologize, but I appreciate the time today. I'll see you next time.","92aee796-fd09-416d-a679-f76e40a88b7b",[40],"d6068dca-119d-46f9-a0ce-2f87b2f624f6",[],{"year":17,"show":4,"number":18,"id":19,"episodes":43},[21,22,23,24,25],{"id":22,"slug":45,"vimeo_id":46,"description":47,"tile":48,"length":49,"resources":9,"people":9,"episode_number":50,"published":51,"title":52,"video_transcript_html":53,"video_transcript_text":54,"content":9,"seo":55,"status":13,"episode_people":56,"recommendations":58,"season":59},"wtf-is-a-cms","941314616","Is content data? Or is data content? And is a content management system really just a data management system? In this episode, Matt muses over what a CMS is, what a DMS is, and if there's a difference. ","15259da8-70f0-458e-8d42-f922adf68b93",3,2,"2024-05-14","WTF is a CMS","\u003Cp>Speaker 0: Hey, everybody. Welcome back to another episode of buzzword wilderness. I'm Matt here to guide you through the tech jungle of buzzwords. Today, we're gonna explore a common confusion that I've run into in the digital world, which is the difference between a CMS and a DMS, and discussing what headless really means in the context of both. So why do we even separate these terms, when at the end of the day, it's all just data?\u003C\u002Fp>\u003Cp>Don't know. Let's dive in. What is a CMS? So a Content Management System, or CMS, is all about creating, managing, and displaying content. And although there's some technical overhead upfront, it's designed for ease of use for the end user, even if you're not tech savvy.\u003C\u002Fp>\u003Cp>You've probably heard of platforms like WordPress or Drupal. Those are the classic examples of CMSs. In a headless CMS, the content, text, images, videos is all stored without a fixed front end system. So this means it can be displayed across various platforms via an API. It's like a storage box for your content, and then you decide where and and how to display it.\u003C\u002Fp>\u003Cp>What is a DMS? So a data management system, or DMS, is broader. It handles all kinds of data, be it customer information, transaction records, or operational metrics. It's not just about data and display, but about efficiently storing and using that data. With headless data, the head or the user interface is separate from the body, which is the data storage and logic.\u003C\u002Fp>\u003Cp>This data can be accessed and and used across different applications, whether it's a web app or a mobile app or even IoT devices. So CMS versus DMS, why the distinction between the 2? While both might seem similar since they manage data, the focus is actually different. The CMS is all about content and how it engages your users. It's really front end friendly.\u003C\u002Fp>\u003Cp>A DMS is about the efficient, versatile use of data at the back end. You might not see it directly, but it powers every system you use every day. Consider a retail brand, for instance. They use a CMS to manage and update their website's product descriptions and images. Simultaneously, they use a DMS to handle inventory data, customer transactions, and analytics, the data that helps them make strategic decisions.\u003C\u002Fp>\u003Cp>So a CMS and a DMS serve distinct purposes, but ultimately, they both handle data just in different ways. Hopefully, that was a help, helpful little reminder about the difference between the two. I appreciate you tuning in, and I'll see you on the next episode.\u003C\u002Fp>","Hey, everybody. Welcome back to another episode of buzzword wilderness. I'm Matt here to guide you through the tech jungle of buzzwords. Today, we're gonna explore a common confusion that I've run into in the digital world, which is the difference between a CMS and a DMS, and discussing what headless really means in the context of both. So why do we even separate these terms, when at the end of the day, it's all just data? Don't know. Let's dive in. What is a CMS? So a Content Management System, or CMS, is all about creating, managing, and displaying content. And although there's some technical overhead upfront, it's designed for ease of use for the end user, even if you're not tech savvy. You've probably heard of platforms like WordPress or Drupal. Those are the classic examples of CMSs. In a headless CMS, the content, text, images, videos is all stored without a fixed front end system. So this means it can be displayed across various platforms via an API. It's like a storage box for your content, and then you decide where and and how to display it. What is a DMS? So a data management system, or DMS, is broader. It handles all kinds of data, be it customer information, transaction records, or operational metrics. It's not just about data and display, but about efficiently storing and using that data. With headless data, the head or the user interface is separate from the body, which is the data storage and logic. This data can be accessed and and used across different applications, whether it's a web app or a mobile app or even IoT devices. So CMS versus DMS, why the distinction between the 2? While both might seem similar since they manage data, the focus is actually different. The CMS is all about content and how it engages your users. It's really front end friendly. A DMS is about the efficient, versatile use of data at the back end. You might not see it directly, but it powers every system you use every day. Consider a retail brand, for instance. They use a CMS to manage and update their website's product descriptions and images. Simultaneously, they use a DMS to handle inventory data, customer transactions, and analytics, the data that helps them make strategic decisions. So a CMS and a DMS serve distinct purposes, but ultimately, they both handle data just in different ways. Hopefully, that was a help, helpful little reminder about the difference between the two. I appreciate you tuning in, and I'll see you on the next episode.","6f978e06-2e4a-4404-a9e3-0697495e2200",[57],"1b68760e-b1e6-455e-b427-cd5504243f63",[],{"year":17,"show":4,"number":18,"id":19,"episodes":60},[21,22,23,24,25],{"id":23,"slug":62,"vimeo_id":63,"description":64,"tile":65,"length":49,"resources":9,"people":9,"episode_number":49,"published":66,"title":67,"video_transcript_html":68,"video_transcript_text":69,"content":9,"seo":70,"status":13,"episode_people":71,"recommendations":73,"season":74},"wtf-is-saas","941313485","BaaS and SaaS sound a lot alike, but in practice they're entirely different. In this episode, Matt breaks down the difference between these two similar terms and offers a high-level look at both. ","82479abe-8c8c-4df9-8a13-0757be4421b3","2024-05-28","WTF is SaaS?","\u003Cp>Speaker 0: Hey there, and welcome back to another episode of Buzzword Wilderness. I'm Matt, navigating you through the forest that is Tech Terms. In this episode, we're breaking down 2 often confused terms in the Cloud world, which is BaaS and SaaS. This is not gonna be good for my list, but we're gonna try it anyways. So what is a BaaS?\u003C\u002Fp>\u003Cp>A BaaS or Backend as a Service simplifies app and website development by managing a lot of the back end operations through cloud services. It allows developers to really concentrate and focus on the fun parts, which are the user facing parts, the UX of the UI of the website or app, the front end. Some of the services managed by BaaS providers include, like, databases, cloud storage, and server management. Some of the best functionality you'll find is is user authentication, data management, and push notifications, or or things like that. What is SaaS?\u003C\u002Fp>\u003Cp>So SaaS is software as a service. It's essentially like renting out, software through the Internet. It's usually like a monthly fee for a SaaS tool or something along those lines. It's universally accessible from most any device, or it should be, with an Internet connection. Common use cases are email services, CRM systems, document creation tools, really any tool you find is probably a SaaS.\u003C\u002Fp>\u003Cp>Major providers like Google Workspace, Sales Salesforce, Microsoft Office, those are comprehensive software solutions. There's a lot of smaller ones, though. BaaS versus SaaS. So why the distinction? While both SaaS and BaaS streamline cloud service processes, they cater to different needs.\u003C\u002Fp>\u003Cp>So a BaaS is akin to delivering the ingredients and tools needed for developers to build applications. And a SaaS is a ready to consume software meal, handling all the back end, maintenance and updates. So if we're in this forest. Right? A BaaS is all of the tools and materials you need to build your own cabin, Whereas, SAS is one you find on Airbnb and you rent a fully equipped cabin.\u003C\u002Fp>\u003Cp>Probably way more expensive in the long run, but it gives you everything you need much faster. So understanding BaaS and SaaS helps demystify class you know, how you're using software in your organization. This was a short but sweet episode. I look forward to seeing you again on the next episode. Appreciate your time.\u003C\u002Fp>","Hey there, and welcome back to another episode of Buzzword Wilderness. I'm Matt, navigating you through the forest that is Tech Terms. In this episode, we're breaking down 2 often confused terms in the Cloud world, which is BaaS and SaaS. This is not gonna be good for my list, but we're gonna try it anyways. So what is a BaaS? A BaaS or Backend as a Service simplifies app and website development by managing a lot of the back end operations through cloud services. It allows developers to really concentrate and focus on the fun parts, which are the user facing parts, the UX of the UI of the website or app, the front end. Some of the services managed by BaaS providers include, like, databases, cloud storage, and server management. Some of the best functionality you'll find is is user authentication, data management, and push notifications, or or things like that. What is SaaS? So SaaS is software as a service. It's essentially like renting out, software through the Internet. It's usually like a monthly fee for a SaaS tool or something along those lines. It's universally accessible from most any device, or it should be, with an Internet connection. Common use cases are email services, CRM systems, document creation tools, really any tool you find is probably a SaaS. Major providers like Google Workspace, Sales Salesforce, Microsoft Office, those are comprehensive software solutions. There's a lot of smaller ones, though. BaaS versus SaaS. So why the distinction? While both SaaS and BaaS streamline cloud service processes, they cater to different needs. So a BaaS is akin to delivering the ingredients and tools needed for developers to build applications. And a SaaS is a ready to consume software meal, handling all the back end, maintenance and updates. So if we're in this forest. Right? A BaaS is all of the tools and materials you need to build your own cabin, Whereas, SAS is one you find on Airbnb and you rent a fully equipped cabin. Probably way more expensive in the long run, but it gives you everything you need much faster. So understanding BaaS and SaaS helps demystify class you know, how you're using software in your organization. This was a short but sweet episode. I look forward to seeing you again on the next episode. Appreciate your time.","760d8590-1637-410b-a84f-7ac518686bee",[72],"fd96ee76-d322-483c-8ac5-9d3d1202371e",[],{"year":17,"show":4,"number":18,"id":19,"episodes":75},[21,22,23,24,25],{"id":24,"slug":77,"vimeo_id":78,"description":79,"tile":80,"length":49,"resources":9,"people":9,"episode_number":81,"published":82,"title":83,"video_transcript_html":84,"video_transcript_text":85,"content":9,"seo":86,"status":13,"episode_people":87,"recommendations":89,"season":90},"wtf-is-composable","941313811","These days, it's nearly impossible to avoid the term \"composable.\" But what does it actually mean in the context of development? ","63050d36-c141-4876-b085-7c4fc19f7816",4,"2024-06-11","WTF is Composable?","\u003Cp>Speaker 0: Hello, and welcome back to another episode of Buzzword Wilderness. I'm Matt. And today, we're tackling a term that you have probably heard of, which is composable. It's a term, it's an approach, it's a philosophy. It's really changing the game in how we build and and talk about digital platforms.\u003C\u002Fp>\u003Cp>It, emphasizes adaptability and flexibility. So let's dive in. What is composable? So composable technology is all about building systems that are flexible and easy to adjust. The systems are are made up of different parts that can be combined in different ways or swapped out, really depends on on the demands you have and how those change.\u003C\u002Fp>\u003Cp>Change. Imagine this is like LEGOs. Each block is a piece of your technology setup, whether it's for storing data, managing content, or anything else. You can rearrange these blocks to fit your needs or teams, whether you're scaling up or shifting focus. Application and technology.\u003C\u002Fp>\u003Cp>So composable architecture really helps businesses stay agile. Instead of replacing an entire system when needs change, you can simply change parts of it. It's like changing the tires instead of buying a whole new car. For developers, especially, this means more freedom. They can choose the best tools for specific tasks without being locked into one system or vendor, and you can customize it exactly like your team needs the back end.\u003C\u002Fp>\u003Cp>A few episodes ago, we talked about digital experience platforms. DXPs traditionally came as one complete package, hard to modify if your needs change, but now a lot of them are embracing these composable principles. Thinking like a smartphone. Right? The older models came fixed with apps you couldn't change.\u003C\u002Fp>\u003Cp>The Apple iPhone came out and completely changed the game. Get the apps you want, the apps you need, for that moment. Download them. Delete them. Do whatever you want.\u003C\u002Fp>\u003Cp>It's completely flexible all just from one base device. So I don't think composable technology is really just another trend or buzzword. It's a new way of thinking about how to structure the back end of your business. You'll see a lot of this in the coming years. I think, as a lot more enterprises start to adopt it in, the terminology is just starting to take off.\u003C\u002Fp>\u003Cp>So I appreciate you sticking with me as always, and I hope this explanation clears up some of the fog around composable. I look forward to seeing you again on the next episode. I appreciate your time.\u003C\u002Fp>","Hello, and welcome back to another episode of Buzzword Wilderness. I'm Matt. And today, we're tackling a term that you have probably heard of, which is composable. It's a term, it's an approach, it's a philosophy. It's really changing the game in how we build and and talk about digital platforms. It, emphasizes adaptability and flexibility. So let's dive in. What is composable? So composable technology is all about building systems that are flexible and easy to adjust. The systems are are made up of different parts that can be combined in different ways or swapped out, really depends on on the demands you have and how those change. Change. Imagine this is like LEGOs. Each block is a piece of your technology setup, whether it's for storing data, managing content, or anything else. You can rearrange these blocks to fit your needs or teams, whether you're scaling up or shifting focus. Application and technology. So composable architecture really helps businesses stay agile. Instead of replacing an entire system when needs change, you can simply change parts of it. It's like changing the tires instead of buying a whole new car. For developers, especially, this means more freedom. They can choose the best tools for specific tasks without being locked into one system or vendor, and you can customize it exactly like your team needs the back end. A few episodes ago, we talked about digital experience platforms. DXPs traditionally came as one complete package, hard to modify if your needs change, but now a lot of them are embracing these composable principles. Thinking like a smartphone. Right? The older models came fixed with apps you couldn't change. The Apple iPhone came out and completely changed the game. Get the apps you want, the apps you need, for that moment. Download them. Delete them. Do whatever you want. It's completely flexible all just from one base device. So I don't think composable technology is really just another trend or buzzword. It's a new way of thinking about how to structure the back end of your business. You'll see a lot of this in the coming years. I think, as a lot more enterprises start to adopt it in, the terminology is just starting to take off. So I appreciate you sticking with me as always, and I hope this explanation clears up some of the fog around composable. I look forward to seeing you again on the next episode. I appreciate your time.","810221b9-e030-494b-adf1-f132251bb1c8",[88],"f1ed5596-6ed0-42bb-856b-b074252cf580",[],{"year":17,"show":4,"number":18,"id":19,"episodes":91},[21,22,23,24,25],{"id":25,"slug":93,"vimeo_id":94,"description":95,"tile":96,"length":81,"resources":9,"people":9,"episode_number":97,"published":98,"title":99,"video_transcript_html":100,"video_transcript_text":101,"content":9,"seo":102,"status":13,"episode_people":103,"recommendations":105,"season":106},"wtf-is-mach","941314137","The term Jamstack has been floating around for the past few years, but a new term is starting to make the rounds. Join Matt as he explores MACH, and how it compares to Jamstack. ","7c248c06-500e-4466-8cf2-4c579954f55f",5,"2024-06-25","WTF is MACH?","\u003Cp>Speaker 0: Everybody. Welcome back to another episode of Buzzword Wilderness. I'm Matt. And today, we're looking at 2 very important tech architectures you've probably heard of, which are Mach and Jamstack. We'll talk about the different frameworks, how they shape the future of digital experiences, their unique features, and how you can pick the right one based on what you need at the moment.\u003C\u002Fp>\u003Cp>So what is mock? Mock technology is a way to build, platforms that are agile, flexible, and scalable. And, actually, each part of the mock acronym stands for a modern best practice in software development. So the m stands for microservices, which is splitting into smaller separate services instead of a big monolith. The a stands for API first.\u003C\u002Fp>\u003Cp>Make sure all the APIs are a top priority when you're designing something or or building something from from the ground up. The c stands for cloud native. So applications are created to take full advantage of the cloud so they can easily scale up and are resilient. And then h stands for headless, which separates the front end from the back end, allowing different front end tools to be used without, you know, back end limitations being all kind of bundled together. So what is Jamstack?\u003C\u002Fp>\u003Cp>Jamstack stands for JavaScript J, APIs a, and markup m. It's a way to build websites, to be more fast, secure, and easier to scale. So JavaScript of that, you can manage dynamic features and user interactions. APIs, server side tasks are simplified into reusable APIs. And then markup created in advance during the build time, it boosts the speed and security by delivering static files.\u003C\u002Fp>\u003Cp>So comparing mock and jamstack. As you can probably guess, both mock and Jamstack obviously use APIs to make services more flexible and independent, but they serve different purposes. So think of mock being designed for creating dynamic scalable applications that work across different platforms. And Jamstack, on the other hand, really hones in on the web development process to make sites faster and more secure with pre rendered content. Mock offers more flexibility with a modular setup, while Jamstack is really good for websites that need high performance and strong security, thanks to use of the static content.\u003C\u002Fp>\u003Cp>So mock and Jamstack offer different ways to create efficient, modern, and strong digital experiences. Choosing between them depends on on exactly what you need, whether you need a complete digital overhaul of your back end infrastructure, for applications, or if you just need a more streamlined web development process. You can't go wrong with either one. Both are really gaining popularity. Jamstack, in particular, has been around for a while.\u003C\u002Fp>\u003Cp>Mock is a little bit of a newer term. So, hopefully, this helped you kinda navigate the forest of of buzzwords on mock and jamstack. I really appreciate you spending time with me out here in the woods of Virginia in 90 degree Fahrenheit, heat. Can't wait for the next episode, and I appreciate the time.\u003C\u002Fp>","Everybody. Welcome back to another episode of Buzzword Wilderness. I'm Matt. And today, we're looking at 2 very important tech architectures you've probably heard of, which are Mach and Jamstack. We'll talk about the different frameworks, how they shape the future of digital experiences, their unique features, and how you can pick the right one based on what you need at the moment. So what is mock? Mock technology is a way to build, platforms that are agile, flexible, and scalable. And, actually, each part of the mock acronym stands for a modern best practice in software development. So the m stands for microservices, which is splitting into smaller separate services instead of a big monolith. The a stands for API first. Make sure all the APIs are a top priority when you're designing something or or building something from from the ground up. The c stands for cloud native. So applications are created to take full advantage of the cloud so they can easily scale up and are resilient. And then h stands for headless, which separates the front end from the back end, allowing different front end tools to be used without, you know, back end limitations being all kind of bundled together. So what is Jamstack? Jamstack stands for JavaScript J, APIs a, and markup m. It's a way to build websites, to be more fast, secure, and easier to scale. So JavaScript of that, you can manage dynamic features and user interactions. APIs, server side tasks are simplified into reusable APIs. And then markup created in advance during the build time, it boosts the speed and security by delivering static files. So comparing mock and jamstack. As you can probably guess, both mock and Jamstack obviously use APIs to make services more flexible and independent, but they serve different purposes. So think of mock being designed for creating dynamic scalable applications that work across different platforms. And Jamstack, on the other hand, really hones in on the web development process to make sites faster and more secure with pre rendered content. Mock offers more flexibility with a modular setup, while Jamstack is really good for websites that need high performance and strong security, thanks to use of the static content. So mock and Jamstack offer different ways to create efficient, modern, and strong digital experiences. Choosing between them depends on on exactly what you need, whether you need a complete digital overhaul of your back end infrastructure, for applications, or if you just need a more streamlined web development process. You can't go wrong with either one. Both are really gaining popularity. Jamstack, in particular, has been around for a while. Mock is a little bit of a newer term. So, hopefully, this helped you kinda navigate the forest of of buzzwords on mock and jamstack. I really appreciate you spending time with me out here in the woods of Virginia in 90 degree Fahrenheit, heat. Can't wait for the next episode, and I appreciate the time.","23e9413b-0c1c-4cd0-aaa3-433ee7b05a79",[104],"02fa84b4-65cf-448c-a944-86e962a60681",[],{"year":17,"show":4,"number":18,"id":19,"episodes":107},[21,22,23,24,25],1784728835818]