柑橘類

GitHub - rtomayko/ronn: the opposite of roff the opposite of roff. Contribute to rtomayko/ronn development by creating an account on GitHub.

github.com/rtomayko/ronn

The actual bottlenecks were, and still are, code reviews, knowledge transfer through mentoring and pairing, testing, debugging, and the human overhead of coordination and communication.

LLM はコードの生成はするが，このあたりがボトルネックなのは依然として変わりない，という話

Writing Code Was Never The Bottleneck LLMs make it easier to write code, but understanding, reviewing, and maintaining it still takes time, trust, and good judgment.

ordep.dev/posts/writin...

グローバル展開にむけたアプリと基盤の再構築 | メルカリエンジニアリング Cross Border (XB) Engineeringの @deeeeeeeeeet です．先日の事業戦略発表会において共有しましたが，今後更にメルカリの海外展開を加速させるためにグローバル版のメルカリアプリを先日リリースしました．この

engineering.mercari.com/blog/entry/2...

G1 の方が適したワークロードもありつつ，全体的に Generational ZGC の恩恵が大きいということか

Bending pause times to your will with Generational ZGC The surprising and not so surprising benefits of generations in the Z Garbage Collector.

netflixtechblog.com/bending-paus...

Instead of only trying to prevent failure at every level of the system, we had to accept that no action on our part—no matter how heroic—could prevent all failures. We had to invest in not only preventing failures, but also in failing better when they inevitably occur.

we identified a pattern in our systems design that needed to change: we had built with the assumption that the only way to handle failure was to prevent it entirely—or to stop everything—rather than finding ways to degrade gracefully and continue delivering value to customers

Failure is inevitable: Learning from a large outage, and building for reliability in depth at Datadog | Datadog After a major outage, we re-architected Datadog systems to degrade gracefully under failure. Here's what we learned—and how we’re building forward.

www.datadoghq.com/blog/enginee...

Command Line Interface Guidelines An open-source guide to help you write better command-line programs, taking traditional UNIX principles and updating them for the modern day.

clig.dev

ZGC is not yet supported. We intend to address this limitation in future work.

効果的な cache を作るためには training run でいかに production run 相当の振る舞いをさせるかがポイント．

With the AOT cache, ... work that the JVM would usually do just-in-time when the program runs in the third step is shifted ahead-of-time to the second step, which creates the cache.

the program starts up faster in the third step because its classes are available instantly from the cache.

To create a cache takes two steps. First, run the application once, in a training run, to record its AOT configuration

Second, use the configuration to create the cache

Subsequently, in testing or production, run the application with the cache

Lay a foundation for continued improvements to startup time and also to warmup time, i.e., the time required for the HotSpot JVM to optimize an application’s code for peak performance.

openjdk.org/jeps/483

Profiles cached during training runs do not prevent additional profiling during production runs. This is critical, since an application's behavior in production can diverge from what was observed in training.

We can improve warmup time by collecting profiles even earlier, in a training run of the application.

We extend the AOT cache, introduced by JEP 483, to collect method profiles during training runs.

openjdk.org/jeps/515

Ultimately, platform engineering is about balancing developer velocity with robust governance.

Manual checkpoints are processes that require human oversight to ensure a platform tenant's activities, such as a major deployment or new architectural design, align with compliance and governance requirements.

A safety net is a reactive control that activates after an error or failure has already occurred. Its purpose is not to prevent the initial event, but to detect the problem, mitigate its impact, and facilitate a swift recovery.

A guardrail doesn't consider a developer's immediate goal or speed; it only cares about preventing an action that could compromise the entire system.

Golden paths aren’t about preventing bad behavior with a wall, but about encouraging good behavior via a well-paved, high-speed lane.

Platform engineering control mechanisms | Google Cloud Blog Learn how to control the platform engineering application lifecycle with golden paths, guardrails, safety nets, and manual checkpoints and reviews.

cloud.google.com/blog/product...

MDBM, a memory-mapped key–value store. This design leveraged the operating system’s page cache via mmap to load database pages on demand

Evolving our real-time timeseries storage again: Built in Rust for performance at scale | Datadog Discover how we reengineered our metrics storage engine for massive scale with Rust, a shard-per-core model, and real-time performance.

www.datadoghq.com/blog/enginee...

Building a centralized authorization service is a serious effort.

You can also use a centralized authorization service from a third-party.

You can sidestep this headache altogether by going all-in on your central authorization service and making it the authoritative source of truth for the data.

If you want your central authorization service to return yes/no authorization results, then it will need to have access to all of the data

For centralized authorization to work you’ll have to relay a copy of that information from all of your application services to the authorization service.

データを複製する方法は数多くある．認可サービスの API を呼ぶとか，DB の operation log を使うとか．

サービスの数が増えるとデータの複製と同期は信頼できなくなりうる．