Explore >> Select a destination
|
You are here 
|
www.warpstream.com | ||
| | | | |
streamnative.io
|
|
| | | | | To satisfy the need for modern streaming data pipelines, we developed Apache Pulsar with a cloud-native architecture designed to significantly enhance the platform's horizontal scalability. We didn't just improve it; we revolutionized it, boosting Apache Pulsar's elasticity by 100x to even 1000x, compared to other data streaming technologies such as Apache Kafka. This blog post outlines what exactly we did to achieve such a leap in performance. | |
| | | | |
0x65.dev
|
|
| | | | | Our Journey to Microservices, Kubernetes and beyond. | |
| | | | |
doordash.engineering
|
|
| | | | | Learn how DoorDashs engineering teams use a service mesh to realize data transfer cost savings without sacrificing service quality. | |
| | | | |
tomasvotruba.com
|
|
| | | In a post from autumn, we looked at how to [develop packages in monorepo on PHP 8.1 and release a downgraded version on PHP 7.2](/blog/how-to-develop-sole-package-in-php81-and-downgrade-to-php72/). But having 2 repositories to work with still feels crappy. Which one should we use? Where do people contribute? Where do we report issues? Everyone needs clarification, and **time is wasted on explaining complexity**. I knew we could do better... we want **one repository**. Today I'll show you how to get there with 39 lines of GitHub Action workflow (including comments). | ||
