/explore
|
You are here 
|
iamsafts.com | ||
| | | | |
blog.nodraak.fr
|
|
| | | | | TL;DR: There is no best architecture, it all depends on your requirements and resources Clusters with 1 to 3 nodes are good for testing, but for production you should have at least 5 nodes Feel free to do differently as I say Introduction Since its launch in 2015, Kubernetes is the new bitcoin and every company wants to migrate all its infrastructure (which is obviously made of hundreds of microservices) to show how cool they are. | |
| | | | |
www.h-i-r.net
|
|
| | | | | Kubernetes relies on Linux containers and cgroups, so you can't run Kubernetes or even docker containers directly on OpenBSD, but Alpine Lin... | |
| | | | |
blog.tanelpoder.com
|
|
| | | | | You may remember my previous article about high-performance I/O for cloud databases, where I tested out the Silk Platform and got a single Azure VM to do over 5 GB/s (gigaBytes/s) of I/O for my large database query workload. The magic was in using iSCSI over the switched cloud compute network to multiple "data VMs" at the virtualized storage layer for high I/O throughput and scalability. Well, the Silk folks are at it again and Chris Buckel (@flashdba) just sent me screenshots of similar test runs using the latest Azure "v5" instance as the single large database node and they achieved over 10 GB/s scanning rate for reads and 6 GB/s write rate with large I/Os! - Linux, Oracle, SQL performance tuning and troubleshooting - consulting & training. | |
| | | | |
perlhacks.com
|
|
| | | In 2011 I wrote a series of three articles about Modern Perl programming for Linux Format. They concentrated on DBIx::Class and Dancer. | ||
