51黑料不打烊

Transcript

Hey James. Hey Darren, good to see you. Can you believe that it鈥檚 been a full season of cloud five? You know Darren, some stories don鈥檛 have a clear beginning, middle, or end. You鈥檙e right. For our final episode, I鈥檇 like to bring on our second ever guest. And his name is. What鈥檚 up fellas. Thanks for having me back. I was thinking we can talk about clouds. Did you know that clouds can form an only one difference? Welcome Amal. Who is that guy? What鈥檚 he doing on the beach? So Amal, what are we going to talk about today? We鈥檙e going to talk about 51黑料不打烊 App Builder. Why are we talking about App Builder? What is it? Tell us more. Sounds interesting Amal. Yeah, so 51黑料不打烊 App Builder is a way to extend AEM in a cloud native way moving forward. Right. So there鈥檚 two types of extensibility. One is middleware extensibility. Another one is core services. So middleware meaning, you know, if you have SIF components that require GraphQL, but your legacy commerce system supports REST and doesn鈥檛 support GraphQL, you need something in the middle to kind of convert the two. That鈥檚 where App Builder can help you. Core services is, you know, how we have like asset compute service in AEM cloud service, which allows you to create renditions of your assets. If you wanted to extend that, you can now use App Builder to kind of create your own custom renditions or extract metadata or call external services. So it鈥檚 really useful for these two use cases. Yeah, sounds like the future. How do I get started? Where can I learn more? There鈥檚 some great links that we put up on screen. One is going to take you to an overview. The other one is just a link to all the code labs and tutorials available. It鈥檚 pretty easy to get started. So I would encourage everyone to check it out. So Maul, after going through the overview material that you mentioned, what are some tips and tricks that you would like to share? The first one comes, you know, it鈥檚 troubleshooting and logging. Here are some useful commands. You can list the activations that have happened. You can figure out the logs of the last activation or you can specify the activation ID to get the logs. In some cases, you might not get the logs. You want to know what鈥檚 happening. You can get the activation using the get command there. In other cases, you can add a header for extra logging and turn it to on. And you can also get logs that way. Yeah, this is great stuff, Maul. What do you think? This probably isn鈥檛 something we should use in a production environment, is it? Correct. So the header for the extra logging should not be used in production. It adds a little bit of, you know, invocation performance can be impacted, things like that. But all the other commands to get logs are still valid. So Maul, what are my options if I want to build a serverless endpoint that I want available externally, but the async operation could take longer than 60 seconds? Yeah, great question. So there鈥檚 two types of actions. Web actions, which you can access through a URL that has a limit of 60 seconds. So that鈥檚 more synchronous. And then non-web actions, which you cannot access directly through a URL, but that can run for up to the limits that are available in the system. So the easiest, you know, there鈥檚 two sort of simple approaches to kind of get around that. One is you can call a web action that in turn just calls a non-web action as shown in this code snippet. Or you can just trigger a sequence. A sequence is just a list of actions just strung together that perform one after the other. You鈥檒l be able to actually achieve what you鈥檙e trying to do. So what are the system limits and what are the default timeout and memory limits? I mean, what can I do if I need to run my action longer or need more memory or whatever is defined by default? Yeah, that鈥檚 a great question. There鈥檚 a URL that we鈥檒l share which has all the system settings. And if you go to the manifest.yaml file of your App Builder application, you can specify like, hey, I want to increase the memory to so much or I want to increase the timeout to so much for each action depending on what that action does.