Is this you? As a journalist, you can create a free Muck Rack account to customize your profile, list your contact preferences, and upload a portfolio of your best work.
Claim your profile
Articles by Mor Paz
How to create a custom Ocean integration in Port
{{survey-buttons}} Get your survey template today By clicking this button, you agree to our Terms of Use and Privacy Policy {{survey}} Download your survey template today By clicking this button, you agree to our Terms of Use and Privacy Policy {{roadmap}} Free Roadmap planner for Platform Engineering teams Set Clear Goals for Your Portal Define Features and Milestones Stay Aligned and Keep Moving Forward Thank you for registering! Create your Roadmap By clicking this button, you agree to our...
How to Upgrade Your Start-Up to an Enterprise?
Let’s start with a few introductions. Welcome to Port. After years of pain working in siloed, chaotic Developer teams and infrastructures, we created the solution we should’ve had all along. Port is a Developer Portal that brings everyone together. It serves as a one-stop-shop for engineering teams to get a complete view of their environment. We’ve interviewed over 150 companies with different backgrounds and profiles to learn how they handled DevOps.
Drive Developer Self-Service with Crossplane, K8s and a Portal
Drive Developer Self-Service with Crossplane, K8s and a Portal sponsor-port,sponsored-post-contributed, Image from Peshkova on Shutterstock.
APIs using an Internal Developer Portal
Manage your APIs using an Internal Developer Portal An API Catalog should be housed in an Internal Developer Portal as it is built to abstract away complexity for dev teams The best description for an API catalog is quite simply a highly organized library of APIs. Just like picking out a book in an actual library, the catalog makes APIs easily discoverable so that the developers and engineering leaders who need to use them can do so with ease.
API Management News, Analysis and Resources
Introduction to API Management API management, a critical aspect of modern digital architecture, involves overseeing the lifecycle of Application Programming Interfaces (APIs) in a secure, scalable environment. It is the process of creating, publishing, maintaining, and securing APIs, a set of protocols and tools for building and integrating application software. API management is integral to businesses seeking to enhance operations and connectivity in the digital realm.
Using a Developer Portal for API Management
An API catalog is like a super organized library where you can easily find and use different APIs. Private API catalogs include all internal APIs used within an organization. This optimizes API management by identifying redundant code and promoting adherence to organization-wide standards. A private API catalog acts as a centralized repository for all internal APIs, affording comprehensive visibility into an organization’s API landscape.
How to Create an Internal Developer Portal MVP
What needs to go into an internal developer portal and how should it be set up by platform engineers and used by developers? This post will take a practical approach to building a portal minimum viable product (MVP), assuming in a GitOps and Kubernetes native environment. MVPs are a great way to get started with an idea and see what it can materialize into.
Data Model for an Internal Developer Portal With Git and Kubernetes
{{cta}} Book a demo right now to check out Port's developer portal yourself {{jenkins}} It's a Trap - Jenkins as Self service UI {{gitops}} How do GitOps affect developer experience? {{ebook}} It's a Trap - Jenkins as Self service UI.
Using Pulumi With an Internal Developer Portal
Infrastructure as code makes life easier both for devops and developers. It gives them a way to create infrastructure that is standardized and reproducible. It shortens time spent creating a new environment and provisioning resources, since it is easy to add new variables or edit files, letting you prototype new infrastructure in a faster, easier and safer way.
Building an Internal Developer Portal for a Serverless Architecture
This post covers how to set up and use an internal developer portal to support the software development life cycle in a serverless architecture. The core pillars of an internal developer portal for serverless Let’s review the core pillars of an internal developer portal in the context of a serverless architecture: The software catalog stores all of the information and maps your infrastructure and assets from an engineering, infrastructure, DevOps and developer standpoint.
self-service actions using infrastructure as code and GitOps
GitOps and the developer experience Why is the intersection of GitOps, infrastructure as code and the developer experience difficult? Truth is that GitOps can be pretty daunting for developers. From the developer point of view, it requires a deep understanding and familiarity with DevOps practices. From the DevOps point of view, it requires a high degree of trust because whatever is committed into the git repository and then exists on the main branch becomes the actual architecture.
Internal Developer Portals and Kubernetes: What You Need to Know
Introduction The rise of cloud native and kubernetes created an increase in the complexity that developers need to be aware of in their ordinary flow of work. This presents more tasks and cognitive load, affecting productivity, and also making it difficult for developers to understand where their apps are running, what is deployed where and whether any changes are required for services to run as they should. DevOps lives aren’t necessarily easier either.
Show More
loading
Actions
Is this you?
As a journalist, you can create a free Muck Rack account to customize your profile, list your contact preferences, and upload a portfolio of your best work.Get in touch with Mor
Contact Mor, search articles and posts on X, monitor coverage, and track replies from one place.
Learn more about Muck Rack