The CTO of a company I have worked for used to say that services should be loosely coupled but tightly integrated. I didn’t realize until a lot later how true that statement is as you’re building out microservices. How those microservices communicate with each other has also changed quite a bit. More often than not, they send messages using asynchronous protocols. As an industry, we decided that this new way of building apps should be called “Event-Driven Architecture (EDA).

As a developer, I always thought that security, like documentation, would be done by someone else. While that might have been true in the past, in today’s world that model no longer works. As a developer you’re responsible for the security of your app. Security in this case should be seen in the broadest sense of the word, ranging from licenses to software packages. A chef creating cheesecake has similar challenges. The ingredients of a cheesecake are similar to the software packages a developer uses. The preparation is similar to the DevOps pipeline, and recipe is similar to the licenses for developers. Messing up any of those means you have a messy kitchen, or a data breach!

If you’re using AWS CloudFormation as your Infrastructure-as-Code, you can have those events show up in dashboards from Wavefront, so your entire DevOps organization now knows what happened and which CloudFormation stack to look at. This could save time while debugging and figuring out where the issues might come from. If you’re part of a DevOps team that deploys using AWS CloudFormation and you want insight into the deployment events.

Trusting Your Ingredients - What Building Go Apps And Cheesecake Have In Common.

In this lightning session at GopherCon 2019, I got the chance to talk about two things I love. Cheesecake and Golang! As a developer, I’ve written code and built apps, and I realized that building apps and creating a cheesecake have a lot in common. In both cases you need to have the right ingredients, you need to trust your suppliers and have transparency in your production process. In this talk, we’ll look at how you can, and why you should, know what is in the app you deploy.

Go modules are here to stay and it’s about time to start modularizing your code. During the meetup at the Go UserGroup in Atlanta we spoke about:

• What Go modules are and why you need them
• The benefits are of using modules
• The differences between modules and the things we did before that
• What you need to do to “switch” to modules.

Go modules are here to stay and I got the chance to talk to the Atlanta chapter of Woman Who Go on what Go modules are and how you can switch to use them.

As a developer, I’ve written code and built apps, and I realized that building apps and creating a cheesecake have a lot in common. In both cases you need to have the right ingredients, you need to trust your suppliers and have transparency in your production process. I got to go to Atlanta and meet with the Docker Meetup Group there, where we got to talk about In this talk, how you can, and why you should, know what is in the app you deploy.

In my talk “Duct Tape and String: Continuously Delivering Serverless Microservices” at swampUP 2019, I got to talk about some best practice for the project that got me excited about both serverless and K8s: OpenFaaS! For me that meant I got to combine a lot of the things I care about (Containers, Serverless, and Golang), while talking about the awesome possibilities that using Artifactory brings you.

The Continuous Delivery Foundation had a colocated event at KubeCon + CloudNativeCon EU 2019 in Barcelona and The New Stack was there to report it. The day featured some awesome sessions from different companies that are part of the founding team of the foundation. I was honored to be interviewed by B. Cameron Gain and that made it into his article on The New Stack.

In some cases you might want to get some data from cloud based systems to an environment that doesn’t expose APIs or ports to the outside world. Using webhooks makes that a little easier, but you still need a system that accepts webhooks and is able to get them across your firewall. That is exactly where Solace PubSub+ Cloud comes in! I’ve built a small webhook forwarder app, that gets data from Solace and sends it onwards without having any of my systems exposed to the Internet.