PlanetScale的动态

What is Client - Client-server architecture in simple Terms: In this video, I have tried explaining client-server architecture using some real-time examples. Please watch this video to learn more about it. https://lnkd.in/dAFWmzq5

In my latest article, we discuss organizing the codebase by business capabilities rather than technical concerns. This approach slices the application vertically and challenges the traditional, layered, approach. Give it a read and let me know what you think! :)

This is a fantastic InfoQ article series by Rafal Gancarz: "Cell-Based Architectures: How to Build Scalable and Resilient Systems" "Cell-based architecture has emerged as a response to many challenges associated with distributed systems. First and foremost, it employs a bulkhead pattern to isolate failures to a fraction of the affected infrastructure footprint and prevent widespread impact. But that’s not all it can offer..." Something for all architects to bookmark! https://lnkd.in/etjid9qq

?? Introducing global replica credentials! You can now automatically route reads to the nearest replica using a single replica credential. The underlying architecture,?PlanetScale Global Network, manages all of this without requiring you to reconnect, even as you add and remove new read-only regions. This allows you to add a read-only region and start using it immediately. https://lnkd.in/gCEJBJTw

automatic routing to the replica that has the lowest latency ??

One of the many advantages of an event-driven architecture is that caching becomes trivial, and often even unnecessary. Once you serve your queries from a view materialised from the observed state, you can optimise how the data is stored to better serve the reads. You're not forced to compromise between write and read needs, and you can choose in-memory stores if it makes your life easier. Your "cache" is updated for every event that propagates through your system, so cache invalidation, a notoriously hard problem, becomes trivial.

Kindly check out my latest article on Medium about Longhorn - The Distributed Block Storage for K8s Longhorn is a cloud-native distributed block storage system for Kubernetes, offering scalable and highly available persistent storage solutions for stateful applications. In this article, I've explained the architecture of Longhorn, exploring its components and providing a step-by-step guide on how to install Longhorn within a Kubernetes cluster. #kubernetes #longhorn #medium

In REST architecture, we often focus primarily on the payload of a request or response, frequently overlooking the crucial metadata that accompanies these exchanges. Two significant examples of such metadata are the Content-Type and Accept headers. Let's take a closer look at a brief summary of the two. The Accept header allows HTTP clients to specify the type of content they expect or prefer to receive in response from the server. Conversely, the Content-Type header is utilized by both clients and servers to clearly define the format of the data contained in their respective requests and responses. This mutual understanding is essential, as it ensures that both parties can accurately interpret and process the exchanged information.

Our latest blog post introduces the KR6680V2 Mission Critical Server, based on Intel's Xeon processors - another performance powerhouse from #KAYTUS #server #intel

An review from Coalfire has confirmed that the Menlo Secure Enterprise Browser solution solves key security challenges of traditional browsers in a #ZeroTrust architecture. If you're looking for a secure enterprise browser solution that aligns with Zero Trust principle, make sure you read this paper: https://lnkd.in/gQM2S64j #MenloSecurity