This Feb my good friend Tom Davies (thodavie ) and I will be holding a session on Serverless Architectures. If you are so inclined, you can register for it here. We've been working pretty hard over the last year on a serverless solution we hope to demonstrate as part of this talk. Here's what we want the audience to walk away with:
Serverless will become the new normal
Regardless as to whether you use someone else's serverless services or something crafted by yourself, most developers will gravitate and be happier working in a world where infrastructure is completely automated and code drives the world. Why? Simple, less work! Wouldn't you rather work on fun creative stuff than mind numbing nastiness of "spin up a VM", "install the operating system", etc.
But wait you say! I don't use VMs! We are advanced! We use containers! Sure. Well then now you need to worry about getting the right container image, building the Dockerfile, etc. Even if you are a big fan of Kubernetes (like I am) it's still a royal-pain-in-the-everywhere to get an infrastructure like that set up. A serverless architecture probably runs with containers and needs something like Kubernetes underneath the hood, but what if you didn't have to do all that?
What serverless offers is a layer of abstraction on top of something like Kubernetes. This can include prebaked functions as a service, or code snippets already created for you that you can incorporate into your own application.
Serverless is more than just the services offered by one giant cloud provider
We want to show that you can create your own serverless service that lives in your own datacenter (or any datacenter) and that's what we have prepared for you. It's simple, doesn't work very well, and has a long way to go, but we want to show you that the concepts are something an enterprise can actually use to make their own developers more productive.
We are trying to tackle a simple problem: People want to try making their own Sparkbot to respond to simple commands like "/sayhello" where the sparkbot account might say "hello back to you". Making a sparkbot isn't as easy as it could be. You have to write lots of code, then find a place to host it, then autoscale it if needed, then baby it. Making changes might require you to set up a CI/CD pipeline or figure out your cloud provider's way of updating. If you are brand new to making sparkbots, this could take you about a week if you had average experience.
We created a serverless platform called Pipeline that attempts to automate most of that part for you and all you have to do is enter the code you want run. From there, we handle the rest! The scaling, the maintenance, etc. We hope to have a pretty neat demo for you in Feb. See you in Berlin!
We can't fetch more than 3000 users using /list-people and pagination API due to API limitation.https://developer.webex.com/docs/api/v1/people/list-people Is there any workaround which returns users beyond limit 3000 using any API request?
Hey everyone,Trying to get the SOAP API to respond nicely to my getPhone request but it is not letting me in. I've tried so many possible combinations of the namespace and the header, and it still gives me an error message stating "Message: Wron...
Hi, I am trying to build a program to create WLAN profile report querying prime with API, 'GET WlanControllerDetails' API resource provides all the rich information like AP groups, listing all the SSID in AP groups, management interface IP address, WLC na...
Hello, We have Cisco Packaged Contact Center Enterprise in our organization. I've been tasked to see if there is any way to pull the incoming call phone number while the caller is waiting in the queue or from the Cisco inbound switch. Once we pull th...