After working on a new feature or an improvement, it's normal that you want to deliver these changes to your users as fast as possible. Depending on your deployment pipeline, confidently deploying changes to production might include coordinating with whoever is leading on-call, getting their approval, manually deploying your changes, spending hours to monitor how it goes, and performing a rollback in case something goes wrong.
A service mesh is a dedicated infrastructure layer that manages traffic, also known as communication, between services in applications composed of containerized microservices. It is a critical component in a microservices architecture, responsible for the secure, fast, and reliable communication between services. This article answers a lot of the questions you may have about service meshes: What are they and how do they work? Who is using them and why?
As a cloud service provider, observability is a critical subject as it's strongly related to the availability of the services running on the platform. We need to understand everything that is happening on our platform to troubleshoot errors as fast as possible and improve performance issues. A year ago, while the platform was still in private beta, we faced a tough reliability issue: users were facing random 500 errors when accessing their applications.
On August 15, 2022, we learned the shocking news that free Heroku Dynos, Heroku Postgres and Heroku Data for Redis will no longer be available and existing services will either need to upgrade to a paid service or find another hosting solution by November 28, 2022. Since its conception, Heroku has changed the way developers, hobbyists, students, and indie hackers deploy applications.
An API gateway is a server that sits between your backend services and your users. It provides an abstraction layer that helps you manage the communication between clients and your services. API gateways are a single point of entry into a microservices application and they work like a reverse proxy: They receive API calls from clients, route them to the right microservices in the backend, and return aggregated responses to clients.
Today, we are super excited to share that the Koyeb platform is available for everyone in public preview. If you don't know us yet, Koyeb is the developer platform to build, deploy and scale full-stack applications where your users are. We've been working on the platform since early 2021. The private preview has been intense with over 10,000 developers joining the community and now over 3000 applications running on the platform.
While writing a comparison of Kubernetes and Koyeb, we tried to determine how much operating a Kubernetes cluster really costs. This section of our comparison took us hours to write and ended up being so long that we decided to write a dedicated post about it. Full disclaimer: At Koyeb, we're building a serverless platform and we have a purpose-built orchestration engine.
If you still rely on big-bang deployments or are ever afraid to break your production environment when you push changes, then it is seriously time to invest in building a strong CI/CD pipeline. Pushing changes quickly and often is critical. The best way to mitigate the risks of new releases is to have a strong deployment strategy in place. Continuous deployment automates the deployment process, which lets you deliver new features and improvements to your applications faster than before.
Here at Koyeb, we're kind of crazy about providing the fastest way to deploy applications globally. As you might already know, we're building a serverless platform exactly for this purpose. We recently wrote about how the Koyeb Serverless Engine runs microVMs to host your Services but we skipped a big subject: Global Networking. Global Networking is a big way of saying "How are my requests processed?".
We're kind of crazy about providing the fastest way to deploy applications globally. As you might already know, we're building a serverless platform exactly for this purpose. We recently wrote about how the Koyeb Serverless Engine runs microVMs to host your Services but we skipped a big subject: Global Networking. Global Networking is a big way of saying "How are my requests processed?". A short answer is: requests go through our edge network before reaching your services hosted on our core locations.
