api gateways

In a new episode of Semaphore Uncut, Solo.io founder and CEO Idit Levine (@Idit_Levine) shares insights on what’s next in service mesh solutions. We dig into the importance of network for distributed systems, the evolution of API gateways, the cutting edge of service mesh infrastructure, and more. Idit was very kind to share many details from her journey in discovering and developing Solo's products.

Key takeaways:

1. When everything is distributed, everything has to go on the network wire.
2. Gloo is a feature-rich, Kubernetes-native ingress controller, and next-generation API gateway.
3. Service Mesh Hub lets you group multiple service meshes into one virtual service mesh that you talk to.
4. WebAssembly Hub is a place for the community to share and consume service mesh or API gateway extensions.

About Semaphore Uncut
In each episode of Semaphore Uncut, we invite software industry professionals to discuss the impact they are making and what excites them about the emerging technologies.

SHOW: 397

DESCRIPTION: Brian talks with Matthew Creager (@matt_creager, Co-Founder & VP Developer Relations @manifoldco) about the challenges of cloud silos, connecting apps to multiple cloud services, the importance of collaboration beyond just coding, and how Manifold makes it simpler to integrate apps to align to business needs. 

SHOW SPONSOR LINKS:

• Digital Ocean Homepage
• Get Started Now and Get a free $100 Credit on Digital Ocean
• Snowflake Homepage
• Get started with Snowflake at snowflake.com/cloudcast
• Get 20% off VelocityConf passes using discount code CLOUD

CLOUD NEWS OF THE WEEK:

• Red Hat launches OpenShift 4 - Enterprise Kubernetes
• Microsoft and Red Hat launch Azure Red Hat OpenShift managed service

SHOW INTERVIEW LINKS:

• Manifold Homepage - Find, organize and connect the best cloud services

SHOW NOTES:

Topic 1 - Welcome to the show. Tell us about your background prior to Manifold, and what motivated you to focus on this new model of application development and integration.  

Topic 2 - I know one truth about developers, that they prefer things to be simple or taken care of for them. Beyond that, I’m not sure of any absolute truths. It seems like Manifold is somewhere near the intersection of Low-Code and PaaS and Integration Services (API Gateways or Middleware) and CI/CD. Beyond simplicity, how do you describe what Manifold does? 

Topic 2a - What is the interaction between the Manifold services and Prefab.cloud services? 

Topic 3 - I really like the idea of shared projects and shared billing. How much do you find that overlapping or re-inventing slows down developers? 

Topic 4 - Can you help us understand the business model or community model? 

Topic 5 - Can you share any examples of how Manifold has helped companies and teams accelerate their application development models?

FEEDBACK?

• Email: show at thecloudcast dot net
• Twitter: @thecloudcastnet and @ServerlessCast