""For example, we used to spend 1-2 months physically building secure environments," he wrote. "In the current Flava security environment, resources can be provisioned in minutes, but accessing those servers can still require roughly 10 separate workflows, such as creating VDI accounts or setting up Box folders for data exchange. Because these steps involve approvals, the end-to-end lead time can still be as long as two months.""
""Because these platforms don't yet provide a unified "cloud experience," developers often have to learn separate ways to handle things like permission management, logging and monitoring, metering and billing, APIs and CLIs, UIs, approvals, and multi-region/availability zone (AZ) capabilities, platform by platform," wrote Young Hee Park, a cloud service lead at LY Corp. LY Corp has therefore decided to build "shared foundations" that mean all the platforms its developers need to develop services will be delivered from an internal private cloud, with a consistent UX."
LY Corporation, formed from the 2021 merger of LINE and Yahoo Japan, operates an internal private cloud called Flava while the two brands still use separate tools. Developers face inconsistent permission management, logging, monitoring, metering, billing, APIs, CLIs, UIs, approvals, and multi-region/AZ capabilities across platforms. LY will pursue "Flavaization" to create shared foundations delivering platforms from a unified internal private cloud with a consistent developer experience and will adopt AIOps. Leadership aims to complete major work within one to three years. Current challenges include long lead times caused by multi-step approval workflows despite faster resource provisioning.
Read at Theregister
Unable to calculate read time
Collection
[
|
...
]