In the past few years containers and orchestrators, like OpenShift, have enabled developers to release API-driven services faster than ever. Developers are able to package their code as a container, expose their endpoints as Kubernetes services, and the orchestrator would do the rest, right? Not quite so. There are a lot other concerns that developers and operators need to take into account before exposing their APIs to the world.
How are users going to access my services from outside my cluster? How can I make sure that they are properly authenticated and have the needed permissions? Am I able to trace requests as they go through the different services? How can I debug potential problems happening in production?
In this webinar, Ara Pulido, Technical Evangelist at Datadog, and Daniel Bryant, Product Architect at Ambassador Labs, will explain how combining an edge proxy and a good observability strategy is the key to being successful when creating API-driven services or public APIs.
You’ve probably written a hundred abstracts in your day, but have you come up with a template that really seems to resonate? Go back through your past webinar inventory and see what events produced the most registrants. Sure – this will vary by topic but what got their attention initially was the description you wrote.
Paint a mental image of the benefits of attending your webinar. Often times this can be summarized in the title of your event. Your prospects may not even make it to the body of the message, so get your point across immediately. Capture their attention, pique their interest, and push them towards the desired action (i.e. signing up for your event). You have to make them focus and you have to do it fast. Using an active voice and bullet points is great way to do this.
Always add key takeaways. Something like this....In this session, you’ll learn about: