مهندس پلتفرم (Platform Engineer) یک نوع مهندسی است که در آن، فرد مسئولیت طراحی، پیاده سازی و مدیریت پلتفرم های نرم افزاری را بر عهده دارد. این پلتفرم ها شامل سیستم های ابری، بانک های اطلاعاتی، سرویس های وب، موتورهای جستجو، سیستم های توزیع محتوا و ... می باشند. هدف اصلی این مهندسان، بهینه سازی عملکرد، قابلیت اطمینان و امنیت پلتفرم های نرم افزاری است. برای این منظور، آنها با استفاده از تکنولوژی های مختلف، مانند مانیتورینگ، خودکارسازی و ابزارهای مدیریت کانتینرها، سعی در بهبود عملکرد و کاهش خطاهای سیستم دارند.
مهندس پلتفرم به عنوان یکی از مهندسان اصلی در صنعت فناوری اطلاعات، با توجه به اهمیت پلتفرم های نرم افزاری در جامعه مدرن، به عنوان یک شغل پر درآمد و پر استخدام شناخته می شود. برای شغل مهندس پلتفرم، دانش فنی و تجربه کاری قوی در زمینه توسعه نرم افزار، مدیریت سیستم ها و شبکه ها، مانیتورینگ و خودکارسازی لازم است. همچنین، آشنایی با تکنولوژی های مختلف مانند کانتینرها، مایکروسرویس ها و تکنولوژی های ابری نیز ضروری است. در نهایت، مهارت های ارتباطی و توانایی مهم است
#platform #enginner #linux
https://t.iss.one/unixmens
مهندس پلتفرم به عنوان یکی از مهندسان اصلی در صنعت فناوری اطلاعات، با توجه به اهمیت پلتفرم های نرم افزاری در جامعه مدرن، به عنوان یک شغل پر درآمد و پر استخدام شناخته می شود. برای شغل مهندس پلتفرم، دانش فنی و تجربه کاری قوی در زمینه توسعه نرم افزار، مدیریت سیستم ها و شبکه ها، مانیتورینگ و خودکارسازی لازم است. همچنین، آشنایی با تکنولوژی های مختلف مانند کانتینرها، مایکروسرویس ها و تکنولوژی های ابری نیز ضروری است. در نهایت، مهارت های ارتباطی و توانایی مهم است
#platform #enginner #linux
https://t.iss.one/unixmens
👍4
DevOps and Platform Engineering are two closely related but distinct fields in the realm of software development and IT operations. Here is an overview of each:
DevOps : stands for Development and Operations. It is a set of practices that combines software development (Dev) and IT operations (Ops) to shorten the system development life cycle and provide continuous delivery with high software quality.
- The primary goal of DevOps is to enable organizations to deliver features, updates, and fixes more frequently and reliably through automated processes and collaboration between development, quality assurance, and IT operations teams.
- DevOps promotes a culture of collaboration, automation, continuous integration, and continuous delivery to achieve efficiency, speed, and stability in software development and deployment.
- DevOps engineers typically use tools like Docker, Kubernetes, Jenkins, Puppet, Chef, Ansible, etc. to automate infrastructure, deployment, and testing processes.
Platform Engineering : focuses on building and maintaining the underlying infrastructure and tools that enable the development, deployment, and operation of software applications.
- Platform Engineers design, implement, and manage the platforms and services that support the software development lifecycle, including provisioning resources, managing scalability, and ensuring reliability and security.
- They work on creating robust platforms that provide a foundation for developers to build and deploy their applications efficiently.
- Platform Engineering requires expertise in cloud computing, networking, security, scalability, and automation to design and maintain platforms that meet the needs of software development teams.
In summary, while DevOps is more focused on the integration and automation of software development and IT operations processes to accelerate delivery and improve quality, Platform Engineering is focused on creating and maintaining the infrastructure and tools that support the software development lifecycle. Both are crucial in modern software development practices to ensure efficient delivery of high-quality software applications.
We provide comprehensive organizational improvement solutions for these concepts. including: devops, sds, security, storage, data center
Just contact us
#devops #platform #secops #itops #sddc #mlops #ops
https://t.iss.one/unixmens
DevOps : stands for Development and Operations. It is a set of practices that combines software development (Dev) and IT operations (Ops) to shorten the system development life cycle and provide continuous delivery with high software quality.
- The primary goal of DevOps is to enable organizations to deliver features, updates, and fixes more frequently and reliably through automated processes and collaboration between development, quality assurance, and IT operations teams.
- DevOps promotes a culture of collaboration, automation, continuous integration, and continuous delivery to achieve efficiency, speed, and stability in software development and deployment.
- DevOps engineers typically use tools like Docker, Kubernetes, Jenkins, Puppet, Chef, Ansible, etc. to automate infrastructure, deployment, and testing processes.
Platform Engineering : focuses on building and maintaining the underlying infrastructure and tools that enable the development, deployment, and operation of software applications.
- Platform Engineers design, implement, and manage the platforms and services that support the software development lifecycle, including provisioning resources, managing scalability, and ensuring reliability and security.
- They work on creating robust platforms that provide a foundation for developers to build and deploy their applications efficiently.
- Platform Engineering requires expertise in cloud computing, networking, security, scalability, and automation to design and maintain platforms that meet the needs of software development teams.
In summary, while DevOps is more focused on the integration and automation of software development and IT operations processes to accelerate delivery and improve quality, Platform Engineering is focused on creating and maintaining the infrastructure and tools that support the software development lifecycle. Both are crucial in modern software development practices to ensure efficient delivery of high-quality software applications.
We provide comprehensive organizational improvement solutions for these concepts. including: devops, sds, security, storage, data center
Just contact us
#devops #platform #secops #itops #sddc #mlops #ops
https://t.iss.one/unixmens
Keptn is an open-source control plane for continuous delivery and automated operations. It is designed to help developers and SRE (Site Reliability Engineering) teams implement and manage continuous delivery pipelines, automate deployments, and perform automated operations tasks in cloud-native environments.
### Key Features and Components of Keptn:
1. Continuous Delivery (CD):
Keptn automates the end-to-end continuous delivery process, including building, testing, deploying, and promoting applications across different environments (e.g., development, staging, production).
2. Cloud-Native Support:
Keptn is designed for cloud-native environments and supports Kubernetes as the primary orchestration platform. It integrates seamlessly with popular cloud services and tools.
3. Event-Driven Automation:
Keptn uses an event-driven architecture to trigger and orchestrate delivery and operations tasks based on predefined events and conditions (e.g., code commits, performance thresholds).
4. GitOps Integration:
Keptn supports GitOps principles by managing application configurations and delivery workflows through Git repositories, enabling version control and traceability.
5. Multi-Stage Pipelines:
Keptn supports multi-stage delivery pipelines, allowing teams to define sequential or parallel stages for building, testing, and deploying applications.
6. Automated Operations:
Beyond deployment automation, Keptn includes features for automated operations, such as auto-remediation of incidents, performance monitoring, and scalability management.
7. Integration with Observability Tools:
Keptn integrates with observability tools like Prometheus, Grafana, and Dynatrace for monitoring application and infrastructure metrics, enabling automatic scaling and performance optimizations.
### Components of Keptn:
- Bridge: A web-based user interface for viewing and managing Keptn projects, stages, services, and deployments.
- Control Plane (APIs): The core control plane of Keptn responsible for managing projects, services, and orchestration of delivery and operations tasks.
- CLI (Command-Line Interface): A CLI tool for interacting with Keptn, creating projects, triggering deployments, and monitoring pipeline execution.
- Service Templates: Pre-defined templates for different types of services (e.g., microservices, web applications) that can be used to bootstrap new projects.
- Automation Engine: The engine that executes delivery and operations workflows based on event triggers and defined configurations.
### Use Cases for Keptn:
- Cloud-Native Application Delivery: Automate the deployment and lifecycle management of cloud-native applications across Kubernetes clusters.
- Continuous Delivery Pipelines: Implement end-to-end continuous delivery pipelines for microservices-based applications.
- Automated Operations: Enable auto-remediation and self-healing capabilities for cloud-native applications based on predefined rules and thresholds.
- GitOps and Infrastructure as Code: Embrace GitOps practices by managing application configurations and delivery workflows as code.
Keptn simplifies and accelerates the adoption of DevOps practices in cloud-native environments by providing a comprehensive framework for continuous delivery, automation, and observability. It is widely used by organizations leveraging Kubernetes and microservices architectures to streamline their software delivery and operations processes.
#devpos #platform #linux #k8s #k3s #kubernetes #keptn #security #control #control_plane
https://t.iss.one/unixmens
### Key Features and Components of Keptn:
1. Continuous Delivery (CD):
Keptn automates the end-to-end continuous delivery process, including building, testing, deploying, and promoting applications across different environments (e.g., development, staging, production).
2. Cloud-Native Support:
Keptn is designed for cloud-native environments and supports Kubernetes as the primary orchestration platform. It integrates seamlessly with popular cloud services and tools.
3. Event-Driven Automation:
Keptn uses an event-driven architecture to trigger and orchestrate delivery and operations tasks based on predefined events and conditions (e.g., code commits, performance thresholds).
4. GitOps Integration:
Keptn supports GitOps principles by managing application configurations and delivery workflows through Git repositories, enabling version control and traceability.
5. Multi-Stage Pipelines:
Keptn supports multi-stage delivery pipelines, allowing teams to define sequential or parallel stages for building, testing, and deploying applications.
6. Automated Operations:
Beyond deployment automation, Keptn includes features for automated operations, such as auto-remediation of incidents, performance monitoring, and scalability management.
7. Integration with Observability Tools:
Keptn integrates with observability tools like Prometheus, Grafana, and Dynatrace for monitoring application and infrastructure metrics, enabling automatic scaling and performance optimizations.
### Components of Keptn:
- Bridge: A web-based user interface for viewing and managing Keptn projects, stages, services, and deployments.
- Control Plane (APIs): The core control plane of Keptn responsible for managing projects, services, and orchestration of delivery and operations tasks.
- CLI (Command-Line Interface): A CLI tool for interacting with Keptn, creating projects, triggering deployments, and monitoring pipeline execution.
- Service Templates: Pre-defined templates for different types of services (e.g., microservices, web applications) that can be used to bootstrap new projects.
- Automation Engine: The engine that executes delivery and operations workflows based on event triggers and defined configurations.
### Use Cases for Keptn:
- Cloud-Native Application Delivery: Automate the deployment and lifecycle management of cloud-native applications across Kubernetes clusters.
- Continuous Delivery Pipelines: Implement end-to-end continuous delivery pipelines for microservices-based applications.
- Automated Operations: Enable auto-remediation and self-healing capabilities for cloud-native applications based on predefined rules and thresholds.
- GitOps and Infrastructure as Code: Embrace GitOps practices by managing application configurations and delivery workflows as code.
Keptn simplifies and accelerates the adoption of DevOps practices in cloud-native environments by providing a comprehensive framework for continuous delivery, automation, and observability. It is widely used by organizations leveraging Kubernetes and microservices architectures to streamline their software delivery and operations processes.
#devpos #platform #linux #k8s #k3s #kubernetes #keptn #security #control #control_plane
https://t.iss.one/unixmens
Academy and Foundation unixmens | Your skills, Your future
Photo
## YouTube Architecture: A Simplified Breakdown
This diagram illustrates the core components that power YouTube's global video streaming platform.
1. User Interaction:
* Mobile & Web Clients: Users interact with YouTube through the app on their phones and tablets, or the website on their computers.
2. Content Delivery Network (CDN):
* Distributed Servers: YouTube relies on a globally distributed CDN to store and deliver video content close to users.
* Benefits: This reduces latency, buffering, and improves streaming reliability by serving videos from the nearest server.
3. Server Infrastructure:
* Load Balancer: Distributes incoming traffic across multiple application servers, preventing bottlenecks and ensuring high availability.
* Application Servers: Handle core YouTube functions such as video playback, search, user interaction, and processing requests efficiently.
* Transcoding Servers: Convert uploaded videos to various formats and resolutions for compatibility across different devices and network conditions.
4. Databases & Metadata:
* User Database: Stores user data like profiles, watch history, and preferences for personalized recommendations.
* Metadata Database: Stores video details (titles, descriptions, tags, categories) to enable search, discovery, and organization.
* Metadata Cache: Temporarily stores frequently accessed metadata for faster retrieval.
5. Storage & Processing:
* Processing Queue: Manages video transcoding and processing workflows to ensure timely availability of new uploads.
* Thumbnail Storage: Dedicated storage for quick access to video thumbnails, enhancing the visual appeal of video listings.
* Media Storage (like S3): Secure, scalable cloud-based storage for videos, images, and other media assets.
6. Web Server: Handles HTTP requests from web clients, delivering web pages and managing communication between the client and backend services.
This simplified explanation highlights the key elements of YouTube's architecture. For deeper understanding, further research on specific technologies and functionalities is recommended.
#youtube #arch #linux #storage #platform
https://t.iss.one/unixmens
This diagram illustrates the core components that power YouTube's global video streaming platform.
1. User Interaction:
* Mobile & Web Clients: Users interact with YouTube through the app on their phones and tablets, or the website on their computers.
2. Content Delivery Network (CDN):
* Distributed Servers: YouTube relies on a globally distributed CDN to store and deliver video content close to users.
* Benefits: This reduces latency, buffering, and improves streaming reliability by serving videos from the nearest server.
3. Server Infrastructure:
* Load Balancer: Distributes incoming traffic across multiple application servers, preventing bottlenecks and ensuring high availability.
* Application Servers: Handle core YouTube functions such as video playback, search, user interaction, and processing requests efficiently.
* Transcoding Servers: Convert uploaded videos to various formats and resolutions for compatibility across different devices and network conditions.
4. Databases & Metadata:
* User Database: Stores user data like profiles, watch history, and preferences for personalized recommendations.
* Metadata Database: Stores video details (titles, descriptions, tags, categories) to enable search, discovery, and organization.
* Metadata Cache: Temporarily stores frequently accessed metadata for faster retrieval.
5. Storage & Processing:
* Processing Queue: Manages video transcoding and processing workflows to ensure timely availability of new uploads.
* Thumbnail Storage: Dedicated storage for quick access to video thumbnails, enhancing the visual appeal of video listings.
* Media Storage (like S3): Secure, scalable cloud-based storage for videos, images, and other media assets.
6. Web Server: Handles HTTP requests from web clients, delivering web pages and managing communication between the client and backend services.
This simplified explanation highlights the key elements of YouTube's architecture. For deeper understanding, further research on specific technologies and functionalities is recommended.
#youtube #arch #linux #storage #platform
https://t.iss.one/unixmens
Telegram
Academy and Foundation unixmens | Your skills, Your future
@unixmens_support
@yashar_esm
[email protected]
یک کانال علمی تکنولوژی
فلسفه متن باز-گنو/لینوکس-امنیت - اقتصاد
دیجیتال
Technology-driven -بیزینس های مبتنی بر تکنولوژی
Enterprise open source
ارایه دهنده راهکارهای ارتقای سازمانی - فردی - تیمی
@yashar_esm
[email protected]
یک کانال علمی تکنولوژی
فلسفه متن باز-گنو/لینوکس-امنیت - اقتصاد
دیجیتال
Technology-driven -بیزینس های مبتنی بر تکنولوژی
Enterprise open source
ارایه دهنده راهکارهای ارتقای سازمانی - فردی - تیمی
👍1
#سوال : آیا یک devops کار یا مهندس پلتفرم نیاز دارد که به مفاهیم DBA تسلط داشته باشد ؟
بله، یک مهندس DevOps یا مهندس پلتفرم نیاز دارد که با مفاهیم و اصول مربوط به DBA (مدیریت پایگاه داده) آشنا باشد. این آشنایی می‌تواند در چندین جنبه مهم کارهای روزانه‌ی آنها تأثیرگذار باشد. در ادامه به دلایلی که چرا این آشنایی ضروری است، اشاره میکنیم:
1 مدیریت پایگاه داده‌ها در محیط‌های production :
-نصب و راه‌اندازی : مهندسان DevOps اغلب مسئول نصب و پیکربندی پایگاه داده‌ها در محیط‌های کلود یا سرورهای داخلی هستند.
- پشتیبان‌گیری و بازیابی: نیاز به اطمینان از اینکه داده‌ها به درستی پشتیبان‌گیری می‌شوند و در صورت لزوم قابل بازیابی هستند.
2.بهینه‌سازی عملکرد
تنظیمات عملکردی: تنظیمات و پیکربندی‌های بهینه برای پایگاه داده‌ها جهت افزایش عملکرد و کاهش تاخیر.
- شاخص‌گذاری (اندکس) و Query Optimization : درک نحوه‌ی بهبود کارایی Queryها از طریق شاخص‌گذاری مناسب و بهینه‌سازی پرس‌وجوها.
3.امنیت پایگاه داده
- کنترل دسترسی: تنظیم دسترسی کاربران و نقش‌ها به پایگاه داده برای اطمینان از امنیت داده‌ها.
- رمزنگاری داده‌ها: استفاده از تکنیک‌های رمزنگاری برای محافظت از داده‌ها در حال ذخیره و انتقال.
4. مانیتورینگ و نگهداری
- نظارت بر عملکرد: مانیتورینگ مداوم عملکرد پایگاه داده برای شناسایی و رفع مشکلات پیش از تبدیل شدن به مسائل بحرانی.
نگهداری و به‌روزرسانی: اعمال به‌روزرسانی‌های امنیتی و نگهداری منظم پایگاه داده‌ها.
5. استقرار و اتوماسیون
اسکریپت‌های استقرار: ایجاد و مدیریت اسکریپت‌هایی برای استقرار و به‌روزرسانی پایگاه داده‌ها به صورت خودکار.
ا Continuous Integration/Continuous Deployment (CI/CD) :
ادغام پایگاه داده در زنجیره‌ی CI/CD برای اطمینان از همگام‌سازی تغییرات پایگاه داده با تغییرات کد.
6. - کار با دیتابیس‌های کلود و ...
مدیریت خدمات پایگاه داده‌های کلود: استفاده از خدمات مدیریت‌شده پایگاه داده مثل Amazon RDS، Google Cloud SQL و Azure SQL Database و دانستن نحوه‌ی پیکربندی و بهینه‌سازی آنها.
7- پیاده سازی راهکاری HA
نیاز به ایجاد راهکارهای HA و replication یک ضرورت برای سازمان ها است . و دانش آن یکی از ضروریات این مفهوم میباشد .
نتیجه‌گیری
تسلط بر مفاهیم DBA برای یک مهندس DevOps یا مهندس پلتفرم نه تنها مفید است بلکه در بسیاری از موارد ضروری میباشد. این دانش به آنها کمک می‌کند تا بتوانند پایگاه داده‌ها را به درستی مدیریت، نگهداری و بهینه‌سازی کنند و در نهایت اطمینان حاصل کنند که سیستم‌ها به طور کامل و بهینه عمل می‌کنند.
#dba #devops #linux #platform #platform_eng
https://t.iss.one/unixmens
بله، یک مهندس DevOps یا مهندس پلتفرم نیاز دارد که با مفاهیم و اصول مربوط به DBA (مدیریت پایگاه داده) آشنا باشد. این آشنایی می‌تواند در چندین جنبه مهم کارهای روزانه‌ی آنها تأثیرگذار باشد. در ادامه به دلایلی که چرا این آشنایی ضروری است، اشاره میکنیم:
1 مدیریت پایگاه داده‌ها در محیط‌های production :
-نصب و راه‌اندازی : مهندسان DevOps اغلب مسئول نصب و پیکربندی پایگاه داده‌ها در محیط‌های کلود یا سرورهای داخلی هستند.
- پشتیبان‌گیری و بازیابی: نیاز به اطمینان از اینکه داده‌ها به درستی پشتیبان‌گیری می‌شوند و در صورت لزوم قابل بازیابی هستند.
2.بهینه‌سازی عملکرد
تنظیمات عملکردی: تنظیمات و پیکربندی‌های بهینه برای پایگاه داده‌ها جهت افزایش عملکرد و کاهش تاخیر.
- شاخص‌گذاری (اندکس) و Query Optimization : درک نحوه‌ی بهبود کارایی Queryها از طریق شاخص‌گذاری مناسب و بهینه‌سازی پرس‌وجوها.
3.امنیت پایگاه داده
- کنترل دسترسی: تنظیم دسترسی کاربران و نقش‌ها به پایگاه داده برای اطمینان از امنیت داده‌ها.
- رمزنگاری داده‌ها: استفاده از تکنیک‌های رمزنگاری برای محافظت از داده‌ها در حال ذخیره و انتقال.
4. مانیتورینگ و نگهداری
- نظارت بر عملکرد: مانیتورینگ مداوم عملکرد پایگاه داده برای شناسایی و رفع مشکلات پیش از تبدیل شدن به مسائل بحرانی.
نگهداری و به‌روزرسانی: اعمال به‌روزرسانی‌های امنیتی و نگهداری منظم پایگاه داده‌ها.
5. استقرار و اتوماسیون
اسکریپت‌های استقرار: ایجاد و مدیریت اسکریپت‌هایی برای استقرار و به‌روزرسانی پایگاه داده‌ها به صورت خودکار.
ا Continuous Integration/Continuous Deployment (CI/CD) :
ادغام پایگاه داده در زنجیره‌ی CI/CD برای اطمینان از همگام‌سازی تغییرات پایگاه داده با تغییرات کد.
6. - کار با دیتابیس‌های کلود و ...
مدیریت خدمات پایگاه داده‌های کلود: استفاده از خدمات مدیریت‌شده پایگاه داده مثل Amazon RDS، Google Cloud SQL و Azure SQL Database و دانستن نحوه‌ی پیکربندی و بهینه‌سازی آنها.
7- پیاده سازی راهکاری HA
نیاز به ایجاد راهکارهای HA و replication یک ضرورت برای سازمان ها است . و دانش آن یکی از ضروریات این مفهوم میباشد .
نتیجه‌گیری
تسلط بر مفاهیم DBA برای یک مهندس DevOps یا مهندس پلتفرم نه تنها مفید است بلکه در بسیاری از موارد ضروری میباشد. این دانش به آنها کمک می‌کند تا بتوانند پایگاه داده‌ها را به درستی مدیریت، نگهداری و بهینه‌سازی کنند و در نهایت اطمینان حاصل کنند که سیستم‌ها به طور کامل و بهینه عمل می‌کنند.
#dba #devops #linux #platform #platform_eng
https://t.iss.one/unixmens
Telegram
Academy and Foundation unixmens | Your skills, Your future
@unixmens_support
@yashar_esm
[email protected]
یک کانال علمی تکنولوژی
فلسفه متن باز-گنو/لینوکس-امنیت - اقتصاد
دیجیتال
Technology-driven -بیزینس های مبتنی بر تکنولوژی
Enterprise open source
ارایه دهنده راهکارهای ارتقای سازمانی - فردی - تیمی
@yashar_esm
[email protected]
یک کانال علمی تکنولوژی
فلسفه متن باز-گنو/لینوکس-امنیت - اقتصاد
دیجیتال
Technology-driven -بیزینس های مبتنی بر تکنولوژی
Enterprise open source
ارایه دهنده راهکارهای ارتقای سازمانی - فردی - تیمی
در مورد نقش های دواپس و دانش اون گفتم که حرف و حدیث زیادی داشت .
و این موضوع مطرح کردم که دواپس یعنی فرایند که فرد باید دانش اون را با پیش‌نیاز های دانش دیگه داشته باشه و نمیشه فرد یهویی دواپس /مهندس پلتفرم و مهندس کلود بشه
https://www.linkedin.com/posts/yashar-esmaildokht_devops-activity-7234456681139630081-tCv2?utm_source=share&utm_medium=member_ios
بعضی ها میگفتن این دانش ها زیاده و برخی کم
باید بگم عزیزم این راه نیاز به دانش های زیادی داره
به خاطر این هست سخت و زمان بر هست
خود دانش لینوکسیش زمان بر هست چه برسه به اینها
به خاطر این هست حقوق این بخش بالا تر هست . چون هرروز باید یاد بگیری . خودت را توسعه بدی و اگر عاشق نباشی نمیتونی توش باشی .
چرا چون ممکنه شما بخواید در یک بیزینس فینتکی باشید کلا استک فرق میکنه
ممکنه تو یه بیزینس کلودی باشید کلا استک فرق میکنه
ممکنه تو بیزینس امنیتی باشی
استک فرق میکنه
ممکنه تو بیزینس مبتنی بر edge compute باشی
استک فرق میکنه و حتی نمیتونه از کوبر استفاده کنی میری از دیسترو های مبتنی بر بیزینس استفاده میکنی که نسخه سفارشی شده کوبر هست استفاده میکنی
و ...
عزیزم باید همه این ها را بدونی
تعارف نداریم که
برو دورهای lpic را ببین متوجه منظورم میشی
برو دوره های رد هت را ببین متوجه منظورم میشی
برو دوره های oracle را ببین متوجه منظورم میشی
برو دوره های ibm را ببین متوجه متظورم میشی
همه اینها مبتنی بر گنو/لینوکس و این کانسپت هستن
و ...
حالا بعد دیدنش بیا پیشم . من میگم خوش اومدی به دنیای enterprise open source
بعد یه تایم ست میکنیم یه قهوه میخوریم باهم . در موردش با لذت بسیار صحبت میکنیم .
یه نکته دیگه :من حتی یک بخش دیگش را نگفته بودم . و این هست که دانش وب ٣ را هم عزیزان باید داشته باشن
چون جهان به این سمت حرکت میکنه . من خودم در موردش دارم کتاب می‌نویسم
این روز ها خیلی busy هستم . ولی در آینده در مورد پروتکل های استوریج مبتنی بر web3 یا ipfs کلاس برگزار خواهم کرد و پروتکل quic. را خواهم گفت .
این را هم بگم من خودم هرروز چیز جدیدی یاد میگیرم ...
#DevOps #platform #cloud #infrastracture
https://t.iss.one/unixmens
و این موضوع مطرح کردم که دواپس یعنی فرایند که فرد باید دانش اون را با پیش‌نیاز های دانش دیگه داشته باشه و نمیشه فرد یهویی دواپس /مهندس پلتفرم و مهندس کلود بشه
https://www.linkedin.com/posts/yashar-esmaildokht_devops-activity-7234456681139630081-tCv2?utm_source=share&utm_medium=member_ios
بعضی ها میگفتن این دانش ها زیاده و برخی کم
باید بگم عزیزم این راه نیاز به دانش های زیادی داره
به خاطر این هست سخت و زمان بر هست
خود دانش لینوکسیش زمان بر هست چه برسه به اینها
به خاطر این هست حقوق این بخش بالا تر هست . چون هرروز باید یاد بگیری . خودت را توسعه بدی و اگر عاشق نباشی نمیتونی توش باشی .
چرا چون ممکنه شما بخواید در یک بیزینس فینتکی باشید کلا استک فرق میکنه
ممکنه تو یه بیزینس کلودی باشید کلا استک فرق میکنه
ممکنه تو بیزینس امنیتی باشی
استک فرق میکنه
ممکنه تو بیزینس مبتنی بر edge compute باشی
استک فرق میکنه و حتی نمیتونه از کوبر استفاده کنی میری از دیسترو های مبتنی بر بیزینس استفاده میکنی که نسخه سفارشی شده کوبر هست استفاده میکنی
و ...
عزیزم باید همه این ها را بدونی
تعارف نداریم که
برو دورهای lpic را ببین متوجه منظورم میشی
برو دوره های رد هت را ببین متوجه منظورم میشی
برو دوره های oracle را ببین متوجه منظورم میشی
برو دوره های ibm را ببین متوجه متظورم میشی
همه اینها مبتنی بر گنو/لینوکس و این کانسپت هستن
و ...
حالا بعد دیدنش بیا پیشم . من میگم خوش اومدی به دنیای enterprise open source
بعد یه تایم ست میکنیم یه قهوه میخوریم باهم . در موردش با لذت بسیار صحبت میکنیم .
یه نکته دیگه :من حتی یک بخش دیگش را نگفته بودم . و این هست که دانش وب ٣ را هم عزیزان باید داشته باشن
چون جهان به این سمت حرکت میکنه . من خودم در موردش دارم کتاب می‌نویسم
این روز ها خیلی busy هستم . ولی در آینده در مورد پروتکل های استوریج مبتنی بر web3 یا ipfs کلاس برگزار خواهم کرد و پروتکل quic. را خواهم گفت .
این را هم بگم من خودم هرروز چیز جدیدی یاد میگیرم ...
#DevOps #platform #cloud #infrastracture
https://t.iss.one/unixmens
Linkedin
من در تعجبم هستم وقتی رزومه برخی از افراد را میبینم / | Yashar Esmaildokht
من در تعجبم هستم وقتی رزومه برخی از افراد را میبینم /
فرایند شغلی devops engineer یک روند هست . که باید تجربه و دانش system engineering و system administrator و ... را داشته باشد .
باید فرآیند های مختلف و معماری سیستم های مختلف را درک کند .
باید دانش…
فرایند شغلی devops engineer یک روند هست . که باید تجربه و دانش system engineering و system administrator و ... را داشته باشد .
باید فرآیند های مختلف و معماری سیستم های مختلف را درک کند .
باید دانش…
👏3
Academy and Foundation unixmens | Your skills, Your future
In many organizations, they don't have Devops and they think they do. Actually they have gitops. And they think have DevOps ... There is a sentence that says Understanding the problem and recognizing it is the most important part of the process. Generally…
Example:
In a GitOps workflow, you'd store your infrastructure configuration, application deployment scripts, and application code in a Git repository. Any change to the repository (e.g., a new feature, bug fix, or infrastructure update) would trigger an automated process to update the target environment. The system would compare the desired state in Git with the actual state of the environment and automatically make the necessary changes.
Why don't organizations understand that DevOps is different from gitops and what is the difference between DevOps and gitops?
It's right to point out that there's often confusion between DevOps and GitOps, and sometimes organizations don't fully grasp the distinction. This can happen for several reasons:
1. Overlapping Principles:
* DevOps and GitOps share a lot of common ground. Both advocate for automation, collaboration, continuous delivery, and a focus on infrastructure as code. This shared vocabulary can lead to blurring the lines.
* Evolutionary Connection: GitOps can be seen as an extension of DevOps. It builds on the principles of DevOps but adds a stricter framework for managing infrastructure and configurations through Git.
2. Marketing Hype:
* The "Git" Appeal: The term "GitOps" naturally catches attention because "Git" is a familiar and popular tool in the developer community. It might appear as an appealing solution without a full understanding of the underlying differences.
* "DevOps" Fatigue: The term "DevOps" has become quite common, sometimes to the point of oversaturation. Organizations might be searching for new terms and concepts, leading to an overemphasis on GitOps as a distinct and superior approach.
3. Misinterpretation of GitOps:
* GitOps as a Replacement: Some might perceive GitOps as a replacement for DevOps, rather than an extension. This misconception could lead to overlooking the broader benefits of DevOps, like fostering a collaborative culture.
* Focus on Tools: The emphasis on Git in GitOps might lead some to think it's just about using Git for deployment, overlooking the underlying principles of automation, observability, and declarative configurations.
4. Lack of Clear Understanding:
* Incomplete Adoption of DevOps: Some organizations might only have partially embraced DevOps, lacking the full understanding of its principles and practices. This makes it harder to distinguish GitOps as a distinct and complementary approach.
* Insufficient Education and Training: A lack of comprehensive education and training on both DevOps and GitOps can contribute to confusion and misinterpretation.
Why DevOps Still Matters:
While GitOps offers significant benefits, DevOps still remains a crucial foundation for successful software delivery:
* Cultural Shift: DevOps focuses on building a collaborative culture between development and operations teams. This cultural change is fundamental to efficient software delivery.
* Broader Scope: DevOps encompasses more than just infrastructure management. It addresses the entire software development lifecycle, including planning, development, testing, deployment, and monitoring.
* Flexibility and Adaptability: DevOps provides a framework for adapting to evolving technologies and processes. It's not tied to specific tools or methodologies.
Conclusion:
It's crucial to recognize that GitOps is a powerful addition to the DevOps toolset. However, it's not a replacement for DevOps. Understanding the differences and the benefits of each approach will help organizations make informed decisions about adopting and implementing them effectively.
Remember:
While GitOps can be a powerful approach, it requires careful planning and implementation. It's not a one-size-fits-all solution and might not be suitable for every team or project.
#devops vs #gitops #linux #platform #culture
https://t.iss.one/unixmens
In a GitOps workflow, you'd store your infrastructure configuration, application deployment scripts, and application code in a Git repository. Any change to the repository (e.g., a new feature, bug fix, or infrastructure update) would trigger an automated process to update the target environment. The system would compare the desired state in Git with the actual state of the environment and automatically make the necessary changes.
Why don't organizations understand that DevOps is different from gitops and what is the difference between DevOps and gitops?
It's right to point out that there's often confusion between DevOps and GitOps, and sometimes organizations don't fully grasp the distinction. This can happen for several reasons:
1. Overlapping Principles:
* DevOps and GitOps share a lot of common ground. Both advocate for automation, collaboration, continuous delivery, and a focus on infrastructure as code. This shared vocabulary can lead to blurring the lines.
* Evolutionary Connection: GitOps can be seen as an extension of DevOps. It builds on the principles of DevOps but adds a stricter framework for managing infrastructure and configurations through Git.
2. Marketing Hype:
* The "Git" Appeal: The term "GitOps" naturally catches attention because "Git" is a familiar and popular tool in the developer community. It might appear as an appealing solution without a full understanding of the underlying differences.
* "DevOps" Fatigue: The term "DevOps" has become quite common, sometimes to the point of oversaturation. Organizations might be searching for new terms and concepts, leading to an overemphasis on GitOps as a distinct and superior approach.
3. Misinterpretation of GitOps:
* GitOps as a Replacement: Some might perceive GitOps as a replacement for DevOps, rather than an extension. This misconception could lead to overlooking the broader benefits of DevOps, like fostering a collaborative culture.
* Focus on Tools: The emphasis on Git in GitOps might lead some to think it's just about using Git for deployment, overlooking the underlying principles of automation, observability, and declarative configurations.
4. Lack of Clear Understanding:
* Incomplete Adoption of DevOps: Some organizations might only have partially embraced DevOps, lacking the full understanding of its principles and practices. This makes it harder to distinguish GitOps as a distinct and complementary approach.
* Insufficient Education and Training: A lack of comprehensive education and training on both DevOps and GitOps can contribute to confusion and misinterpretation.
Why DevOps Still Matters:
While GitOps offers significant benefits, DevOps still remains a crucial foundation for successful software delivery:
* Cultural Shift: DevOps focuses on building a collaborative culture between development and operations teams. This cultural change is fundamental to efficient software delivery.
* Broader Scope: DevOps encompasses more than just infrastructure management. It addresses the entire software development lifecycle, including planning, development, testing, deployment, and monitoring.
* Flexibility and Adaptability: DevOps provides a framework for adapting to evolving technologies and processes. It's not tied to specific tools or methodologies.
Conclusion:
It's crucial to recognize that GitOps is a powerful addition to the DevOps toolset. However, it's not a replacement for DevOps. Understanding the differences and the benefits of each approach will help organizations make informed decisions about adopting and implementing them effectively.
Remember:
While GitOps can be a powerful approach, it requires careful planning and implementation. It's not a one-size-fits-all solution and might not be suitable for every team or project.
#devops vs #gitops #linux #platform #culture
https://t.iss.one/unixmens
Telegram
Academy and Foundation unixmens | Your skills, Your future
@unixmens_support
@yashar_esm
[email protected]
یک کانال علمی تکنولوژی
فلسفه متن باز-گنو/لینوکس-امنیت - اقتصاد
دیجیتال
Technology-driven -بیزینس های مبتنی بر تکنولوژی
Enterprise open source
ارایه دهنده راهکارهای ارتقای سازمانی - فردی - تیمی
@yashar_esm
[email protected]
یک کانال علمی تکنولوژی
فلسفه متن باز-گنو/لینوکس-امنیت - اقتصاد
دیجیتال
Technology-driven -بیزینس های مبتنی بر تکنولوژی
Enterprise open source
ارایه دهنده راهکارهای ارتقای سازمانی - فردی - تیمی
AI DevOps Engineer
AI Platform Engineer
AI Infrastructure Engineer
AI/ML Cloud Engineer
AI Data Infrastructure Engineer
Automation Platform Engineer
Infrastructure as Code (IaC) Architect
Infrastructure Automation Specialist
Platform as a Service (PaaS) Engineer
AI Ops Engineer (Artificial Intelligence for IT Operations)
Cloud SD-WAN Engineer
Service Mesh Engineer
Network Function Virtualization (NFV) Engineer
Network Edge Architect
Virtualized Network Engineer
Telecom Cloud Engineer
5G Cloud Architect
Cloud Connectivity Engineer
Content Delivery Network (CDN) Engineer
Software-Defined Infrastructure Engineer
lockchain Platform Engineer
Blockchain Infrastructure Engineer
DevOps Automation Architect
Smart Contract Infrastructure Engineer
Container Platform Engineer (Docker, Kubernetes, etc.)
Serverless Operations Engineer
Function-as-a-Service (FaaS) Architect
Distributed Systems Engineer
System Design Engineer
Cloud System Architect
Distributed Systems Architect
Systems Integration Engineer
Systems Design Architect
Microservices Architect
High Availability Systems Architect
Resilient Systems Engineer
Systems Performance Engineer
Scalability Architect
Large-Scale Systems Engineer
Event-Driven Architecture Engineer
Data Systems Architect
Real-Time Systems Architect
Service-Oriented Architecture (SOA) Engineer
Fault-Tolerant Systems Engineer
Systems Engineering Manager
Enterprise Systems Architect
Cloud Native System Architect
Hybrid Systems Architect
Backend Systems Architect
Systems Infrastructure Architect
Systems Monitoring and Observability Engineer
Multi-Cloud Systems Engineer
Edge Systems Architect
API Systems Architect
Platform Systems Designer
Cross-Platform Systems Architect
Modular Systems Architect
#job #jobs #linux #devops #cloud #platform
https://t.iss.one/unixmens
AI Platform Engineer
AI Infrastructure Engineer
AI/ML Cloud Engineer
AI Data Infrastructure Engineer
Automation Platform Engineer
Infrastructure as Code (IaC) Architect
Infrastructure Automation Specialist
Platform as a Service (PaaS) Engineer
AI Ops Engineer (Artificial Intelligence for IT Operations)
Cloud SD-WAN Engineer
Service Mesh Engineer
Network Function Virtualization (NFV) Engineer
Network Edge Architect
Virtualized Network Engineer
Telecom Cloud Engineer
5G Cloud Architect
Cloud Connectivity Engineer
Content Delivery Network (CDN) Engineer
Software-Defined Infrastructure Engineer
lockchain Platform Engineer
Blockchain Infrastructure Engineer
DevOps Automation Architect
Smart Contract Infrastructure Engineer
Container Platform Engineer (Docker, Kubernetes, etc.)
Serverless Operations Engineer
Function-as-a-Service (FaaS) Architect
Distributed Systems Engineer
System Design Engineer
Cloud System Architect
Distributed Systems Architect
Systems Integration Engineer
Systems Design Architect
Microservices Architect
High Availability Systems Architect
Resilient Systems Engineer
Systems Performance Engineer
Scalability Architect
Large-Scale Systems Engineer
Event-Driven Architecture Engineer
Data Systems Architect
Real-Time Systems Architect
Service-Oriented Architecture (SOA) Engineer
Fault-Tolerant Systems Engineer
Systems Engineering Manager
Enterprise Systems Architect
Cloud Native System Architect
Hybrid Systems Architect
Backend Systems Architect
Systems Infrastructure Architect
Systems Monitoring and Observability Engineer
Multi-Cloud Systems Engineer
Edge Systems Architect
API Systems Architect
Platform Systems Designer
Cross-Platform Systems Architect
Modular Systems Architect
#job #jobs #linux #devops #cloud #platform
https://t.iss.one/unixmens
Telegram
Academy and Foundation unixmens | Your skills, Your future
@unixmens_support
@yashar_esm
[email protected]
یک کانال علمی تکنولوژی
فلسفه متن باز-گنو/لینوکس-امنیت - اقتصاد
دیجیتال
Technology-driven -بیزینس های مبتنی بر تکنولوژی
Enterprise open source
ارایه دهنده راهکارهای ارتقای سازمانی - فردی - تیمی
@yashar_esm
[email protected]
یک کانال علمی تکنولوژی
فلسفه متن باز-گنو/لینوکس-امنیت - اقتصاد
دیجیتال
Technology-driven -بیزینس های مبتنی بر تکنولوژی
Enterprise open source
ارایه دهنده راهکارهای ارتقای سازمانی - فردی - تیمی
devops and bcp .pdf
1 MB