Commercetools Training: Composable Commerce Functional Architect Transcript PDF

Speaker 2 | 00:00 Hello and got meced up with us as well. Hello. Mehtap Parkinson | 00:06 Hi everyone. Speaker 2 | 00:15 And that's Artur where you go. Artur is with us as well. Hi hello there and more people coming and that's good. Yeah, it's right on time. Hello Suzanna. And Lela is with us as wel...

Speaker 2 | 00:00 Hello and got meced up with us as well. Hello. Mehtap Parkinson | 00:06 Hi everyone. Speaker 2 | 00:15 And that's Artur where you go. Artur is with us as well. Hi hello there and more people coming and that's good. Yeah, it's right on time. Hello Suzanna. And Lela is with us as well. Hell, Lela are right still waiting for Max Patck and hopefully two more people from Commercetools that will join us. But thank you all for coming. I think most of you were here on Friday. Yeah, except met Hub, but that's fine. You didn't miss match, just some technical stuff. We'll do that here as well. We got Patrick coming in. Hello at it. Patrick, can you hear me? Okay, I Patrick is sorting out his audio situation and looks like amogmola. Sorry, I might be mispronouncing that. I apologize if you can correct me. Speaker 3 | 01:52 Yeah, it's Amogmola. Speaker 2 | 01:54 Amogmola. Very nice to meet you welcome. Speaker 4 | 01:57 Thank you. Speaker 2 | 02:03 Okay we got Adrien joining us Parick has video does he have audio? That's the question yes. Okay, there we go. Hello, Adrien. Adrien disappeared. Hopefully he will come back and Max, so that's assuming Advian comes back. There is, we'll have full house everyone. Hello and there we go, all good connection wise. We lost you there for a second. No, now you're fine. When you came up originally you disappeared for a bit and now you're back. So. Speaker 5 | 02:50 Yeah, I went out to grant Audi access for a while. Speaker 2 | 02:56 Alrighty, awesome. So looks like this is everyone. Welcome. Welcome everyone to this Commercetools Functional Architect training most of you met. Met me on the warm up session on Friday. But we have some new faces here as well, so we're going to start off with quick introductions. So a bit of a shorter version than what we did on Friday, just so we all know how to pronounce each other's names and who we're going to spend the next three days with. I'll get started and then I will call you out in whatever order. I have you here on my list. And if you could just tell us you know how to pronounce your name. How do you prefer to be addressed? What it is? Which company you're representing, what it is you do. And as a little iceworm icebreaker. We're gonna be talking about food quite a bit in this training cause that's gonna be kind of the use case we'll be dealing with. So if everyone could say what's their favorite snack? That will be fun. So starting with myself, my name is Marius Nas. I am a senior technical trainer here in camera stores. I've been with Commercetools for almost two years now, and but I've been a technical trainer for, like, this is my 13th year on this job in different companies. And I guess my favorite snack. I'm Polish. So I'm gonna go stereotypical. I'm gonna say pierogi is my favorite snack. So that's me. And let's move on to the first person on my list, which is Antonina. Speaker 6 | 04:28 Hi, Hol, I'm Antonina. I'm from Italy. I work for Reply and consultant company in Italy, and my role is a business analyst. So the main objective from my perspective is to understand how to, propose Commercetools Tool as a possible solution for a different company. And my favorite snack is a pizza. Speaker 2 | 04:57 There you go, stereotypical Italian, I guess. No pizza is always a good answer across the globe, so it doesn't matter what the question is, pizza is a good answer. Very good, Antonina. Thank you so much. Speaker 6 | 05:12 Thank you. Speaker 2 | 05:13 Graty Miller now we got Lela. Speaker 7 | 05:18 Hi everyone, my name's Lela. I'm an associate software developer for Commercetools Tools. I'm relatively new to the company, so I've joined this course to sort of just get to know the product a little bit more. From this perspective, I don't really snack, but when I do, I usually choose protein bars. Kind of healthy, but it has chocolate, so I. Speaker 2 | 05:41 Like my balance. Yeah, thanks, yeah, thank you. Yeah, protein bars, less guilt because like, well, it says it's healthy, so very good. Thank you so much. Lega Bob. Speaker 8 | 05:55 You' next I my name is Bob, I work for Skippus. We have an e commerce web shop in about twelve countries. We are going to implement commerce tools in the next six months or so, and I'm the product own of the e commerce environment. My favorite snack I can gets spicy Dorritos. The chips nice. Speaker 2 | 06:31 Awesome. Thank you so much, Bob. And your colleague Max is next. Speaker 4 | 06:36 Yeah, my name is Max, a colleague of Bob. I'm the functional analyst at the Shippers group. I'm responsible for and during the implementation, working out all the functions and assisting it in the business side of the implementation. Mehtap Parkinson | 06:48 The. Speaker 4 | 06:54 And my favorite snack are doughnuts. Speaker 2 | 06:57 Nice, awesome, all good choices so far. Nice. At least the ones I agree with. All of them. Thank you, Max. Next one is Mecta. Mehtap Parkinson | 07:09 Hi everyone. I'm made from Turkey, but based in Barcelona. I'm an associate software en engineer at the connecting in commercials and my favorite snack is cinnamon rolls. Speaker 2 | 07:23 Nice. See, I could really use you on a developer training because that's where we talk a lot more about Connect, but we're going to talk about it a little bit here as well. So nice to have you here as support. Thank you maced up. Next one is Artur and Hide together. I'm author or author from a city spent consulting working as a consultant and my favorite snack would be nachoed with cheese saucer. Awesome. Thank you so much. After. Short and sweet or I guess spicy with the nachos. Next one is your colleague Patrick. Speaker 8 | 08:02 Yeah, I'm Patrick. Speaker 2 | 08:03 Colleague of Artur working at Mercedes Benz Consulting and I'm consulting e commerce, and my favorite snack or is probably pizza. Nice. Thank you so much, Patrick. Next one is another one of my colleagues and fellow Paul Suzanna. Speaker 3 | 08:26 So I have one Suzanna from Poland, but based in Berlin. I joined as Associate Software Engineer in Commercetools Tools in November, and my favorite snack is If I want to be healthy fruit and not healthy chocolate. Speaker 2 | 08:45 Or you can have fruit with chocolate. And there you go, you can have it both ways or a protein bar, there you go they sometimes have fruit inside as well. Awesome, thank you, Somm Suzanna. And next one, sorry, I'm learning this one. Ammogo, Amogmola, sorry, but that's a new name. I haven't heard that one before. Speaker 3 | 09:07 Yeah, it's fine. So I'm. Mehtap Parkinson | 09:08 So you can work with any cons as I can FS Davis an artists and bet and as the yous and everything was like so it so this year un experience is to be delivered to co. Speaker 3 | 09:08 I'm a Gomer from Berlin. I work for Commercetools as a junior software engineer and my favorite snack is, caramelized almonds. I didn't like them. Speaker 2 | 09:22 Yeah, I don't think I had those, but sound they sound awesome. So yeah, nice, very good suggestion. Thank you. And but not least, another commerce stoler. Adrien. Speaker 5 | 09:37 Hey, hello everyone, I'm Adrien. I'm from Valencia and joining the cult from Valencia today. I was living in Berlin for nine years and just moved to Valencia and was very happy to find that Commercials has an office in here. I am Senior UX Design UX Y Designer in the Prices team, so we take care of prices and discounts mostly. I joined the company in January in early January. So I'm very new to the company, but I really started with some topics and they went to the office ready to get to know some people. And my favorite snack are the, peanuts covered in paprika around. Speaker 2 | 10:24 Nice. Speaker 5 | 10:25 What? I mean the orange onesmm awesome. Speaker 2 | 10:30 Thank you so much, Adrien. And yeah, we got actually quite a few people interested in pricing and discounts in this training, so I might need your backup as well on that topic. Mehtap Parkinson | 10:32 For people interested in pricing discounts and describing. So is that nice. Speaker 2 | 10:38 So I see. Awesome. Welcome everyone. Thank you all for these introductions. So let's just maybe share the welcome slide. Make sure that my screen sharing is working. Once again, thank you to those of you who were here on Friday, those of you who haven't. Don't worry. Like I said, it's an optional meeting, but basically it made sure that we will spend less time on solving people's technical issues and more time on actual training content, so that's always good, right? Mehtap Parkinson | 11:00 And what basically make sure that was finalized time and so people that was a good time to break up that. So and that's always good TOS what is the discovering today this line it's this one we can one confirm that paper can be on some counts if you can see the slide. Speaker 2 | 11:12 Where is my screen today with the slide? It's this one. ALR can everyone confirm that give me a thumbs up on camera or something that you can see the slide? Alrighty, awesome. All right, before we get started with the actual content, just a few ground rules of the training, just so we are all aware. So first of all, cameras. I would really appreciate if you keep the cameras on throughout the training. This just makes it a bit more, you know, personal. Makes me feel like I'm talking to people. But I can read the room a little bit better. I can see when you're happy and not happy with what I'm telling you. Mehtap Parkinson | 11:51 And see what you're telling me? What' telling you if you jokes like maybe if you just stop with the jokes and if you're confused by the see this just and next the fee. Speaker 2 | 11:54 If my jokes. Land. Or maybe I should just stop with the jokes and all of that if you're confused by the topic we're talking about. So this just makes the feedback easier. When I'm asking you a quick question like, Hey, can everyone see the slide? Mehtap Parkinson | 12:04 So it is you want to but it's like everyone's seen as you one sounds like it's always st like me out is down go back in this line that. Speaker 2 | 12:07 You know, you can give me a quick thumbs up on camera. That's always the fastest way to let me know that everything's okay or something's not okay. You can give a little wave or something like slow down. Go back to the previous slide that catches my attention as well. Whenever you have a question, feel free to ask it. So I won't be doing any specific Q&A rounds, or if I will, it will be me asking new questions, not the other way around. Mehtap Parkinson | 12:31 Question. Speaker 2 | 12:32 So whenever you have any questions, just un mut yourself, you can interrupt me mid sentence. It's absolutely fine. I will not be offended or nothing like that. It's all good. If you don't feel comfortable interrupting me, you can raise your hand in the zoom in the toolbar. You should have like, a little. I think it's a little emog icon or something. For me as the host, it's always somewhere else, but if anyone could like do the race hand thing just as a little demo for the group. There we go. Thank you Lela, for demonstrating. So we can use that as well. And I will not that you have a question. And I will address that when I finish my thought. So that's it, what else? Yeah, maybe one more thing about the cameras. So like I said, great, there you go, Audi. And that works as well if when you're celebrating, that's awesome. So one more thing about the cameras. Obviously, you might have a situation where, I don't know, there's someone at the door, someone's walking into your room, maybe your cat, maybe your child, maybe, you know, your spouse, whatever. Maybe you want to have a quick snack. Then, of course, you can turn off the camera for a few moments until you resolve that situation. Mehtap Parkinson | 13:45 Resolve that situation during the training. Speaker 2 | 13:46 You don't want people to see you eat or something like that. That is all good as well. So eating during the training is okay, although a bit risky because I might ask you a question and you might have a full mouth, but that's a risk you have to take when you're hungry sometimes, I guess. All right, this is our agenda for the next three days. So day one. Unfortunately, it's a lot of me talking because, you know, I'm introducing you to this whole new world of commerce tools. Mehtap Parkinson | 14:12 Introducing it to the strong are strong to explain some stuffer cor mean. Speaker 2 | 14:14 Obviously, you have to explain some stuff. There's kind of no going around that. So we're going to start with introductions to Commercetools as a product. Introduction to the Merchant Center. What is the Merchant Center? Well, that's exactly why we have this session. Mehtap Parkinson | 14:28 That's exactly what we have the subject statement if we here for you. Speaker 2 | 14:30 The most important information here for you is that we will have two breaks. Mehtap Parkinson | 14:33 I think we will have two breaks. Speaker 2 | 14:34 Each of them will be exactly 15min. Mehtap Parkinson | 14:35 Will be exactly. 15 minutes. Speaker 2 | 14:36 There will be a timer on the screen, so I won't lie to you, it's going to be exactly 15min. Mehtap Parkinson | 14:36 And SOS. Speaker 2 | 14:42 And each break we will do after about an hour. 15min hour and a half ish. You know, depending where we are, obviously, if we are in the middle of an exercise or something like that, then, you know, we're going to finish that and then take the break. So give or take. AY there will be exercises. So some hands on exercises that she will be doing. Those will be done in groups, so don't worry that she will be on the spot. We have, I think, eleven people here, so I will divide you up in probably three teams so one team will have a numbers advantage. But I will mix the themes up every time or every now and again, so you'll get to work with different people. Mehtap Parkinson | 15:22 For so. For people. Speaker 2 | 15:24 And there will be quizzes throughout the training. So after we finish each, you know, each topic like this is a block here, there will be a quiz that you will have to do. Everyone does the quiz. This is mostly for you to see how well you understood the topic and if you feel that maybe some more time should be spent on it. You do not need to pass all the quizzes to pass this training. To pass this training. You need to be here for three days. And listen to me. Talk, that's punishment enough. That's all you have to do to pass this training, so don't worry if you don't do great. And quizzes, I mean, that just means, you know, maybe some more time should be spent on certain topics. Maybe I did a bad job explaining them. That's good feedback for me as well. But don't stress about the quizzes. You're going to pass the training if you're here for the and participate, that's all you have to do to successfully complete it. Mehtap Parkinson | 16:18 That's all you have to do to successfully the organizational aspects training before it started. Speaker 2 | 16:22 Any questions about the organizational aspects of the training before we get started? Alright, the final thing, like I mentioned, I'm Polish and I, you know, English is not my first language. And I think for most of us here, that's the same situation. So if I am speaking too fast, if I am not easy to understand because of my accent or something like that, it's fine to, you know, tell me to slow down, maybe repeat something. I'm going to try to speak as clear as I can, but obviously, you know the best way to slow me down is by asking me questions. If you don't ask me questions, then I might just go on autopilot and just, you know, pull speed ahead. Awesome. Okay, everyone. Okay, can we get started? Wonderful. If I'm looking in this direction, that's why I moved your faces. So I just want to kind of have a quick feedback. There we go. So introductions to Commercetools Schools as a platform. Sorry about that. So our whole product offering can be. Described in this kind of layered, cake like structure that you see here. So the foundation of everything is the Commercetools Stors platform. We'll talk about it in a second. And resting on this platform, we have our main product. So we have commerce tools. Composable commerce. This is the topic of the conversation of this whole training. And composable commerce, as you can see here, comes in two flavors. So we have a B2C version of composable cameras and we have a B2B. Once again, in this training, we will focus mostly on the B2C 1. But if you are interested in B2B, we have a whole separate one day session functional Architect session devoted to B2B after completing this training, you can sign up for that thing. Mehtap Parkinson | 18:19 To me to be ex. Speaker 2 | 18:23 It's a one day training that kind of goes over the extra B2B stuff. On top of what we will be talking about. We have Commercetools frontend as a separate product. So even though we are a headless platform, you may choose to take to use the front end that we offer as well. Mehtap Parkinson | 18:38 To use the as well. Speaker 2 | 18:40 You don't have to. Mehtap Parkinson | 18:40 We don't have to always see. Speaker 2 | 18:41 We always we are always offering our customers a choice. Frontend is a topic if you're using CAMERASOURCE frontent we will not be covering here. I will just mention basically that it exists and maybe some benefits and so on, but otherwise we have a whole separate free day. Mehtap Parkinson | 18:52 That it exists. But. Speaker 2 | 18:58 Front end training. And of course you may. Doesn't matter if using front end backend both of them, you probably want to integrate them with some systems you're already using or that you will be using. Mehtap Parkinson | 19:09 That you will be using SOF from scratch to help you focus. Speaker 2 | 19:10 So integrations are supported. You can write the integrations yourself from scratch, but we have tools that can help you, like connect, for example. That way you don't have to focus on hosting those integrations. We can just host everything on the camera tools side. We can help you with that, but we'll talk. We'll cross that bridge when we get to it a bit closer to the end of this training. So let's focus on the camera stools platform. So our platform is a cloud native infrastructure. Cloud native, not cloud adopted. This means that Commercetools Composable Commercetools was built with cloud in mind from day one. So this was not just some kind of on prem application that one day we just decided we're going to put in the cloud. No, it's been built with the cloud in my from day one so we can use the kind of native functionality that mainly Google Cloud and AWS have to offer in terms of security, scalability, all that stuff. We want to make sure that we benefit from all of those features as well when using Commercetools because especially, you know, in Commercetools, scalability is a very important thing. Because, as you probably know, traffic in commerce is not a flat line. It's usually a flat line. And then you have those peaks. Like Black Friday. Holidays. You know, there's always some stuff happening and then you need to scale accordingly. But you don't want to scale the whole platform, you want to scale the parts that need to be scaled. And that the way how our platform is built, the way where it's hosted. Repay it's really kind of important in accomplishing that to make sure you don't overpay for scaling things you don't need. But we'll talk about that in just a second. Of course, we want to make sure that everything is nice and secure. So we have best in class practices like SLA as monitoring incident responses. Mehtap Parkinson | 21:09 Response to three points in a few seconds as well. Speaker 2 | 21:09 You have an amazing support team. We're going talk about support in a few seconds as well, so more on that in a few moments. Mehtap Parkinson | 21:14 So moment that in. Speaker 2 | 21:17 This is supported by a robust but expandable data model, meaning that when you get commerce tools composable commerce out of the box, you already have, let's say, all the popular components that people need to build an e commerce solution. But obviously, everyone's needs are different. That's why our data model is very extensible as well. Mehtap Parkinson | 21:40 That excites them as well. Speaker 2 | 21:42 So you can kind of build on top of it and shape it to your knees. Mehtap Parkinson | 21:42 So we get on top of and expect when it comes to how yours will be represented. Speaker 2 | 21:46 And that's especially important when it comes to how your products will be represented. Mehtap Parkinson | 21:50 That actually one of the. Speaker 2 | 21:51 And actually, one of the main focuses of this training is how are we modeling our products, how are we representing them in this Composable Commercetools project Versionless. That's a very interesting aspect, and one of our kind of main features, I think the differentiators of Commercetools is that yes, we are versionless. Mehtap Parkinson | 22:04 Interesting aspectsable checks you see like it's ving 1.3 point something's working two points something certainly what that means always have access to all filters. Speaker 2 | 22:13 That means when you use composable commerce, you don't see like it's version 1.3 point something, it's version two point something. Instead of versioning our software, we evolve our software. We always focus on backwards compatibility. Essentially, what that means is you pay for camera stores. You join at any time, you always have access to all the latest features. You don't worry about updating. Mehtap Parkinson | 22:38 We don't worry about building that's Speaker 2 | 22:40 We do updating for you, but you don't have to worry about backwards compatibility. That's on us. Mehtap Parkinson | 22:46 So. Speaker 2 | 22:46 So essentially, if, let's say you're someone who created a commerce source project in 2017 and you haven't touched it since, it's still going to work today. Mehtap Parkinson | 22:56 It's. Speaker 2 | 22:58 Because we make sure that of course, we constantly introduce new features to composable commerce, but we always want to make sure that it is backwards compatible so that we don't want to annoy developers on our customer side saying, By the way, next month we're releasing this thing, it's gonna completely change how pricing works. So you guys should really change your pricing model because otherwise your whole store will stop working. You know, no one wants that, so we avoid that. And we want to make sure that if you want to use the new feature, go ahead. You may have to do some changes to use it, but if you're happy with the way things are, they are going to continue to work in such a way. Mehtap Parkinson | 23:36 You go to continue to work in such a way going for the. Speaker 2 | 23:39 Going forward to the future, we will make sure that it still works. Yes. Connect integration platform is a big thing. Connect is kind of like a new product that we offer. And basically it comes down to us hosting your integrations. Because traditionally, when you want to Design an integration for a platform, you know you have commerce tools here, you have, let's say, your ERP system here. Mehtap Parkinson | 24:02 System here you need something in the mi to each other is. Speaker 2 | 24:02 Well, you need something in the middle that's going to make those two systems talk to each other. That thing in the middle, this is your integration code. And traditionally you had to host this yourself and figure out how to do that. But if you use Cameras Tools Connect, we will host that code for you. Mehtap Parkinson | 24:19 That resources. Speaker 2 | 24:20 It's going to sit right there next to cameras tolls. It's going to have nice and quick access to all the resources of your project, just kind of reducing the hassle of the whole process. But we're going to talk about Connect closer to the end. Everything is logged and monitored. We'll talk about the audit log a bit later, but essentially what that means. Well, you can always see what happened to your project. We keep a record for at least one year and if you pay a bit more for three years of what's going on in your project so you can see all the changes that have been made, who made those changes and so on. Mehtap Parkinson | 24:52 All the changes that have been made for many it those steps. Speaker 2 | 24:56 And you can kind of work your way back from there. So even if someone messes something up, you can always retrace those steps and kind of see, you know, what went wrong. And how can we go back? And as I kind of mentioned, with the data model, it's all extensible. So usually in this training I get a lot of questions like is it possible to do this? Is it possible to integrate with that? Is it possible to do this? The short answer always is everything is possible with customization, some things are available. So usually my two answers are either something is possible out of the box, or something is possible, but you have to do some customization for maybe on your front end code, maybe on your bfff layer. But we are very open, we don't block you. So we want to make sure our customers can basically create the scenarios they want to create because everyone's needs are different. You know, it's pretty much impossible to build an e commerce platform that out of the box fits the needs of all the possible customers. I mean, everyone has their own way of selling stuff and it just. I don't think it's feasible and possible to do that. So the focus of this training, like I mentioned, is cameras, tools, composable cameras. This is the main product that we're selling. It's been in the market since 2006, I believe. Sorry. 2013. So, yeah, it's 15th here on the market. And still growing and still evolving. Like I mentioned. Now the Best Way to describe Commercetools Composable Commercetools and basically Commercetools Approach to Building Software is with four letters MA CH. You can read this a Mac like max speed. If you watch Top Gun, they talk about max speed quite a bit. There basically means very fast. I think it's the ratio of the speed of the plane to the speed of sound or something like that. So, Mac, 1 is the speed of sound. Anyway, apart from my Commercetools colleagues, who I'm sure they know what this abbreviation means, let's try to break it down. Mehtap Parkinson | 27:12 Gues who are trying to know the means and. Speaker 2 | 27:18 Can anyone tell me maybe you saw some of our marketing material what the M stands for? Microservices. Microservices. Okay, it looks like Patrick saw some of those slides from marketing. Very good micro service. And I apologize for my terrible writing, but. Well, that's why I went into it, so I don't have to write by hand. And now would cut up. All right. Microservices. Yes. So this basically describes that we don't have a monolith application that we offered to you that. I mean, you have to use the whole thing and, you know, it's kind of all just jumbled together. Instead, compsable commerce is built of teeny tiny applications. We call them microservices. Each of them is responsible for doing a very specific task. Mehtap Parkinson | 28:13 So that's responsible. Speaker 2 | 28:13 So you might have a microservice that's responsible for managing discount codes. You might have a microservice that's managing customers, and if you want to create a new customer, you make a request to that microservice hey, create this new customer in the database and it does it. They all communicate using REST API as the communication standard and they talk to each other. Mehtap Parkinson | 28:33 They talk to each other as. Speaker 2 | 28:34 You can talk to them as well. This swarm of microservices together forms composable commerce. That's where the word composable comes from is that you have all these little applications swamp together, making this platform. But if you're not happy with one of them, you can just not use them and maybe bring in like a third party thing or something you wrote yourself and use that instead. Mehtap Parkinson | 28:57 Yours and use that instead. Speaker 2 | 28:59 So that's kind of. Mehtap Parkinson | 28:59 So that's into the composable part of the services are exposed to you. Speaker 2 | 29:00 That kind of ties into the composable part of the name of our software. And usually a lot of those Miro microservices are exposed to you. So like I said, you can communicate with them as well using the API so we're going to use the word endpoints quite a bit throughout this training. Mehtap Parkinson | 29:10 So you. Speaker 2 | 29:19 You will see that once you have your project, that project will have different endpoints like here we can see a customer group's endpoint or a category's endpoint. Mehtap Parkinson | 29:20 Have your project will have different endpoints. You basically see endpoint and categories endpoint. So this isgories we have the new categories. Speaker 2 | 29:27 This is usually where you would communicate with compos of commerce to work with a specific resource. So for example, I would like to see what categories we have for our products. I would like to create a new categories. You will accomplish that by sending requests to the categories endpoint. Mehtap Parkinson | 29:39 You have to start by sending requests to the categories. Speaker 2 | 29:46 Of course, we have the merchant center. So these days, to work with composable cameras, you don't have to do everything for commands and for the API we have, you know, an interface, a front end interface, a visual interface that you can use to do that. Mehtap Parkinson | 29:49 That is to do. You can. In terms of the API, you know. Interface. Interface. Interfa. Speaker 2 | 30:00 But it's good to kind of be aware, because the API is still the most powerful way of communicating with composable commerce. And that actually ties into the second letter a what could that mean? A very good API first. I know it's technically two words, but you know, I'm not going to argue with marketing. It's their game. They really wanted this Mac thing, right? API first. API first basically comes down to all the functionality of Composable Commercetools is available to you over the API so using commands, using curl, using Postman, using Bruno. Doesn't matter what you use to issue API requests and receive responses that where you have access to everything we offer. Now the Merchant Center is a very nice visual way of working with your project. But the Merchant Center is and always will be a bit behind, you know, behind the API whenever we release a new feature, of course, we guarantee that you can use it over the API over the Merchant Center? Well, maybe not today. Maybe it is available, maybe it will be, maybe it never will be. It depends. So it's good to be aware how to work with the API as well. In this training we focus mostly on using the Merchant Center, but there will be things that I even I cannot do with the Merchant Center, and I will show you how to do them over the API as well. So you'll have a chance to kind of see that part, even if you're not really involved in that. Mehtap Parkinson | 31:36 That if you're not reading as. It's interesting you like. Speaker 2 | 31:38 I think that would be interesting. You know, you'll feel like a hacker at the end, looking at data and code and stuff. So that's going to be fun. All right. C in Mac. What does C stand for? I kind of mentioned that a little bit when I talked about the platform slide before. Speaker 6 | 32:00 Loud Native. Speaker 2 | 32:02 Loud native perfect. Like I said, we are cloud native, not cloud adapted, so absolutely it's built with cloud in mind from day one. I talked about it already, so let's just jump straight to H headless. Very good, wonderful headless what does headless mean? Let's see. Maybe. Maybe Max, you can tell me how do you understand the word headless when talking about an e commerce platform? Speaker 4 | 32:44 Well, it means it's loosely coupled. There isn't one thing controlling everything. Speaker 2 | 32:49 Somm yeah I like loo loose decoupled or even decoupled I guess. So basically the front end is decoupled from the back end. Means that we don't enforce any front, we don't force you to use any specific frontend. Mehtap Parkinson | 33:00 Means that we don'. Speaker 2 | 33:06 You know, you can use Carsce then, but it's always an option. We never force anyone to use it. Most of our customers actually have their own. So basically it means we give you taking Mercedes into example, we give you the engine, we give you anything that everything that this car needs to function as a car. Mehtap Parkinson | 33:20 We give you the engine, we give you anything and we think that. Speaker 2 | 33:26 But how it will look like, what the body will be, how the people will work with it, that's up to you. So especially, you know, these days when there are so many ways how we can interact with an e commerce solution, it doesn't have to be a website or a mobile app anymore. Mehtap Parkinson | 33:38 So doesn't have to. Speaker 2 | 33:43 You know, we got now screens everywhere, like on our fridges, in our cars, on our wrists. We don't even need screens because we've got voice assistants that can help us with our shopping as well. Mehtap Parkinson | 33:51 Help us with our shopping as well. Speaker 2 | 33:54 So there's so many different ways. Mehtap Parkinson | 33:54 So. So many different ways how we can interact and that you want to force on our customers. Speaker 2 | 33:55 How we can interact and buy things that the interface could be whatever you want. So we never want to force anything on our customers. And that's actually kind of been the story for quite a long time because when you look at it. Mehtap Parkinson | 34:08 Whatas. Speaker 2 | 34:10 When it comes to commercetource front end. Maybe some of you who have been in the industry for a bit are familiar with a company called Fastic. There your Adrien knows. So fantastic. They used to do the opposite of what we were doing. They were doing FRONTENT for headless platforms. So if you. Camera schools being one of them. And we really liked what they were doing. And we had some customers coming to us saying, well, you know, this whole headless thing, that's a great approach. Mehtap Parkinson | 34:36 Had some customers coming to us saying well, you know this whole camp, you just give us something that we can. Speaker 2 | 34:40 But could you just give us something like some starting point that we can just quickly customize and get going? So by that time, Commercetools was a big, successful software company, and they did what any big, successful software company does and we bought a smaller successful software company B, which is fantastic. Mehtap Parkinson | 34:55 Success. Speaker 2 | 34:58 So fantastic is no more. Now it's called Commercetools Front end and you can use it as one of the options for building the front end for your composable commerce project. Very good. So that's what Mac means. This is our philosophy behind how we build our software. Mehtap Parkinson | 35:17 Our software actually proud of this. Speaker 2 | 35:18 We are actually so proud of this approach that I think it was in 2017. Mehtap Parkinson | 35:20 Ros over 01:20 is of software companies that fund these principles. Speaker 2 | 35:23 I might be wrong. On that date, we co founded an organization called the Mac Alliance, which is basically a little club of software companies that follow these principles when it comes to how they build their software. Mehtap Parkinson | 35:34 When it comes to build the software is growing growum every year in the their responsibility and find that they. Speaker 2 | 35:37 And that group is growing and growing every year. They have conferences if you follow Commercetools LinkedIn. The Mac stuff shows up there as well, so you can find them there if you want to learn more about that. Just to reemphasize the API only or API first approach, because this is especially if I give developers in this training, they sometimes ask us well, can you do I have direct access to the database? And the answer always is no. You always use the API, which go, you know, you always go through us, through the microservices to get to the data. There is no way around it. There's no direct access to the database. Yes, maybe it would be faster in some cases, but it definitely would become more complex and less safe. Mehtap Parkinson | 36:24 Comp. So this is the approach we have. Speaker 2 | 36:25 So this is the approach we have. Mehtap Parkinson | 36:27 We have. Speaker 2 | 36:27 Not like some of our competitors where some of the functionality is available over the API, then some of it is for some proprietary interface, then some of it is by going directly to the data. Mehtap Parkinson | 36:38 The in our case nothing more than just but other G pi. Speaker 2 | 36:39 Now, in our case, everything goes for the E Pi, even the Merchant Center. The Merchant Center is nothing more than just a visual interface, kind of on top of the API it still does the same type of API requests you would do if you would just issue the commands yourself. Mehtap Parkinson | 36:48 It still does the same type of API request. I too if. Speaker 2 | 36:53 It just makes it a bit faster and easier for you. So everything goes through the API this is definitely our approach now to use the API to use Commercetools, you need to be. Obviously, you're not going to remember everything. You're not going to remember every single resource, every single command. Mehtap Parkinson | 37:14 That's why it's important to them how to navigate documentation. Speaker 2 | 37:14 That's why it's important to know how to navigate our documentation. Mehtap Parkinson | 37:18 So let me take you a. Speaker 2 | 37:19 So let me take you on a brief tour of how to read our documentation. And that is available under dobs. Commercetools.com. And I can actually tell you a bit more than two years ago when I was approached by camera schools to start working here, one of the first places I visited was their documentation. And I was blown away. Like how neatly organized everything is. Because I'm not gonna say anything bad about my previous employer. They are an awesome company. But their documentation really needed some work. So I was really like, this was, you know, my Disneyland. When I saw this, i wasn't blown away by this, alright, but let me show you how well organized it is. And let's actually work our way from the bottom. Mehtap Parkinson | 38:08 So here we see release Speaker 2 | 38:09 So here we see release notes. Since you're not asking too many questions yet, at least one of another popular questions I get is what is our release cycle? How often do we update composable cameras? And because, you know, some companies do it like every two weeks, every month on a specific day, they have an update date, rollout day. Mehtap Parkinson | 38:26 A big like you can see its whatever you feel like it's like I almost every days we have so many different problems. Speaker 2 | 38:30 In our case, you can see it's whenever we feel like it. Pretty much sometimes it's like even actually, like almost every day. Our engineers have been busy from the beginning of the year. But yeah, basically whenever a feature is ready, we roll it out. We don't wait for a specific, you know, day or nothing like that. Now it's ready, send it out, make sure customers can use it so you can view all of their release notes here. Of course. You know, we have so many different products and areas in those products that you can of course filter these updates as well these releases. Mehtap Parkinson | 39:00 We ask in those parliaments to that of course filter these outptics as well these releases to f as like possibles specifically the ep. Speaker 2 | 39:08 So if I'm interested in stuff related to composable commerce, specifically the API, I would like to know about new features because that's exciting. Mehtap Parkinson | 39:14 I'll like to. About new. The. Because that's exciting. Speaker 2 | 39:17 So there we go. You can narrow it down to filter down to the things you need. Once you open the details, it does a very good job and explaining what has changed. What is the new thing where it's documented? So to learn even more about that, well, this is actually a B2B topic, but so we won't be talking about business units too much. But it's nice that we have them. So very cool stuff. It's a good idea to come here every now and again and kind of see what new stuff was released, but you don't have to come here every single day when you have your morning coffee and see what's what. Mehtap Parkinson | 39:44 It's a good. What's really you can just, you know, subscribe to an artist and speak. Speaker 2 | 39:55 New stuff COMMERCEOLS released. You can just, you know, subscribe to our RSS feed. So when you have some kind of RSS reader or built in your browser, we can notify you whenever there's a new release and you can find about it that way, or you can just subscribe to our product newsletter and every month we'll send you an e mail with a summary of what happened in the last month or so. Mehtap Parkinson | 40:01 So when you got some artists reader that you can we can notify you and you can just describe to our newsletter and will send an email in the last month or so. Speaker 2 | 40:20 It's a good idea to kind of stay current, especially when you are a developer working with camera tools, because, you know, maybe you had a problem and that problem has been solved. Mehtap Parkinson | 40:20 Difficult you have to especially when you are in development what your power is. So you know the problem and the problem has been solved with e problem. Speaker 2 | 40:29 Maybe we have a nicer way of doing something that used to be not so easy in the past and so on. Mehtap Parkinson | 40:30 And you are doing something that used to be so easy in the price. On. Speaker 2 | 40:36 So there's constantly stuff going on. Any questions, my friends? About the rebase notes, I think they're pretty straightforward. Good, right now let's move on to this support section here. I'm not going to go through everything in here, just maybe the most important stuff. I mean, who cares? Come up training costs. I don't even know. Company pays for that. No one cares. So SLA service level agreement. Mehtap Parkinson | 41:13 Service agreement. We want to make you some promises for a license for all schools. Speaker 2 | 41:14 We have to make you some promises when you buy a license for commerce stores, and the main promise is our availability. Mehtap Parkinson | 41:18 And the main part of. Speaker 2 | 41:22 We promise you that we will have an availability of no less than 99.9%. That means that our s we promise you that our services will be up 99.9. Mehtap Parkinson | 41:33 That ours will be 99.9 on in the year. Speaker 2 | 41:37 Excuse me. Of time in a year, which means that in a year, our services cannot be down for more than. Mehtap Parkinson | 41:42 Our services can be from. Speaker 2 | 41:45 I think it's like almost eight hours or something like that in a year. Mehtap Parkinson | 41:45 I think it's like almost three hours or something like that of the year. So that's quite a small window. Speaker 2 | 41:49 So that's quite a small window. And as far as I know, at least we've never gone below that. We actually are like 99.99999. Like, there's a lot of lines after that every year, so that's pretty good, pretty stable. Mehtap Parkinson | 42:04 Able how can you know if something is there? Speaker 2 | 42:04 How can you know if something is down? Well, you can go to the status page. Mehtap Parkinson | 42:07 When you can go into the studies page? I you say you feel like the number 100 and the House of Green. Speaker 2 | 42:10 I always say if you like the number 100 and the color green. Mehtap Parkinson | 42:13 This is the website for you. Speaker 2 | 42:14 This is the website for you. There's a lot of green and a lot of one hundreds here. Mehtap Parkinson | 42:16 There's hundreds here. So right heres, they are both under running and that's nice. Speaker 2 | 42:19 So right here you can see all of our different services in the different regions. They are all up and running. That's nice. Mehtap Parkinson | 42:30 And we didn't see any. Speaker 2 | 42:30 And we can see have they been up and running in the recent history weak month. We had a bit of a hiccup with Google Cloud in Australia on the seventh. Looks like it. So you can kind of see basically whenever you have any issues. That's Australia making a mess. Mehtap Parkinson | 42:52 Making announcement, any connected with the merchant center or a request or something like that. Speaker 2 | 42:54 Basically, you can kind of see if you have any trouble connecting with the merchant center, or maybe your API requests are bouncing or not getting through or something like that. Mehtap Parkinson | 43:03 But. Speaker 2 | 43:04 Before contacting support, maybe the first thing you should do is go to this status page and see. Well, is everything up and running? If it's not, we probably know about it already and are working on it. Mehtap Parkinson | 43:12 We probably already and are working on it. Speaker 2 | 43:15 If it's showing that we are green, maybe the issue is somewhere else. Maybe it's, you know, your firewall, your VPN, your internet provider could be in a whole range of issues that can impact a connection. You can subscribe to this as well, so we will notify you if something is down as well. So there's a lot of choices. What's this one? Mehtap Parkinson | 43:40 '. Speaker 2 | 43:41 O There we go. You can even have a bit of a more detailed information in North America in Google Cloud and Euro Google Cloud. There we go. So if you want to know specifically what happened on a specific day, let's see January seventh in Australia. Mehtap Parkinson | 43:57 Specifics started Australia way. Speaker 2 | 44:03 So we're very transparent. We're even gonna let you know what was the issue and how we resolved it and when. So that's nice. This is actually, I think, a new page. I don't remember seeing this one, so that's right next to that one. If anyone's interested, you can read that as well. What happens if something does not work? Who you're gonna call? Well, obviously not. Ghostbusters. You're gonna call our support team. You can just go to support.camerastols.com and I will take you to our to the support portal where you can send the ticket. I will not click this because it looks a little bit different for me as an employee, but that's where you go. Well, what happens if the support if the ticketing system doesn't work? Mehtap Parkinson | 44:48 What happens if it exist? Doesn't work as we have. Speaker 2 | 44:52 Well, we probably have a lot of problems, but, there's a backup solution. We have emails down here that you can use. So if the ticketing system doesn't work, you can use these emails to let us know. By the way, a nice feature of the documentation is you can send copy a link to a specific section of a page, which is super convenient when sharing links with people. Mehtap Parkinson | 45:10 A specific sections which is reient with the. Speaker 2 | 45:17 So that's in the chat for those of you who are interested. You might end up actually contacting support a bit more, than you would suspect, because you don't only contact support when something goes wrong, but when you just want something or you want something unlocked, because there are certain things that you can only do for support just because you want to make sure it's done in a safe way. Mehtap Parkinson | 45:33 Goes wrong but because there are certain things that you can only do for support. Just because your electron it's still in the same way. Speaker 2 | 45:46 Yes, Bob. Mehtap Parkinson | 45:47 But. Speaker 8 | 45:48 Yes. If we have a partner, an implementation partner, do we con contact them first or can we contact Commercetools tool straight away? On how is that I usually. Speaker 2 | 46:04 Going you know what, I don't think there's any harm. It depends on who's on you're and going to fix the issue. Mehtap Parkinson | 46:09 Depends on who the be the one working with supportization partner maybe the like just for them. Speaker 2 | 46:11 Like they're gonna be the ones working with support. I guess you should do it for them. If you're going to be fixing it directly, then it should be you. And there's a third thing depend depends what's in your contract with that implementation partner, maybe they, you know, it's even going to be in the contract. Everything has to go for them. They don't want you doing stuff on your own because then they will not be aware of it and it will be harder for them to come in and help you. Mehtap Parkinson | 46:30 They don't want you to fix up wrong because they will not be aware of it. So it will be harder for them to come in. And. Speaker 2 | 46:36 Maybe later on. So I would look at it that way. Thank you, Bob. And finally, I got a question, so that's nice. Awesome. Yeah, so like I said, some things you can only do for support, for example, recovering from a backup. I did say that we do have an activity log. Mehtap Parkinson | 46:55 I did. Speaker 2 | 46:58 So everything that's happening in your project is logged, so you can always kind of retrace your steps and go back. But what if you mess up really bad? Mehtap Parkinson | 47:05 Myself some. Speaker 2 | 47:07 What if someone accidentally deletes 200000 products that you've, you know, been importing into the project and so on? You lost a big portion of data accidentally from your project. Mehtap Parkinson | 47:16 Big portion of dataly from your project every two hours and for fourteen days. Speaker 2 | 47:20 Well, the good news is we back up your project every two hours and we do it for 14 days. Mehtap Parkinson | 47:27 So. Speaker 2 | 47:27 So if you delete a huge amount of data and you want to get it back, you can recover from a backup. Just like those of you who are using Windows or have been using Windows, there's an option to like a time machine, you can always go back to a stamp in time how your system look like. Mehtap Parkinson | 47:40 How your system looks like so you can as you can do yourself that supports to recover from the back of them and I'll do something. Speaker 2 | 47:41 So we have a similar thing, but this is not something you can do yourself. You have to contact support and support will recover from the backup. So don't treat that. Treat this as an undo button. Mehtap Parkinson | 47:54 But that's a very small amount amounts. Speaker 2 | 47:54 Because it's a very slow undo button when you think about it. But it's up to you what happens after 14 days. Mehtap Parkinson | 48:01 After. Speaker 2 | 48:02 The backups get permanently deleted. So if you mess up really bad and you don't realize for two weeks that you messed up really bad, then possibly there's no way of going back to that thing. So. But I you know, the assumption always is when people really mess up, they probably know about it like pretty fast. So I think the two weeks. I mean, if customers would have problems with the two weeks. Mehtap Parkinson | 48:28 That, the problems for the two weeks. Speaker 2 | 48:30 We will probably make this time longer. Mehtap Parkinson | 48:30 We would probably make this time longerconnected. Speaker 2 | 48:32 But so far, looks like this one is working. Do we still have everyone for someone. Yeah, so for someone disconnected, so this is our backup cycle and again to recover from the backup, this is just a support thing. Mehtap Parkinson | 48:41 So this Isomers device. Speaker 2 | 48:50 Very good. You can get premium support. I don't know what is your status? Those of you in the call who are our customers standard. So everyone who buys Commercetools gets an uptime of 99% 99.9%. Mehtap Parkinson | 49:04 99% 99.9% point you mentioned if you pay your customer, it's 79 point 99%. Speaker 2 | 49:06 Like I mentioned, if you're a premium customer, it's 99.99%. Mehtap Parkinson | 49:10 Which means the downtime. Speaker 2 | 49:10 Which means that downtime cannot fall below 50 something minutes. I don't remember, but it's like less than an hour. So very huge uptime. You get faster responses to your support tickets, so that's nice. Mehtap Parkinson | 49:24 That you would give a phone directly. Speaker 2 | 49:26 And I think you can even get a phone number to call support directly. What happens if we go below these numbers? Well, then we will give you a service credit as they are, service credits as they are called. Basically, you're going to get some money back on your contract. That's kind of what it comes down to. I'm not involved in that, so I don't really know that much, but there we go. And I don't think it happens often or at all so far. Right, so that was the backups SLAs I wanted to check one more thing. Yeah, there you go. Compatibility and recycle. Like I said, compatibility, you don't have to worry about it. I mean, we do the updates, you don't press any button, you don't do anything. When we say Hey, we release this new feature, you open up Commercetools, there it is, it's already in your project, so we can use it. What is the release cycle for these new features? There's actually three steps. So whenever we are ready to first share something with a small group of people, that feature is released in Early Access. Previously this was called closed beta, so that means that only specific groups of people can use it. Usually this is the customer or partner that requested this feature. In the meantime, maybe we identified some customers or partners who wanted something similar, so we're going to pull them into this as well. You know, maybe we can solve a few problems with one go. And they can mess around with this. They can try it out on a project, see if it meets their expectations. If they're happy with it, they can give us feedback. We can tweak a few things, but like I said, it's a closed beta thing, so it's still relatively. It can change if things can be modified. That's why you cannot use early access functionality in production projects. So basically you cannot use them in an actual backend for an actual web store somewhere that people are using to buy things from you. Because, well, again, this feature might change, might completely get deleted, so you don't even want to take that risk. That's good, Ada. Thank you for letting me know. Aan needs to get the door, so that's early Access. Once Early Access is over, a feature gets released as public beta. When something is in public beta, it means it's a robust and secure implementation. Mehtap Parkinson | 51:56 Its ros and secure and implemented two kids kis so kindly closes of use it can use it. Speaker 2 | 52:00 That means yes, it's still in beta, so some things may still change with it, but we are so confident that it works well. Everyone can use it and you can even use it in production projects. How do you know if a feature that you're using is in public beta? Well, when you look at it in the documentation and you'll see it a bit later as well, it's going to have this blue beta flag tag lill next to it, so you'll probably see it in a few places once we kind of keep going. Now again, it's still beta, so technically it may still have some changes that will involve you changing something as well in your code, for example when you're using this feature. Mehtap Parkinson | 52:33 And some changes that we all the changes will be announced three months. Speaker 2 | 52:40 So breaking changes will be announced three months in advance at least to give you time to adjust to it. And removals either of part of the feature of the whole or the whole functionality will be announced six months in advance. Mehtap Parkinson | 52:53 Six months give. Speaker 2 | 52:56 Now, we mostly mentioned this here to cover ourselves. I can tell you this is theoretically this may happen practically. I'm. I mean, I've only been here for like two years. I haven't seen this happen yet. So this is just so we are prepared if that situation comes. But in ninet 9.9% of cases. Public beta things, the way they work in public beta, that's how they will work when they're generally available. Mehtap Parkinson | 53:24 Like one song pretty safe using that but it's so if you keep those this may sal. Speaker 2 | 53:24 So you're pretty safe using them. But again, it's good to kind of keep this in the back of your head that this may potentially happen, so just please be aware of that. Speaker 8 | 53:38 Is there. Speaker 2 | 53:39 Like a community. Speaker 8 | 53:41 Forum or something where people request those new features? Or is it done by your account manager or anything? Speaker 2 | 53:52 Sure. I mean, so yeah, you have an account person that deals with you. You can through them you can make suggestions to what you would like to be in commerce stores. Mehtap Parkinson | 53:55 From the. Speaker 2 | 54:00 Speaking of community, yes, we do have a community page. It's not really focused on gathering feature requests, it's more on customers, partners and even people working in Commercetools just communicating and solving problems, discussing different ways of doing things. Mehtap Parkinson | 54:16 Problems discussing different ways of doing things. Speaker 2 | 54:20 So yeah, I would go for the account person to request new features, but this is still a good forum to even say Hey, we want to do something like this. Mehtap Parkinson | 54:20 So. And to. To. To. This is a little bit. From. To. Ob. Speaker 2 | 54:30 Is this right now possible? Or maybe someone else solved it in some way and they can share that information with you. So this would be the forum, the official curated by us forum to do that kind of stuff. I will talk about it at the end of the training, but the link is in the chat for our community page as well. Thank you for that question. And yes, once the once something is like ironed out, we are happy with how it works, it becomes generally available. We send out a release note saying that hey, this feature that was in beta like two months ago now is generally available. And then basically what happens is it loses the beta tag and that's it and just continues to work the way it did it. Mehtap Parkinson | 55:13 Continues. To. Speaker 2 | 55:16 When it's generally available, then you don't have to worry about these things. So it's going to work. Zero stress after that. Now, with all that said, yes. Speaker 5 | 55:30 Advian has it been sometimes the case that there is like a better release and therefore some or is reworked or change or something? Because I guess if it's better, it's because you're getting feedback, right? So. Speaker 2 | 55:44 Yeah, and you know, some things are in beta for longer or shorter periods of time. It really depends. But. Yes. Sometimes something is generally available. Even. And we add new stuff to it, but it's kind of put on top of the existing functionality, so we just want to make sure it doesn't mess with anything people are using. So far, that's how that's usually handled. Now, sure. Does this mean we never get rid of things? We do have deprecations and we announce those as well. But well, the nice thing about being a software as a service company is we know exactly what features our customers are using. So that way, if we see that there's a field somewhere that no one has used. Like, literally no one is using and we want to get rid of it or we want to change it to something else. We'll just do it. I mean, obviously we'll post a release note about it, but we'll just do it. No stress to anyone. Sometimes we do what's called a silent deprecation. So when, let's say there's a field or a feature that's like very niche, like literally just a few people are using it, we will. It's going to still work, but we will, for example, hide it from the get rid of it from the documentation. So no, new customers will start using it because maybe you want to point them to this new feature that we released that does this thing better arguably or something like that. Mehtap Parkinson | 57:06 Customers. Us. Speaker 2 | 57:14 So that may happen as well, but generally all you have to worry about is. Like I said, as far as compatibility is concerned, your staff will still work so you are always safe. You don't have to make any changes. Mehtap Parkinson | 57:28 Any changes? Speaker 2 | 57:29 The only time where you might be required to make changes, like I said, is if you're using public beta features. Mehtap Parkinson | 57:30 You might be to. Any changes? Like. Speaker 2 | 57:35 In that case, theoretically, yes, we might tell you that. Hey, this thing that you're using, just make sure you're doing it this way because we're going to make some changes and it's going to do something else. So just be aware of that. And the final part in this support section is the limits page. This is a page I want you to have opened throughout this whole training. So as awesome as commerce tools composable commerce is, it does have its limitations because of, you know, for performance reasons, because of the technologies use. I mean, there's always limits to something, and they are all listed in this page. It's important to be aware. Some limits are more important than others, and you can come across them more often than others, so it's a good idea to be aware. For example, here we have a limit on slugs. What is a slug? We'll find out. If you don't know. The worry. We'll get to that, but we can see that the slug is limited to 256 characters, and that's it. If you want a slug to be five 300 characters, that is not possible. So this is what we call a hard limit. That means nothing can be done about it. So you just have to kind of work your way around that. But then we have other limits like, for example here. Categories. A maximum number of categories in your project is 10000. That means you can have 10,000 categories. But what if we need 15,000 in our project? Well, if a limit has this low note below it, this is what we call a soft limit. Soft limit means that, yes, this is the limit. This is the wall you're going to hit. But you can contact support. Tell them why you want 15000 categories. They will check if it negatively impacts the performance of your project. If it doesn't, they'll just raise the limit for you and you can have 15,000 categories, no problem. If it does create issues with your performance, then maybe they'll suggest some other way. Like, okay, what do you want to accomplish? Maybe we can do this some other way to make it work and not slow things down too much. Mehtap Parkinson | 59:52 Affects that too much. So that'ss. Speaker 2 | 59:54 So that's kind of why we have those limits in place. Some of them, like I said, for performance reasons, and all of them are listed here and throughout the training. When we're going to talk about something, I may want to point out what the limit of that thing is. And like the Spanish Inquisition, you never expect it. I might ask, Antonina, could you, for example, tell me how many? How many? I don't know. Let's see. How many product types can we have in a composable commerce project? What is the limit on product types? Speaker 6 | 01:00:39 I don't remember I. Speaker 2 | 01:00:43 Exactly that's why we have the limits. Yeah, but it's impossible to remember all of them. Speaker 6 | 01:00:50 I'm checkings. Speaker 2 | 01:01:03 Actually that's interesting. Hold on, I out there it is. Okay, sorry, yeah, how many product types can we have people love? Mehtap Parkinson | 01:01:17 The prosp. Speaker 2 | 01:01:46 So that's on the limits page, the one I linked. Yeah, I'm gonna give you a hint's in this actually in the configuration section, not in the product catalog section, which is weird when you think about it, but yeah. So how many product types can we have in a composable commerce project? Someone suggested, Advian suggested 100. That' not exactly it. Yeah, but he did it in a private message to me, so I don't think anyone else saw that. Okay, laylack is a suggestion. 1000 1000 where did it go? That is the correct answer. There we go. Product types. Speaker 5 | 01:03:32 1000 product types and variants. Speaker 2 | 01:03:36 That's a very good question. What's the difference between product types and variants? Yes, because we can have 1000 product types, we can have 100 variants. That's exactly what we're going to talk about a bit later today. Okay? So when it comes to product representing your products, there's three words there's product types, products and product variants, and they all mean different things, so it's important to know which is which. Yes. So thank you, maced up. In the direct message you said 1000, that is correct. Antonina, did you manage to find it or you know where. Speaker 8 | 01:04:08 Are you trying to? Speaker 6 | 01:04:16 Okay, yes, I found it. Yeah. Speaker 2 | 01:04:18 Actually I guided you wrong. Sorry, it's my fault. I said configuration was actually one step lower in conta customizable data behavior, so that's my fault. Sorry for that. Alright, can maybe Amogmola could you tell me is this a hard limit or a soft limit? You muted Amogmola so the limit of 1,000 product types is that a soft limit or a hard limit? Speaker 3 | 01:05:07 Sorry. I was still trying to come back because I was on the web. Sideite. So, can you show me? Can you ask the question again? Speaker 2 | 01:05:16 Sure. So we found that the limit for product types is 1000, so we can have 1000 product type. This is a limit. Is this a soft limit or a hard limit? So hard limits is a hard limit is a limit that means we cannot do anything about it. A soft limit means that, well, we can contact support and maybe if we need 2000 product types, they can help us with that. Speaker 3 | 01:05:41 I think it's a soft limit. Speaker 2 | 01:05:44 Exactly. Because whenever we see this little note below a limit, that means can everyone see my screen correctly? By the way? Okay, so sometimes I see something and it's not showing to you guys, so I just want to make sure. Yeah, so this means it's a soft limit. Very good. So just please remember that. And yet the Limits page. Like I said, in general it's important to kind of know where it is and maybe you don't remember how to get it through here. So that's why we have our wonderful search functionality. Whenever I need it, I just typed in limits and that's actually the first result I get, so that's a very quick way of getting to that page. So the search feature is quite awesome. I think that's all with when it comes to support. Mehtap Parkinson | 01:06:31 Come to support ss here we have thepos which is the topic of our you. Speaker 2 | 01:06:33 Next in the documentation page, we have two sections up here. We have Composable Commercetools, which is the topic of our training, and we have Front End, which is not the topic of our training. So I'll just ignore that and we'll go to the composable commerce part. And here we have some more sections. This one is about the merchant center. How to get started, how to do some basic stuff after this. After this training, if you pay attention, you won't need this because I will teach you all you need to know about the Merchant Center. But if you forget something, this is a good place to go. Now the holy book of anyone using composedable Commercetools anyone messing around with Commercetools is this one the HCTP API documentation. Because like I said, API first, all the functionality is behind the EPI that's how it's available. You need to know how to talk with the EPI you need to know what's available to you, what resources can you access, what can you do with them, how do you create them, what fields they have. All of that information is here in the HTTP API so anyone, I think working in Commercetools or anyone working with Commercetools doesn't matter if you're a developer, functional architect, whatever. Like they have this page open 2047 in a tab somewhere because this is the main reference point, and I will teach you how to work with this in just a few moments. Next, we have a learning section here. Just a bunch of handy tutorials. I'll leave that for yourself to explore, but something I would really recommend is this self learning section. And there are a few interesting things here. First of all, these three self learning modules. So this is basically our e learning stuff. These three cover, let's say, 80% of what we will do in this training. So a few weeks, a few months from now, if you won't be messing around with camera tools that much you know, you'll probably forget a lot of the stuff I'm gonna tell you because it's gonna be a lot of information I'm gonna drop on your heads if you want to refresh some knowledge. These three modules do a great job doing that. So when we're going to talk about pricing and three weeks from now, we're going to say, okay, what's the difference between embedded and standalone prices? Marius said something about it. Well, you can go here to types of prices and read what is the difference between embedded and standalone? Or you want to know, like some one? I think maybe I forgot who I was asking, but what's the difference between product variants and product types? Well, you can find that one here in Modeling your Product Catalog. And there you go. Product types what are those? Products and product variances what are those? But this is not dry documentation. This is explained in a way how I would explain it to you in a class how would the trainer explain it to you? So this is different concepts put into context and connected, how this thing talks to that thing and makes the third thing happen, and so on. Mehtap Parkinson | 01:09:48 St. TOS to makes the thing happen. Speaker 2 | 01:09:52 So very good resource. If you want to do some self studying, maybe if you can, if you want to take certification in the future, this is definitely a good way. I keep causing that tab. This is definitely a good way to prepare yourself for that certification. Yes. And we have these nice little refresher modules. These ones are just interesting. If you want to know, you don't want to go through all the release notes, but you want to know. Okay, what are the main things that happened in Commercetools in the previous year? This is still the one for 2023, but I think before March we will release the one for 2024 and it's a module highlighting all the new features that came to commer stores in the last year. So if you just want to learn about the new stuff, that's going to be a very fun module to go through. So I definitely recommend all of those. Why do I keep closing the tab? Just cannot help myself. So that's the self learning stuff in the developer course. I go deeper into this. But we have our SDKS documented. So software development kits where you can download them, how to work with them, how to build your first application that's going to communicate with your Commercetools. Composable Commercetools Project. We got SDKS in Java, TYPESCRIPT, PHP dot net, Swift, and I think that's it. So yeah, those are the ones that are maintained and supported by us. But of course, sometimes people ask, well, but what about Rust? What about? We got PIPPI mentioned. What about Rust? What about Python? What about, you know, insert your favorite programming language? Well, we use REST API as the communication standard, and that's a standard for pretty much all, you know, sauce platforms out there. So if you're using one of those languages, you can still make an application that's going to communicate with Commercetools just fine. It just means it's gonna require a bit more work on your end because you won't get some tools out of the box like the ones we provide in the SDK, but it's definitely doable. So this is not really a blocker for anyone. Mehtap Parkinson | 01:12:02 So this is like. Speaker 2 | 01:12:05 And we just chose to have these SDKS because these are the most demanded languages we get, especially Java and TYPESCRIPT. Mehtap Parkinson | 01:12:10 ESPECIALLYX. Speaker 2 | 01:12:12 Like 99, I think percent of our customers who write applications that work with Commercetools do it in these two languages. Mehtap Parkinson | 01:12:12 90 90%. Speaker 2 | 01:12:22 And then some use PP some use dot net. I don't think we get a Swift customer in quite a time. So there you go. Any questions here? All right, I see you're already getting a little bit tired, so the good news is we'll have a break in a few minutes. Let me just quickly go to this section. Like I said to the holy book and just show you how to work with it. So like I mentioned the HTTP API documentation. This gives you information about all the resources that you have available to you, how they look like, and what can you do with them. What do we mean by this? Well, if, for example, I would like to write an application that imports customers from Platform a into our composable Commercetools backend, well, I need to know how customers are represented. Or maybe I just want to build like a registration form on our website and have customers be able to register with our store. You can see how a customer is represented. Here. You can see a representation of a customer. It tells you what fields exist on a customer, what types of fields that they these are. So, you know, string basically means text, integer is a number. And you know, all IT people now, all this stuff. Now, some of these fields have. They have a nice little explanation. Sometimes the limit is mentioned. That's nice. Mehtap Parkinson | 01:13:57 That's what extent these ones are mand. Speaker 2 | 01:13:59 Some of these have a red asterisk next to them, which means that these ones are mandatory or required. That means, you know, a customer cannot exist without an ID, without a version, without an email, and so on. But everything else can be optional if you don't need it. But this is already important because as a developer, for example, I know what fields exist on a customer. I know exactly what their name is. Mehtap Parkinson | 01:14:24 Because you know given the APL right? Speaker 2 | 01:14:24 Because you know, when working with the API, it's usually not case sensitive, so you have to know exactly what the name of a field is you want to get out of a system and so on. Mehtap Parkinson | 01:14:26 It's my kids accident. So you don't exactly what the fis you want to system and. Speaker 2 | 01:14:34 So a lot of very useful information already. And then here on the right, you can see. Okay, this is how a customer looks like. But how do I do something with customers? Mehtap Parkinson | 01:14:46 Do something with customers? It's comer. Speaker 2 | 01:14:47 It's all written on the right hand side here. How do I get a customer? How do I creevy customers? Mehtap Parkinson | 01:14:53 How do I get a specific customer if I know it's. Speaker 2 | 01:14:53 How do I get a specific customer if I know what their ID or key is? How do I get a customer of a specific web store? It's all here. And for example, I want to get a customer by ID it shows me what type of request I need to use in my API Obviously for reading stuff, it's a get request. Mehtap Parkinson | 01:15:08 Using my p for read s? Speaker 2 | 01:15:13 What is the endpoint that I'm supposed to use? What do I need to provide and what type of response I can expect? Mehtap Parkinson | 01:15:18 Need to provide? I don't see what type of I can expect trans an examples. Speaker 2 | 01:15:22 E even shows you an example API request and an example response. So like I said when I was blown away by the documentation. Like, it's all here. It basically takes you by the hand and shows you everything you need to do. You just need to know how to read it. Mehtap Parkinson | 01:15:39 But and sold. Speaker 2 | 01:15:39 But it I think very well done. And I was definitely impressed when I first, you know, came to this company and saw this. And we won't be doing this very heavily, but we will be going back to this a few times in this training, how the presentation, how we do some things. Like I said in this course, most of the stuff we'll be doing in the Merchant Center you will not be required to do anything for the API so if you're not that technical of a person, don't worry about it. Mostly you'll just be clicking things and not have to type anything. But later on, if you want, I can show you some demos and postm and stuff how to do something for the API just if you're curious how that looks like one thing maybe just to be aware from an API perspective. Mehtap Parkinson | 01:16:16 POs stuff up you just like it for the UPI guess if you give that like just to be aware that from an API perspective and interesting behavioral resources. Speaker 2 | 01:16:27 The interesting aspect is creating resources. Mehtap Parkinson | 01:16:31 So the representations comer become a customer is the key. Speaker 2 | 01:16:31 So if you look here at the representations, for example, customer, we have a customer and there's a draft representation. So, for example, I see here that the customer has a key customer number, ID version, all this stuff. Mehtap Parkinson | 01:16:43 All this stuff it this version of the customer. Speaker 2 | 01:16:44 And then in the draft, it's almost the same. I mean, some stuff is missing. I don't have the ID, I don't have the version, but I still have the email. I still have this thing and all of that stuff. So why do I have two representations? The reason is the draft. This is the version of the customer that you submit when you want to create a new one. Mehtap Parkinson | 01:17:07 Did you submit what you want to you? So when you want to sub. Speaker 2 | 01:17:10 So whenever you want to create an new resource, you submit a draft version of it. If that draft version is valid, it becomes a customer in the. In the database, in the system. Mehtap Parkinson | 01:17:24 The system. So when you want to create a customer, you submit the customer draft whatever you want to create a discount code you submitcept is routed through all the resources that their entire re. Speaker 2 | 01:17:25 So whenever you want to create a customer, you submit a customer draft. Whenever you want to create a discount code, you submit a discount code draft. So on and so forth. This conpt is repeated through all the resources in commerce schools essentially. Now can anyone tell me just so I see that you haven't just been nodding along and getting tired from all this information. Maybe something landed. If I want to create a new customer based on what I told you, what is the absolute minimum amount of information I have to provide based on what we see here in the documentation? Open question Let's see who. Answer what is the absolute minimum amount of information need to provide to create a valid customer in the system? So which fields are required when creating a customer? Which are. Speaker 4 | 01:18:25 Many ones with the red cross. Speaker 2 | 01:18:28 Exactly with the red asterisk. So we can see that just e mail is required. And that's pretty much. Sorry. There we go. Sorry, I didn't see the chat. It's that's the problem with the chat, it's kind of off center. Yes, Lela and Suzanna, absolutely correct, they both let me know, please. If you suggest your answers, you can do it in the public channel. You don't have to do it privately. It's all good, but because other I want others to see it. But yes, very good answer to both of you. Thank you. The email is the required field. Exactly. Awesome. So that's the basics and we will be going kind of back to this stuff. Mehtap Parkinson | 01:19:02 Be reason. Speaker 2 | 01:19:05 Yes, Lela. Speaker 7 | 01:19:07 Sorry, for some reason the chat is not public like. Mehtap Parkinson | 01:19:08 My s is not public. But I'll try to send it. Speaker 7 | 01:19:10 I tried to send it in the main, but it goes directly to you table here. Mehtap Parkinson | 01:19:11 It. Speaker 2 | 01:19:15 You wouldn't. Okay, yeah, okay, sorry, that's my fault. So we used to use our own accounts for like when someone takes the certification exam, we have to watch them do it and we have to block a bunch of stuff. And I think I forgot to uncheck a box somewhere, and that's why. Okay, so for now, send them to me privately and I will read out the answers. Because unfortunately, this is not something I can change. While the meeting is in progress, I'll just make a note to fix it, hopefully for tomorrow. Mehtap Parkinson | 01:19:43 Progress. I'll. Speaker 2 | 01:19:48 So my fault. Mehtap Parkinson | 01:19:48 So my goss can send messages to it with all of you. Speaker 2 | 01:19:49 Sorry about that. We'll just have to work through it so far, but thank you for checking. If it works, at least I can send messages to everyone, so that's good. I can share the links with all of you. Mehtap Parkinson | 01:20:00 And that's the important point. Speaker 2 | 01:20:00 I guess that's the important part. All right, very good. Already a lot of information, as you can see. Thank you for providing the answers to my questions before we take our break, quick question how is everyone doing so far with the speed, the volume and everything manageable? Mehtap Parkinson | 01:20:08 Thank you for providing questions. So. Speaker 2 | 01:20:23 Awesome. Thank you all for the thumbs up. Wonderful. So like I said, the way we're gonna do this is I'll put a timeround screen. The break will be exactly 15min. Please be back here when the clock reaches zero. Thank you, guys. Enjoy your break. See you back in 15min. Speaker 4 | 01:31:23 Where are you in Moxy? Speaker 8 | 01:31:35 Yeah, I'm taken know where this second floor. Speaker 4 | 01:31:39 Yeah, R&D customer service. Speaker 8 | 01:31:51 That's the first one. Speaker 4 | 01:31:54 Yeah, it depends on what country you're. In. In America the ground floor is the first floor, I think. Speaker 2 | 01:32:10 Yeah, correct. I see Bob got bored and creative during the break. Speaker 8 | 01:35:26 We are using Google Meet in our company, so I'm pretty new to this zoom. Speaker 2 | 01:35:32 Sure. Speaker 8 | 01:35:34 Just op. Al. Speaker 2 | 01:35:45 Right. Looks like everyone's coming back. Keep forgetting how loud this is. Welcome back everyone. Let's see Adrien and MEKTB come back as well. Maybe you go mactubs back finishing a quick lunch or a pizza or whatever. That thing was good. Mehtap Parkinson | 01:36:26 Spanish. Dest. Speaker 2 | 01:36:29 Nice, awesome, enjoy Adrien, are you back? Okay look take ad I still need a moment. That's fine, we're making good time. B screen. Well there you go. One more thing. Since we're waiting. I forgot to mention is when I was mentioning our product portfolio. So we have front end, we have Connect, we have composable commerce. Of course you can get the value pack, let's say, and you can get all of our products in one box, and that thing is called Foundry. So Foundry is essentially a collect of all the products we offer. Backend, frontend, connect check out everything. Well, Checkout is no longer a separate product. You can get it out of the box now with composable cameras. So that's nice. But if you ever see the Word Foundry, that's what it means. It means a package of all Commercetools products in once. Kind of built to help you get out there as fast as you can selling stuff. Well, there you go. Addis back. So maybe just for addiance benefit again, Foundry means all of Commercetools products in one nice package. So just don't be surprised whenever you see this word from around in the documentation or somewhere. That's what it means. All right, one more thing I should mention. On the HGDPA Pi section. Mehtap Parkinson | 01:38:27 Section majority. Speaker 2 | 01:38:27 So we already know if we want to create a new resource, we have to submit a who can tell me? Mehtap Parkinson | 01:38:29 That. Res. We have to submit. Speaker 2 | 01:38:37 Let's for example, if I want to create a new category, what do I have to submit? As in the payload of my API request a draft, a category draft. Very good. Exactly. So just remember that concept with Commercetools when creating something, you submit the draft of that something. Mehtap Parkinson | 01:38:52 Ands retaining something or something natural thought. Speaker 2 | 01:38:56 Now, of course, this is important to you when you're using the API If you're using the Merchant Center, then well, to create a category, you just have you have a form. Mehtap Parkinson | 01:38:57 Of course this is important to you using the AP. Speaker 2 | 01:39:05 You fill out the form and the category is created. That's it. It kind of does that part for you creating the draft and all of that. But it's good to know kind of what happens, you know, on the below the hood, so to speak. So that's creating. And I think a good thing to know how updating resources works. So let's say we have a customer created and we would like to update them. Mehtap Parkinson | 01:39:28 And then we would like to update all of that mention here. Speaker 2 | 01:39:30 Well, of course that's mentioned here on this right side as well. Mehtap Parkinson | 01:39:32 Des right something that's go which still developing something that's gonna be bost request once again because the end of it and what we have to in our request only is the ex of the re. Speaker 2 | 01:39:35 So it shows us that to update something that's going to be a post REQUESTCE again shows us the endpoint and what do we have to include in our request body? It's the version of the resource that we want to update and a list of actions. The version is handled automatically by the system. So when you create a new customer, it has version 1, then you change something and that customer becomes version 2, version 3. Every time something changes with that customer, the version gets incremented. So whenever you want to update a resource using the API, you not only have to specif which resource you're updating so for example, by providing the ID, but you have to say what is the current version of that resource and then what do you want to do with it? So, for example, I want to change the customer's middle name. So that will be an update action. Right? But the interesting thing is this. So the system controls the version. This is not something we can manually change in any way. We can only update the latest version of a resource, obviously. So why do you think? And you can see it's mandatory we have to provide it. Why do you think, whenever updating a resource for the API, do we always have to say what version it is? Why do you think that's the case? Why is that important? Any guesses? Now let me look at the chat. Speaker 8 | 01:41:21 Maybe you're working with different systems that have to has to update the customer information. Mehtap Parkinson | 01:41:26 To have cons. Speaker 8 | 01:41:28 So you always. I'm just going. Speaker 2 | 01:41:33 I like your way of thinking, but I got a private message from someone. Yes, yeah, MEC up put it quite nicely so that people would not be updating the same thing twice. But yes, you're correct when you mentioned two applications. Yes. It doesn't have to be people. It could be applications communicating with your project. Two entities. Let's call them. We don't want two entities updating the same resource at the same time and to not create a conflict. Mehtap Parkinson | 01:41:56 Ities. The same. Speaker 2 | 01:42:03 So that's why. Let's say the latest version of the customer is version 5. If I want to update something on the customer, I say, well, I want to update version 5 of this customer. And Lela wants to update the same customer. So she says I want to update version 5 of this customer with this. And let's say Lela is a faster typer than I am. So she typed in her request, submitted it. Success. She updated the customer. The customer is now on version 6, for example. And then I'm second. I submit my request. I will get an error message because I wanted to update version 5 of the customer, but before I did that Lela updated it to six, so I'll get a 04:09 response saying no, sorry, you're trying to update version 5. The customer is actually on version six, so that tells me alright. The last time I looked at the customer, someone has updated it, so there's a newer version available. Maybe I should have a look at it first and then do my update. So that let's say the scientific term for this is optimistic concurrency control. Mehtap Parkinson | 01:43:04 Ific term for this is altonistic concurrency, but concurrency. Speaker 2 | 01:43:07 So concurrency we don't want like you like MAXP mentioned, we don't want two people editing the same version of the resource at the same time. Very good. So that's why I know for some of you, maybe it goes a bit deeper than you would like. So the main takeaway. And I'm mostly telling you this because there's going to be a quiz very soon. But the main takeaway I want you to have from this portion is that to create a resource, we submit a draft of it. To update a resource, we submit a version and a list of actions. Mehtap Parkinson | 01:43:40 Version or actions along with these two things and dis. Speaker 2 | 01:43:42 Always these two things version andst of actions. So just please remember that and you'll be good. All rightight. Very good. And the final part, the documentation is. Maybe some of you saw this crystal ball up here. This is our very own AI assistant. So instead of just looking for information, what you can actually do is you can ask it a question. For example. Let's see how I did not rehearse this beforehand, so I don't know what's going to come up. This is based on the question one of you asked before. But we'll see. We'll see if AI will take my job or not yet. Okay, it actually did a pretty good job, but I want to keep my job, so I'll explain that to you. But yes. So this is a nice resource. If you have any questions how something works, how to do something, you can use the as and the right hand side actually shows you where it got the information from. So if you want to go to that specific part of the documentation, you can do that as well as at template that defines common characteristics. I get it. Go. Okay yeah, there you go, see my time saved. So yeah the robots are out to get my job now time to update the CV again. Alright, so that's the AI assistant. Any questions about the documentation? Right. So now we know where to find all the knowledge we need. Time to hopefully finally start doing something. And we'll we're getting close to that point. So what we're going to do is we're going to create ourselves a composable commerce project. Mehtap Parkinson | 01:45:50 Ourselves. Speaker 2 | 01:45:54 Actually, one of you already did that I saw in the organization I invited you to. A lot of people ask me, what is a project? Well, a project is basically a container holding a specific configuration of a Commercetools backend. So this is where you're holding not only all your data that you need for your store. So your products, your customers, your categories, discounts, prices, all that stuff, but where all the logic sits, how those things chuck together and so on. Mehtap Parkinson | 01:46:23 Price together and so on. So. Speaker 2 | 01:46:30 So that whole thing that in a bubble is a project. And you can have many projects if you want, but of course, only one of them would be what we call a production project, which is an actual backend for an actual store somewhere. Mehtap Parkinson | 01:46:40 Actual bucket somewhere you know the production that. Speaker 2 | 01:46:43 But you know, maybe you want to have a project for testing, for training, for doing some other stuff, and then just the production project you just updated it once you have everything else tested. So that's what we're going to be messing around with. So very soon I'm going to show you how to create a new project. Mehtap Parkinson | 01:46:58 I can assure you how to create a new projects. Speaker 2 | 01:47:02 But once we have a project created, we want to access it somehow. So first of all, there's different paths you can take to communicate with a project. Mehtap Parkinson | 01:47:10 You can take to communicate with the project. You can see here on be have each can city AP request like to give customer by customer who helling through the store. Speaker 2 | 01:47:12 You can see here we have the HTTP API endpoint. This is the one where we send all of our HTTP requests like creating a customer, updating a customer. We always send it through this door. Of course, we don't allow just anyone off the streets to communicate with our project because that will be, you know, stupid and unsafe. Mehtap Parkinson | 01:47:27 Just anyone on the street still for it like you know people need to it needs to have an attached to an. Speaker 2 | 01:47:33 So you have to be authorized, which means that whenever a request is sent to commerce stores, it needs to have a token attached to it. A token is generated by this endpoint where you set your credentials. Those credentials are basically a cost a ID and secret, and based on that a token is generated. Mehtap Parkinson | 01:47:51 Basically very ID and secret and gener says yes to something in the apr development has specific conditions. Speaker 2 | 01:47:57 Says yes, you are authorized to do something in the API and you can even manage what specific permissions, that token can allow you to access. So we'll see that in a few moments. So you then attach this token to your request. That what? How the system knows you're allowed to do certain things in it. Mehtap Parkinson | 01:48:17 Without some moment. Speaker 2 | 01:48:17 We have some more. For example, we have the import API as well. Mehtap Parkinson | 01:48:18 For example, we have the endpoint 8 next one. Speaker 2 | 01:48:21 This endpoint is used well, as you can probably guess by the name to import data in bulk because using the HGTP API you can only manage one resource at a time. Mehtap Parkinson | 01:48:21 This one point is used. One you can probably get by you only men. One resource at a time. So for example. Speaker 2 | 01:48:31 So if, for example, I want to add 20 products to my project, I would have to make 20 separate API requests. Mehtap Parkinson | 01:48:33 I want request. Speaker 2 | 01:48:41 But if I use the import API, I can just do them all in one request and just in bulk. Mehtap Parkinson | 01:48:41 If I. Speaker 2 | 01:48:46 Import 20 products. But we'll talk a bit more about the import API maybe closer to the end so we know what the endpoints are. As you can see, they can be in different regions as well and on different cloud platforms. So you can see an example here. EUROPWST 1 Google Cloud. You can have AWS for example. Mehtap Parkinson | 01:49:05 For. Speaker 2 | 01:49:07 The list of available regions is available in the documentation. You don't need to know specifically where it is. You can ask the AI assistant or you can use the search functionality. So let's see who will be the first person to tell me in how many regions can your project potentially be deployed in? How many do we have available? What are the options? Okay, Bob was first. Bob said. Five. We find a browser somewhere, there we go. So the quickest way is just type in the word regions and see what comes up. And yes, it looks like we got five. Bob is correct. Antonina. Actually, you know what? This private thing is nice because the rest of you don't know that. Bob gave me the answer. I can still get answers from more people. Maybe I'll just keep it like that. So there we go. So yeah, the available regions currently, this is all subject to change. You know, we might open up a new region in China, we might open up a new one in South America or in Africa or somewhere. Who knows. All depends on customers' requests. But the ones we have right now is Google Cloud in North America, AWS in North America, Google Cloud in Europe, AWS in Europe and Google Cloud in Australia, so you can have your project hosted in any of these regions where it will be hosted. It all depends, well, basically on what you prefer. Usually it's based on where is your audience or where are you located and you wanted to be hosted as close as possible to those people. Mehtap Parkinson | 01:51:00 Or where are you thinking that you wanted to make cost as goals as possible to those people? Speaker 2 | 01:51:06 Sometimes maybe for legal reasons, you want to have it hosted in a specific place because, for example, you know, Europe has some very specific personal data processing laws, and maybe to avoid some of that hassle, you want to host it in North America or something like that. Mehtap Parkinson | 01:51:06 That may be one reasons you want to have host in a specific place because for example, you know you not any specific in the process was too. Speaker 2 | 01:51:25 But in general, it's up to you. We do not support multi regional deployments. Mehtap Parkinson | 01:51:29 We do not projects at the same time, but it can only be in one. Speaker 2 | 01:51:31 So your project cannot be deployed in two regions at the same time. It can only be in one. Mehtap Parkinson | 01:51:38 So. Speaker 2 | 01:51:38 So just so you know that is the case, right? Mehtap Parkinson | 01:51:39 Yes. So. I think you know that. That is. Speaker 2 | 01:51:45 So once we know where our project is, how we can access it. Now what tools do we have to talk with our project? One of those tools is the Merchant Center. So the Merchant Center is available under mc. Commercetools.com, but it defaults meets the Europe region. So let's make sure everyone has access to the Merchant Center. Can you please check if everyone can access this link? From what I've seen, I think all of you have access to the merchant center. Mehtap Parkinson | 01:52:17 Would you see? I think all of you have access to. Speaker 2 | 01:52:20 Definitely. The people who work here on Friday have access because we tested it. But I think the other three did. And the other, the three people who were not here and fight it, they're all from Commercetools, so I'm pretty sure they have access to it. But let's just confirm. So you should see this when you go to that link that I sent you. Mehtap Parkinson | 01:52:40 See this when you go to that and see our project. Speaker 2 | 01:52:44 You should see our demo project that I've created. If you forgot your password or something, of course you can choose the forgotta password option. Mehtap Parkinson | 01:53:00 Now to me something else that she was supposed to sleep there earlier. Speaker 2 | 01:53:00 Now it's showing me something else that you're not supposed to see. There we go. All right, can I get a fumbs up on screen? If everyone has access yes okay Max was doing this so I wasn't sure but okay thank you good amgmola are you in? Mehtap Parkinson | 01:53:11 Every. Okay let this so. Speaker 2 | 01:53:27 Okay, thank you. Sorry, you didn't see your feet there, I had to move a thing. Thank you. Awesome. So this is what the Merchant center looks like when you're looking at a specific project. Mehtap Parkinson | 01:53:37 You can see here. Speaker 2 | 01:53:37 You can see here there's quite a few options. Mehtap Parkinson | 01:53:38 So quality of options here, the dashboard we can customize and we can kind of see some. Speaker 2 | 01:53:39 We have a dashboard where we can customize it. We can kind of see a summary of how our store is doin