We gebruiken cookies om de ervaring met de Bookmate-website en onze aanbevelingen te verbeteren.
Lees onze cookiebeleid voor meer informatie.
Accepteer alle cookies
Cookie-instellingen
Martin Kleppmann
en

Martin Kleppmann

  • Hyeonsoo Shin
    Hyeonsoo Shinciteerde uit6 maanden geleden
    We call an application data-intensive if data is its primary challenge—the quantity of data, the complexity of data, or the speed at which it is changing—as opposed to compute-intensive, where CPU cycles are the bottleneck
  • Hyeonsoo Shinciteerde uit6 maanden geleden
    A fault is usually defined as one component of the system deviating from its spec, whereas a failure is when the system as a whole stops providing the required service to the user
  • Hyeonsoo Shinciteerde uit5 maanden geleden
    Operability
    Make it easy for operations teams to keep the system running smoothly.
    Simplicity
    Make it easy for new engineers to understand the system, by removing as much complexity as possible from the system. (Note this is not the same as simplicity of the user interface.)
    Evolvability
    Make it easy for engineers to make changes to the system in the future, adapting it for unanticipated use cases as requirements change. Also known as extensibility, modifiability, or plasticity.
  • Hyeonsoo Shinciteerde uit5 maanden geleden
    One of the best tools we have for removing accidental complexity is abstraction. A good abstraction can hide a great deal of implementation detail behind a clean, simple-to-understand façade. A good abstraction can also be used for a wide range of different applications. Not only is this reuse more efficient than reimplementing a similar thing multiple times, but it also leads to higher-quality software, as quality improvements in the abstracted component benefit all applications that use it
  • Samson Mwathiciteerde uitvorig jaar
    Many applications today are data-intensive , as opposed to compute-intensive
fb2epub
Sleep je bestanden hiernaartoe (maximaal 5 per keer)