Wix Engineering’s Post

Platform as a Runtime? Is this the Next Step in Platform Engineering? 🤔 Lessons learned from Wix developing and operating 4000 microservices - an excellent write-up by Aviran Mordo 🪐 VP eng. Takeaways: ▶️PE today is focused on CI/CD and getting started experience. We expanded this problem by building Platform as a Runtime (PaaR). ▶️ Complex environments demand standardized coding practices. We translated these into an opinionated development platform. ▶️ We automatically take care of most of the system's cross-cutting concerns. For example, encryption of PII fields, handling GDPR, and more. ▶️ Additionally, any new feature added to the platform is automatically available and active on all services built within the platform, saving cross-company efforts. ▶️ Should you build your own PaaR? Only after you scale to thousands of microservices, you could start building a platform. My thoguths: ▶️ Having watched Aviran’s #QConLondon talk on the same topic, this is a demonstration of the value a runtime brings to large-scale microservices-based deployments. ▶️ Many of the goals (let developers focus on writing business logic), features (cross-cutting concerns of distributed apps), architecture (sidecar, shared sidecar), and direction (polyglotism) the Nile project is undertaking are the exact same goals of Dapr. ▶️ Wix is a huge company with custom needs for a custom PaaR. Not every organization can and should build their own PaaR as Wix can (nor build their own Kubernetes). For many organizations, @daprdev will get you to 80%. As Aviran said: “the most crucial KPI for the platform team is developer adoption." If developers aren't using your platform, it might not be delivering enough value. Check out Dapr to see for yourself. QConLondon talk https://lnkd.in/e27Cn_q3 The Full post here https://lnkd.in/eRbzZ2iy