Cloud 5 Adobe App Builder

Transcript

Hey, James. Hey, Darin Good to see you. Can you believe that - It’s been a full season of Cloud Five? You know, Darin - some stories don’t have a clear beginning, middle or end. You’re right. For our final episode, - I like to bring on our second ever guest. And his name is. What’s up, fellas? Thanks for having me back. I was thinking we can talk about clouds. Did you know that clouds can form - in a number. Of different.

Welcome, Amol Who is that guy? What’s he doing on the beach? So Amol - What are we going to talk about today? We going to talk about Adobe App Builder. So why are we talking about App Builder? What is it? Tell us more. - Sounds interesting Amol Yeah. So Adobe App Builder is a way to extend - AEM in a cloud native way moving forward. Right. - So there’s two types of extensibility. One is middleware extensibility. Another one is core services. So middleware meaning, you know, if you - have CIF components that require graphQL but your legacy commerce system - supports rest and doesn’t support graphql, you need something in the middle - to kind of convert the two. That’s 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 is used for these two use - cases. Yeah. Sounds like sounds like the future. How do I get started? - Where can I learn more? There’s 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’s pretty easy to get started So I would - encourage everyone to check it out.

So I’m all - 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’s - 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’s happening. You can get the you can get the activation - using the get command. In other cases, you can add a header for extra logging and turn it on and you can also get logs. Yeah, this is great stuff Amol. What do you think? It’s just this probably isn’t something we should use in - a production environment, is it? Correct. So the 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 Amol, 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’s two types of actions, - web actions which you can access through a URL. That has a limit of 60 seconds. So that’s more synchronous and then non web actions which you can not - 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’s 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. So those two ways would be able to do - you would be able to actually achieve what you’re 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 I need more memory - or whatever is defined by default? Yeah, that’s a good question. There’s a URL that I will 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, - you know, increase the memory to so much. I want to increase the time after so much it for each action, depending on - what the what that action does.