Açıklaması şöyle
MessagePack is a great choice when you need a balance between speed and cross-language compatibility. It’s suitable for real-time applications and situations where data size reduction is crucial.
MessagePack is a great choice when you need a balance between speed and cross-language compatibility. It’s suitable for real-time applications and situations where data size reduction is crucial.
Google has five options for running containers which are:1. GKE Standard2. GKE Autopilot3. Cloud Run4. App Engine Flex : App Engine Flex has been more or less completely superseded by Cloud Run.4. GCE with Containers : Only really appropriate for very small deployments.
if you have an Azure-based deployment, you can assign specific zones to Azure Kubernetes Service (AKS). If you use Google Cloud, you can leverage Google Kubernetes Engine (GKE) to select multi-zone or region clusters (each option offers different benefits and drawbacks in terms of redundancy, cost, and proximity to the end-user).GKE Standard vs Autopilot
The main difference between these is that Autopilot applies a level of Google opinionation to the cluster and makes node management their responsibility.... Interestingly Google has recently made autopilot the default option when provisioning new clusters, recommending it for the majority of workloads with a potentially lower TCO as per the diagram below.
Cloud Run is Google’s ‘serverless’ container offering where all you need to do is to deploy your container image to the service and Google takes care of everything else.
The main difference between aws s3 command and aws s3api command is thataws s3 command is a higher-level abstraction that provides a more simplified and easier-to-use interface, while the aws s3api command provides a more direct and granular interface to the underlying S3 API.
aws s3 cp <kaynak dosya veya dizin> <s3://bucket ismi> [-- seçenekleri]
aws --endpoint-url=http://localhost:4566 \ s3 cp cafezin.png \ s3://bucket-example
aws --endpoint-url=http://localhost:4566 \ s3 ls \ s3://bucket-example/
aws s3 mb s3://my.private.maven
aws s3 rb s3://your-unique-bucket-name --force aws iam delete-role --role-name CrossRegionReplicationRole
aws s3 presign s3://your-unique-bucket-name/hello.txt --expires-in 3600
{ "Version": "2012-10-17", "Statement": [ { "Sid": "PublicReadGetObject", "Effect": "Allow", "Principal": "*", "Action": "s3:GetObject", "Resource": "arn:aws:s3:::testbucket/*" } ] }
# sync the website folder that contains our files to the S3 bucket aws --endpoint-url=http://localhost:4566 s3 sync .\website\ s3://testbucket # enable static website hosting on the bucket and configure the index and error documents: aws --endpoint-url=http://localhost:4566 s3 website s3://testbucket/ \ --index-document index.html --error-document error.html
aws --endpoint-url=http://127.0.0.1:4566 \ s3api create-bucket \ --bucket bucket-example
# create s3 bucket aws --endpoint-url=http://localhost:4566 s3api create-bucket --bucket testbucket # list s3 buckets aws --endpoint-url=http://localhost:4566 s3api list-buckets # copy test file to the created bucket. aws --endpoint-url=http://localhost:4566 s3 cp test.txt s3://testbucket # check files aws --endpoint-url=http://localhost:4566 s3api list-objects --bucket testbucket
aws s3api put-bucket-versioning --bucket your-unique-bucket-name --versioning-configuration Status=Enabled
When interacting with LocalStack to emulate AWS services it’s important to configure your AWS CLI or SDK to point to the LocalStack endpoint URL. This allows you to interact with LocalStack easily without having to specify the --endpoint-url option every time you run a command.Another option is installing a tool called “awslocal” which is a wrapper around the AWS CLI for LocalStack. It automatically configures the CLI to use the LocalStack endpoint URL, saving you from the manual step of specifying the --endpoint-url option.
awslocal is a thin wrapper and a drop-in replacement for the aws command that runs commands directly against LocalStack
# create s3 bucket aws --endpoint-url=http://localhost:4566 s3api create-bucket --bucket testbucket # list s3 buckets aws --endpoint-url=http://localhost:4566 s3api list-buckets # copy test file to the created bucket. aws --endpoint-url=http://localhost:4566 s3 cp test.txt s3://testbucket # check files aws --endpoint-url=http://localhost:4566 s3api list-objects --bucket testbucket
{ "Version": "2012-10-17", "Statement": [ { "Sid": "PublicReadGetObject", "Effect": "Allow", "Principal": "*", "Action": "s3:GetObject", "Resource": "arn:aws:s3:::testbucket/*" } ] }
# sync the website folder that contains our files to the S3 bucket aws --endpoint-url=http://localhost:4566 s3 sync .\website\ s3://testbucket # enable static website hosting on the bucket and configure the index and error documents: aws --endpoint-url=http://localhost:4566 s3 website s3://testbucket/ \ --index-document index.html --error-document error.html
docker exec -it <container_id> /bin/bash
$awslocal sqs create-queue --queue-name test-queue $awslocal sqs list-queues { "QueueUrls" : [ http:/localhost:4566:/000000/test-queue" ] }
awslocal s3 mb s3://my-test-bucket
awslocal s3api create-bucket \ --bucket mybucket \ --create-bucket-configuration LocationConstraint=eu-central-1
LocalStack is a cloud service emulator that runs in a single container on your laptop or in your CI environment. With LocalStack, you can run your AWS applications or Lambdas entirely on your local machine without connecting to a remote cloud provider! Whether you are testing complex CDK applications or Terraform configurations, or just beginning to learn about AWS services, LocalStack helps speed up and simplify your testing and development workflow.
LocalStack is a cloud service emulator that runs AWS services solely on your laptop without connecting to a remote cloud provider .
SELECT a || a || a || a as a from (SELECT 'aaaa' || rand() as a) tSELECT a || a || a || a as a from ("SELECT 'aaaa' as a) t
// Abstract Product - Buttonpublic interface Button {void render();}// Concrete Product - WindowsButtonpublic class WindowsButton implements Button {@Overridepublic void render() {System.out.println("Rendering a Windows button");}}// Concrete Product - MacButtonpublic class MacButton implements Button {@Overridepublic void render() {System.out.println("Rendering a Mac button");}}
// Abstract Factory public interface GUIFactory { Button createButton(); } // Concrete Factory - WindowsFactory public class WindowsFactory implements GUIFactory { @Override public Button createButton() { return new WindowsButton(); } } // Concrete Factory - MacFactory public class MacFactory implements GUIFactory { @Override public Button createButton() { return new MacButton(); } }
They are grouped into families that emphasize some possibilities for your workloads:General Purpose (Genel Amaçlı) – also known as balanced instances, best for web servers, microservices, small and medium databases, development environments, and code repositories.Compute Optimized (İşlem İçin Optimize Edilmiş) – designed for compute-intensive workloads, like batch processing, data analytics, scientific modeling, dedicated gaming servers, machine learning, and high-performance computing.Memory-Optimized (Bellek İçin Optimize Edilmiş) – memory-intensive applications that process large data sets in memory, such as databases and real-time streaming.Accelerated Computing (Hızlandırılmış Bilişim) – used for graphics processing, machine learning, data pattern matching, and other numerically intensive workloads.Storage Optimized (Depolama İçin Optimize Edilmiş) – designed for high, sequential read and write access to very large data sets on local storage. Best for NoSQL databases, in-memory databases, data warehousing, Elasticsearch, analytics workloads.
In AWS, there are many Instance Families. One of them is burstable general-purpose instances, which are basically T Instance Family.The T Instance Family offers a baseline CPU performance but it also has the ability to burst above the baseline at any time as logs as required. Which is essential for business-critical or unknown behavior of the workloads.
Burstable Instances earn CPU credits while running below the baseline and spending them when bursting.
Earned Credits: The amount of credits an instance earns while runningUsed Credits: When a burstable instance is in the running state, it will continuously use CPU credits.Accrued Credits: Difference between the earned credits and used credits is called accrued credits.
For a typical, simple microservice application, a minimum configuration of t2.medium instance type should do the work. T2 instances are the lowest-cost general purpose instance type. You can easily change your instance types if after a while your needs change.