Best match

Most recent

Currituck County

MicroCAT will help to expand services into “transit desert” areas in Albermarle County, Va., where public transport is scarce.

https://www.bing.com/th?id=OVFT.TunaNI5KD8aq0x_X5yxbGi&pid=News

Albermarie County, CAT launch on-demand ride sharing pilot

https://www.bing.com/th?id=ODF.CigQv_RBGnU9_eK1ucbkkQ&pid=news

Mass Transit

Link Light Rail

East Link

The phase includes training for operators and maintenance staff and continued testing to ensure stations, tracks, utilities and vehicles work together as expected in

https://www.bing.com/th?id=OVFT.z6Rpb0CwSgPlhkT2H71vnS&pid=News

Sound Transit enters pre-revenue phase on East Link light-rail extension project

Michael Bloomberg

Russia

European Union

The next round of EU sanctions on Moscow could hit more than 5 billion in trade according to Bloomberg sources Read Full Article at RTcom

https://www.bing.com/th?id=OVFT.Aorg3Fe66LSMZ7Y_nB-3KC&pid=News

EU looks to expand sanctions on Russia - Bloomberg

https://www.bing.com/th?id=ODF.k6O3sRggnv9dZCaM2w5RLw&pid=news

Big News Network.com

The Washington Informer

All of that has led to a $750 million budget shortfall that will slam the transit system when federal pandemic funds run out in July 2024 — unless contributing jurisdictions step up to provide more funding. Metro has released some of the “doomsday ...

EDITORIAL: The DMV Cannot Let Metro Fall Off the Fiscal Cliff

Howard County

Outline of transport

Bicycle safety

The meeting, at the George Howard Building in Ellicott City, included representatives from the Maryland Department of Transportation, the Maryland State Highway Administration, the Motor Vehicle Administration, Maryland Transit Administration and Maryland ...

Howard County and state officials outline transportation priorities, bicycle safety improvements

Yahoo News

From Hollywood's death-dealing Terminator to warnings from genius Stephen Hawking or Silicon Valley stars, fears have been fueled that artificial intelligence (AI) could one day destroy humanity. Tech titans are racing toward creating AI far smarter than ...

https://www.bing.com/th?id=OVFT.TpDsUD_mJ0PlqjVKw-8Z1i&pid=News

AI anxiety as computers get super smart

San Francisco Examiner

Arapahoe County

Corridor

Colorado

The presentation and questionnaire are available through Nov. 6, 2023.

https://www.bing.com/th?id=OVFT.iWa3qJghUcpT4fgzAIJbMi&pid=News

CO Highway 7 (Arapahoe Ave.) corridor planning team seeks input

https://www.bing.com/th?id=ODF.2_D_q1qvrwb9yyvECmbQHQ&pid=news

Longmont Leader

Europe

Permit

Peace

DALLAS — Air Peace (P4) recently obtained the necessary permits that allow it to operate flights into the United Kingdom. The secured permits include the Foreign Carrier Operator Permit (FCOP), which allows airlines from other regions to fly to Europe,

https://www.bing.com/th?id=OVFT.EIm1JKRNzuCcUQ3OlZTCbS&pid=News

Air Peace Secures Flight Permit to Europe, the UK

https://www.bing.com/th?id=ODF.RRPFQJ6RIZPmwStrcwLVjg&pid=news

Airways

North Quincy

Massachusetts Bay Transportation Authority

Slow zone

First identified by work crews before Labor Day in 2022, the Red Line slow zone was “being removed” as of Wednesday morning. Here is its story.

https://www.bing.com/th?id=OVFT.VgpKKdnYXjQOtYYQjvtgoy&pid=News

The MBTA just eliminated one of its longest-lasting slow zones

https://www.bing.com/th?id=ODF.D5N6ynx7QyTc8HOh5j9zvQ&pid=news

The Boston Globe

Seattle

Train station

Light rail

The man accused of randomly attacking multiple people with a hammer at the Beacon Hill Link light rail station is expected to appear in court Wednesday morning.

https://www.bing.com/th?id=OVFT.C-wBxY_LqGt5mofW34bnEC&pid=News

Man charged with Seattle light rail station hammer attack expected in court

https://www.bing.com/th?id=ODF.Nwhu7HbZPeS5Fj1x-Mt3RQ&pid=news

komonews

Get the most recent info and news about Transit on HackerNoon, where 10k+ technologists publish stories for 4M+ monthly readers.

Transit simplifies local travel in more than 200 cities worldwide. Right on launch, it shows you all nearby transport options and departure times in big text and bright colours. Users can plan trips, set reminders, and get notifications about disruptions. Plus, Transit also integrates other sustainable transport modes — bikeshare, scooters, carshare, and ridehail — so users can determine the best way to get from A to B.

Transit

In many major cities, public transportation has been suffering from the decrease in profitability and reliability, as well as poor customer experience. As the global economy continues to shift to an on-demand model, commuters expect more personalized services and more pleasant experience, that rely on technology. Meet Mobility-as-a-Service (MaaS) — a solution that integrates public and private transportation into one system. Think of using one mobile app for multiple modes of transportation (bike, shared car, train…) to get to your destination and paying one fee for that journey. The payment will be distributed between all operators. The technology will connect vehicles, public transit, and infrastructure with the customers and will offer flexible and safe travel. In 2019–2024, we will see broader use and adoption of MaaS due to the advancements in and machine learning and the increasing adoption rates of unconventional transportation modes, such as bike- and car-sharing services. IoT According to , MaaS will have a “disruptive impact on traditional transportation modes like car ownership, buses, trains, aviation, taxis and rental cars.” ABI Research This idea is being tested around the world and relies heavily on IoT technology. MaaS needs real-time vehicle connectivity and artificial intelligence to plan trips, optimize routes, and shorten travel times. Without knowing each vehicle’s precise location and status, in addition to other data, such as traffic and maintenance information, usability of MaaS will suffer. The mobility algorithm will calculate the most appropriate travel option from the user’s location to the destination and provide the optimal combination of transportation types. Travel options will account for scheduled maintenance (based on asset utilization) and unexpected breakdowns. While artificial intelligence and route optimization are already at work at Google, Uber, and others, IoT in mass transit is in a nascent phase. Both AI and IoT will become much more widespread in the transportation sector in the next 2–3 years, with IoT accelerating its adoption rate even faster. For example, companies like use IoT to collect and analyze traffic data to anticipate traffic issues. DENSO A journey planner will be an inherent part of the solution and will unite all means of transportation in a single network. The application will be always aware of each vehicle’s location and status and will provide the users with the precise arrival and departure times for each leg. There’s a clear benefit to the end user: simplicity of journey planning, shorter travel, and, likely, a lower price. Helsinki rolled out a , which brings together public transportation, taxis, city bikes, and car-sharing services. The app enjoyed strong support from the city and the community. MaaS solution MaaS isn’t without caveats. Public transportation, subsidized by the local taxpayers, often has complicated cost structures that may make it difficult to figure out which part of the total fee should be attributed to each of the types of transportation used in a journey. Public mass transit can also be slow to adopt new technologies — and all that can hinder the development of MaaS. Nonetheless, public sector is the backbone of MaaS solutions, which will get people out of private cars into shared transportation mode and benefit economic activity by lowering transportation costs. future

The Future of Mass Transit and IoT

The job market is ever-evolving, shaped by technological advancements, economic shifts, and global trends. Analyzing the current job market reveals a dynamic landscape. Industries such as technology, healthcare, and sustainable energy are witnessing significant growth, offering many opportunities. Conversely, traditional sectors might be experiencing a decline. Understanding these trends provides a foundation for career change strategies in 2024. As we enter 2024, understanding the current job market trends is crucial for those considering a career change. I will share some tips on successfully transitioning to a new industry or role here. Analyzing Job Market Trends for Industry Transition Guide Self-Assessment Before Transitioning Before embarking on a career change journey, conducting a self-assessment is crucial. Running a personal skills and interests audit involves introspection and a realistic evaluation of one's strengths, weaknesses, passions, and skills. This self-awareness serves as a compass, guiding individuals toward cross-industry skill transfer. Reskilling for Career Shifts Technology and automation are across industries. While they bring forth efficiency and innovation, they also alter the skills landscape. Jobs involving creativity, critical thinking, and emotional intelligence are gaining prominence, highlighting the need for individuals to adapt and acquire relevant skills to stay competitive in the job market. reshaping job roles Aligning personal values with career goals is fundamental for long-term satisfaction and success. Entering a new industry requires . The journey of developing new skills begins with a clear roadmap. In the digital age, numerous resources facilitate skill acquisition. acquiring new skills From online courses on platforms like LinkedIn Learning and Coursera to intensive boot camps and industry-recognized certifications, individuals can enhance their skill set. Leveraging Technology to Market Skills Transferable skills play a pivotal role in making a successful career transition. Understanding the is essential. Crafting resumes and cover letters that showcase transferable skills is an art. transferability of skills Tailoring applications to highlight relevant experiences and skills is necessary, increasing the chances of securing interviews in a new industry. is also an effective networking strategy for career pivot planning. Building a professional network requires strategic efforts. Social media is critical in professional networking in this digital age. Job seekers must leverage platforms like LinkedIn to expand one's professional network and create meaningful connections in the new industry. Networking Building a Personal Brand for the New Industry is essential when transitioning to a new industry. The strategy requires creating strategies for updating online profiles, crafting personal branding statements, and communicating the value of previous experience in the context of the new industry. Rebranding oneself An online presence is often the first impression employers have. Job seekers must update their profiles on LinkedIn, personal websites, and other online platforms to align with the new industry practices. Effectively communicating the value of previous experience is a crucial aspect of rebranding. Individuals must know how to articulate their skills and achievements in a way that resonates with the requirements of the new industry. Acquiring temporary positions, internships, and volunteering opportunities can be valuable for gaining industry experience. To ensure that you receive maximum benefits, it is essential to identify relevant options that can help you gain practical experience and build credibility in your chosen field. These opportunities can provide insights into the day-to-day workings of the industry. Volunteering and seeking out can facilitate a smoother transition to a new career path. mentors Navigating the Emotional Challenges of Career Changes Career change often comes with emotional challenges. It is essential to address the psychological aspects of transition, creating strategies for dealing with uncertainty and fear of change and maintaining a positive mindset throughout the journey. Uncertainty is a common emotion during a . You should know effective coping strategies for navigating uncertainties and confidently making informed decisions. A positive mindset is a crucial driver of success. career transition Maintaining optimism, resilience, and a forward-looking attitude is essential, even in the face of challenges encountered during a career change. Interviewing Techniques for Career Changers Interviewing for a new industry requires specific preparation. During the interview, you should explain the reasons for a career transition to potential employers. During interviews, an essential part is framing the career change as a strength rather than a weakness. You must communicate transferable skills and highlight relevant experiences to project your image as valuable assets to potential employers. Effectively explaining the reasons for a career transition is crucial. It would be best if you communicated the decision to switch industries in a way that emphasizes growth, adaptability, and a genuine passion for the new field. Planning for Financial Stability During Career Transitions Embarking on a career change may come with financial implications. You must budget for potential gaps in employment and address the financial considerations of retraining and potentially starting in a new industry at a different position or salary level. Planning for potential gaps in employment is a prudent financial strategy. It is essential to gain skills related to budgeting, saving, and creating a financial safety net to navigate transition periods. Retraining for a new career often requires a financial investment. It is essential to carefully consider the financial implications of pursuing additional education or certifications. To navigate a career change in 2024, taking a multifaceted approach that includes self-assessment, upskilling, networking, and strategic planning is essential. By implementing these strategies, individuals can successfully transition into a new industry and thrive in the changing job market. Remember, a career change is not just a shift in employment; it presents an opportunity for personal and professional growth. About the Author is a marketing and growth expert with extensive experience scaling venture-backed hyper-growth startups such as Tynker, Roku, IMVU, Texture, and TrustedID. He is also the author of " ," a book that is part of the bestselling "The Lean Startup" series by Eric Ries. Lomit Patel Lean AI

Your Career Path: A Step-by-Step Guide to Navigating Industry and Role Transitions in 2024

আপনার কর্মজীবনের পথ: 2024 সালে নেভিগেট শিল্প এবং ভূমিকা পরিবর্তনের জন্য একটি ধাপে ধাপে নির্দেশিকা

Ihr Karriereweg: Eine Schritt-für-Schritt-Anleitung zur Bewältigung von Branchen- und Rollenwechseln im Jahr 2024

Su trayectoria profesional: una guía paso a paso para navegar por la industria y las transiciones de roles en 2024

Votre cheminement de carrière : un guide étape par étape pour naviguer dans les transitions d'industrie et de rôle en 2024

आपका कैरियर पथ: 2024 में उद्योग और भूमिका परिवर्तन को नेविगेट करने के लिए एक चरण-दर-चरण मार्गदर्शिका

あなたのキャリアパス: 2024 年の業界と役割の変遷をナビゲートするためのステップバイステップ ガイド

진로: 2024년 업계 및 역할 전환을 위한 단계별 가이드

Seu plano de carreira: um guia passo a passo para navegar na indústria e nas transições de funções em 2024

Ваш карьерный путь: пошаговое руководство по смене отраслей и ролей в 2024 году

Kariyer Yolunuz: 2024'te Endüstri ve Rol Geçişlerinde Yön Bulmanıza Yönelik Adım Adım Kılavuz

Con đường sự nghiệp của bạn: Hướng dẫn từng bước để định hướng chuyển đổi ngành và vai trò vào năm 2024

您的职业道路：2024 年行业和角色转变的分步指南

DevOps for Beginners: Navigating the Transition from Traditional Development

On October 5th, Rails 7.1 has been released. In this article, I will show you how I upgraded one of our projects, OneTribe ( ), to the new major release within one day of my holidays. https://onetribe.team/ Prerequisites OneTribe runs Ruby 3.2.2 and Rails 7.0.7. We host on GitHub and deploy with GitHub Actions and Kamal. code Dependencies Update I started with upgrading rails in the application Gemfile. # Gemfile
gem 'pg_party'

# ...

gem 'rails', '~> 7.1.0'
gem 'rails-i18n' After this, you can try to run and depending on your other dependencies, it will either succeed or fail. In my case, it failed because does not support Rails 7.1 yet. bundle update rails pg_party The good news is that Ryan (author and maintainer of PgParty), with help from me and one more developer, within one evening, but didn’t release the new version of the gem yet, so I am going to take the code from the branch. managed to add support for AR 7.1 main # Gemfile
gem 'pg_party', github: 'rkrage/pg_party' After solving the issue with the PgParty bundle, it succeeded. I was almost sure that the application was ready for the next phase of the update, but I remembered that Rails 7.1 introduced composite primary keys for ActiveRecord support out of the box (you can find a full list of new features and improvements here: ). https://rubyonrails.org/2023/10/5/Rails-7-1-0-has-been-released In OneTribe, we’ve used the gem called ( ). It was rather easy; I replaced call with and removed from the application bundle. composite_primary_keys https://github.com/composite-primary-keys/composite_primary_keys self.primary_keys = <array> self.primary_key = <array> composite_primary_keys class TimeTracking::Entry < TimeTrackingRecord
	# with composite_primary_keys
	# self.primary_keys = :id, :date

	# with ActiveRecord 7.1
  self.primary_key = [:id, :date]

  range_partition_by :date
	
	# ...
end After this, I updated Sidekiq to 6.5.11, , and tried to start the application. However, I got an error. which added support to Rails 7.1 ActionText in Rails 7.1 introduced a new HTML 5 sanitizer, which is now default and falls back to HTML 4. As a result of this change, and are applied at runtime and return nil during application load. ActionText::ContentHelper.allowed_tags .allowed_attributes In our case, I don’t need additional tags to be added to ActionText allowed tags configuration, and I removed the initializer. I ran the application test suit, and all specs passed successfully, meaning I can start . rails app:update Application Configuration Update Rails has a special task that can help you to update application configuration in an interactive mode. I used VS Code for development and wanted to use its merge tool, so I specified the THOR_MERGE constant before running the command and used the merge tool to track changes over files. rails app:update THOR_MERGE="code --wait" ./bin/rails app:update One notable change in the 7.1 release is that option with that has an inverted meaning. Both options will still work for backward compatibility, but I suggest to replace with in  environments configuration files. config.cache_classes has been replaced config.enable_reloading config.cache_classes = false config.enable_reloading = true Another new configuration option of Rails 7.1 is . I always try to reduce the number of callbacks used in controllers since they can be extremely hard to maintain. However, there may be situations when controller callbacks fit well (e.g., authorization check). Conditional callbacks are an even bigger hell. Before Rails 7.1, if you defined a condition with or option for an action that does not exist, Rails would say nothing. Now, you can set for test and development environments, and Rails will raise an exception. You can read more info in the railties changelog: . config.action_controller.raise_on_missing_callback_actions only except config.action_controller.raise_on_missing_callback_actions=true https://github.com/rails/rails/blob/7-1-stable/railties/CHANGELOG.md In my Kamal guide, I showed how to create an initializer, which will deal with a load balancer that terminates SSL (e.g., AWS ALB). Rails 7.1 introduced option. This means that in environments that work behind a load balancer (usually production, staging, etc.), you have to enable it and delete the initializer that you used in Rails 7.0. config.assume_ssl=true # config/environments/production.rb

# Assume all access to the app is happening through a SSL-terminating reverse proxy.
# Can be used together with config.force_ssl for Strict-Transport-Security and secure cookies.
config.assume_ssl = true

# Force all access to the app over SSL, use Strict-Transport-Security, and use secure cookies.
config.force_ssl = false After you merge all your configuration files and the interactive tool is finished, some tweaks can still be done. First of all, you may notice that you will have a new file in your code base called . It contains all Rails 7.1 default params commented, so you can enable them one by one. Another option is to change in file to have value and delete , this will enable all options at once. new_framework_defaults_7_1.rb config.load_defaults config/application.rb 7.1 new_framework_defaults_7_1.rb Last but not least is option. Before 7.1, you probably had something similar to the code below in your application that uses Zeitwerk. config.autoload_lib # config/application.rb

module OneTribe
  class Application < Rails::Application
    config.eager_load_paths << config.root.join("lib")

    Rails.autoloaders.main.ignore(
      config.root.join("lib").join("assets"),
      config.root.join("lib").join("tasks"),
      config.root.join("lib").join("middleware"),
    )

    # ...
  end
end The code above added folder to both eager load and autoload paths and excluded from autoload paths from lib that didn’t contain or should not be reloaded or eager-loaded. lib Ruby code With Rails 7.1 and , everything becomes easier. You just tell Rails to autoload everything in and provide a list of folders that should not be reloaded and eager-loaded. config.autoload_lib lib # config/application.rb

module OneTribe
  class Application < Rails::Application

    # Please, add to the `ignore` list any other `lib` subdirectories that do
    # not contain `.rb` files, or that should not be reloaded or eager loaded.
    # Common ones are `templates`, `generators`, or `middleware`, for example.
    config.autoload_lib(ignore: %w[assets tasks middleware])

		# ...
  end
end Thats all. I reran my specs to ensure I didn’t break anything. Of course, I ran Rubocop to ensure all the changes fit the code style, created PR, and successfully upgraded OneTribe to the new Rails version. Conclusions Rails 7.1 gives you many new features and abilities ( ), but as usual, the upgrading process is smooth and straightforward. https://rubyonrails.org/2023/10/5/Rails-7-1-0-has-been-released Thanks to all the contributors, the core team, and those who tested the release candidate and beta builds! Also published . here

How We Upgraded to Ruby on Rails 7.1: A Smooth Transition

MacMan: Your Handbook to Transitioning From Windows to Mac as a Developer [Part 1]

Introduction As Kubernetes continues to mature as the leading container orchestration platform, security remains a paramount concern for organizations deploying containerized applications. Among the fundamental tools in Kubernetes' security arsenal, once played a pivotal role. PSP allowed administrators to meticulously define and enforce security constraints on Pods, ensuring that only containers meeting specific security standards could operate within the cluster. However, the landscape of Kubernetes security is evolving rapidly, and it's important to note that PSP has now been deprecated, starting with Kubernetes 1.25 (see link to Kubernetes 1.25 Urgent Release notes). This change stems from various factors, including the complexity of managing and maintaining PSP policies, often leading to operational challenges for users. In response to the deprecation, organizations are now looking for modern alternatives to PSP, ones that not only address security requirements but also streamline the process of securing workloads in . In this comprehensive guide, we embark on a journey to navigate this shift in Kubernetes security practices, focusing on the transition to Pod Security Admission (PSA). PSA is one of the most robust alternatives available, and this article explores it in-depth. However, it's worth mentioning that two other alternatives, Kyverno and OPA Gatekeeper, will be covered in separate articles within this series. Throughout this article, you will find detailed instructions for setting up and installing PSA, step-by-step migration guides to transition from PSP to PSA smoothly, and precise commands for transferring existing PSP rules to PSA. Additionally, you will gain the knowledge to assess namespaces for migration readiness using dry-run commands tailored to PSA. By the end of this guide, you will gain a comprehensive understanding of the strengths and limitations of PSA, equipping you to make an informed decision based on your organization's specific security requirements and Kubernetes environment. With this guide, you can confidently modernize your Kubernetes security practices, ensuring that your workloads remain protected as you bid farewell to the era of Pod Security Policies. Pod Security Policies (PSP) Kubernetes Pod Security Admission (PSA) PSA ensures containers adhere to Kubernetes' native security standards, which are defined by the Pod Security Standards. These standards classify security policies into three distinct profiles, each with a different level of restrictiveness: PSA Enforces Kubernetes Security Standards: : The Privileged policy is intentionally open and entirely unrestricted. Typically, this policy targets system- and infrastructure-level workloads managed by trusted users. It is characterized by an absence of restrictions. While allow-by-default mechanisms like Gatekeeper may inherently be Privileged, for deny-by-default mechanisms such as Pod Security Policy (PSP), the Privileged policy should deactivate all restrictions. Privileged : The Baseline policy is designed for easy adoption by common containerized workloads while preventing known privilege escalations. It caters to application operators and developers of non-critical applications. Baseline : The Restricted policy is focused on enforcing rigorous Pod hardening best practices, albeit at the potential expense of some compatibility. It primarily targets operators and developers of security-critical applications, as well as lower-trust users. For a comprehensive list of controls that should be enforced or disallowed under each profile, you can refer to the official documentation. Restricted Unlike some other solutions, PSA does not offer a straightforward method for directly migrating or modifying Pod Security Policy (PSP) rules. PSA's primary focus is on validating pods against the established , including the profiles mentioned above. No Direct PSP Rule Transfer: Kubernetes security standards : While PSA is effective at validation, it cannot modify or customize pod specifications as PSP could. PSA's main purpose is to enforce predefined Kubernetes security standards and does not include features for altering or mutating pod specifications. It primarily focuses on validating pods against these established standards. No Mutations Setup and Installation Since PSA is a Kubernetes Native component, to make it work, you just need to ensure that the Pod Security Admission (PSA) controller is enabled in your Kubernetes cluster. You can do that by running  the following command: kubectl api-versions | grep admission Prep Steps for Migration Assess Namespace Permissions Control of Pod Security Admission is influenced by namespace labels. This implies that individuals with the capability to update, patch, or create namespaces also have the authority to modify the Pod Security settings for those namespaces. This modification could potentially bypass stricter security policies. Before proceeding, it is essential to verify that namespace permissions are assigned exclusively to trusted and privileged users. It is advisable to refrain from granting these elevated permissions to users who do not require such access. If additional constraints are needed for configuring Pod Security labels on Namespace objects, consider utilizing an admission webhook to enforce those restrictions. Streamline and Normalize PodSecurityPolicies Before migrating to Pod Security Admission (PSA), it is beneficial to normalize your PodSecurityPolicies (PSP): : Eliminate options not covered by the Pod Security Standards. These options include: Remove Unsupported Fields .spec.allowedHostPaths

.spec.allowedFlexVolumes

.spec.allowedCSIDrivers

.spec.forbiddenSysctls

.spec.runtimeClass : Initiate the process by removing fields that solely have a mutating effect and do not impact the validation policy. These fields, as also mentioned in the "Mapping PodSecurityPolicies to Pod Security Standards" reference, include: Eliminate Purely Mutating Fields .spec.defaultAllowPrivilegeEscalation
.spec.runtimeClass.defaultRuntimeClassName
.metadata.annotations['seccomp.security.alpha.kubernetes.io/defaultProfileName']
.metadata.annotations['apparmor.security.beta.kubernetes.io/defaultProfileName']
.spec.defaultAddCapabilities Important Note: Removing these fields may lead to workloads lacking necessary configurations, which could potentially cause operational issues. It is crucial to ensure that workloads can function correctly with the simplified policies. Determine the Suitable Pod Security Level When determining the appropriate Pod Security level for your namespace, you have several methods to consider: By Security Requirements for the Namespace If you are familiar with the expected access level and security requirements for the namespace, you can select an appropriate Pod Security level based on those specific requirements. This approach is similar to how you would approach security settings in a new cluster. By Existing PodSecurityPolicies: Utilize the reference to map each of your existing Pod Security Policies (PSPs) to a corresponding Pod Security Standard level. If your PSPs are not originally based on the Pod Security Standards, you may need to make a decision. Choose a Pod Security level that is at least as permissive as your PSPs, or opt for a level that is at least as restrictive. To identify which PSPs are in use for pods within a specific namespace, use the following command: "Mapping PodSecurityPolicies to Pod Security Standards" kubectl get pods -n $NAMESPACE -o jsonpath="{.items[*].metadata.annotations.kubernetes\.io\/psp}" | tr " " "\n" | sort -u By Existing Pods: Conduct a dry run and apply the label command from the next section to test both the Baseline and Restricted Pod Security levels. This helps you assess whether these levels are sufficiently permissive for your existing workloads. Choose the least-privileged valid level that aligns with your existing workloads. It's important to note that the mentioned options are based on existing pods, which may not account for workloads that are not currently running. This includes CronJobs, scale-to-zero workloads, or other workloads that have not yet been deployed. Testing the Pod Security Level Once you've determined the Pod Security level for your namespace (except for the Privileged level), it's important to validate the chosen policy. Pod Security offers testing options to ensure a smooth rollout and compliance with security standards. Dry Run Testing: Use this method to assess the impact of the selected policy without immediate enforcement. To perform a dry run, use the following command, which will highlight any existing pods that do not meet the specified policy level: kubectl label --overwrite ns $NAMESPACE pod-security.kubernetes.io/enforce=$LEVEL Audit Mode Testing: Audit mode allows you to record policy violations without enforcing them. Violating pods are logged in the audit records for later review. Enable audit mode with the command: kubectl label --overwrite ns $NAMESPACE pod-security.kubernetes.io/audit=$LEVEL If unexpected policy violations arise during testing, you can: Update non-compliant workloads to align with the policy. Adjust the Pod Security level for the namespace if necessary to accommodate your workload requirements. Enforcing the Pod Security Level Once you are confident that the selected Pod Security level is appropriate for your namespace, you can proceed to enforce it. This step ensures that the desired security standards are actively applied to your workloads within the namespace. To enforce the desired Pod Security level on the namespace, use the following command: kubectl label --overwrite ns $NAMESPACE pod-security.kubernetes.io/enforce=$LEVEL Executing this command will activate and enforce the specified Pod Security level, enhancing the security posture of your namespace. Bypassing PSP To effectively bypass PodSecurityPolicy at the namespace level, you can bind a fully privileged Pod Security Policy (PSP) to all service accounts in the namespace. This process ensures that pods within the namespace are no longer subjected to modifications or restrictions imposed by PodSecurityPolicy. You can do that at a cluster level or at an individual namespace level. Cluster-Scoped Setup (Needed Only Once for the whole cluster): Create a fully privileged Pod Security Policy (PSP) by applying a YAML configuration file, such as . This PSP should grant all necessary privileges to pods and create a cluster role named privileged-psp to allow the use of Pod Security Policies (PSPs) and associate it with the privileged PSP: privileged-psp.yaml kubectl apply -f privileged-psp.yaml
kubectl create clusterrole privileged-psp --verb use --resource podsecuritypolicies.policy --resource-name privileged Per-Namespace Disablement: Create a role binding in the target namespace to associate the privileged-psp cluster role with the group. This binding effectively grants all service accounts within the namespace access to the fully privileged PSP, bypassing PodSecurityPolicy: system:serviceaccounts:$NAMESPACE kubectl create -n $NAMESPACE rolebinding disable-psp --clusterrole privileged-psp --group system:serviceaccounts:$NAMESPACE With this setup, the privileged PSP is non-mutating, and the PodSecurityPolicy admission controller always prioritizes non-mutating PSPs. As a result, pods in this namespace will no longer be modified or restricted by PodSecurityPolicy. One advantage of this approach is its reversibility. If any issues arise, you can easily roll back the change by deleting the RoleBinding associated with disabling PodSecurityPolicy. Ensure that pre-existing Pod Security Policies remain in place during this process. Undo PodSecurityPolicy Disablement: To revert the PodSecurityPolicy disablement for the namespace, simply delete the RoleBinding created earlier: kubectl delete -n $NAMESPACE rolebinding disable-psp Revisit Namespace Creation Processes With existing namespaces updated to enforce Pod Security Admission, it's essential to review and update your processes and policies for creating new namespaces. This ensures that new namespaces are configured with an appropriate Pod Security profile from the outset. Consider the following steps to enhance namespace creation processes: : Update your organization's policies and procedures for creating new namespaces to include the selection and application of the desired Pod Security level. Ensure that security standards are established right from the creation stage. Adjust Namespace Creation Policies You can statically configure the Pod Security admission controller to define default enforcement, audit, and/or warning levels for unlabeled namespaces. This approach ensures that namespaces lacking explicit Pod Security labels still adhere to your specified security standards by default. Static Configuration: By revisiting your namespace creation processes, you can seamlessly integrate Pod Security standards into y and maintain a consistent and secure approach across all namespaces, old and new. our Kubernetes environment Disable PodSecurityPolicy Once you are confident that the PodSecurityPolicy (PSP) admission controller is no longer needed and that Pod Security Admission (PSA) has been successfully implemented and validated, you can proceed to disable the PSP admission controller. Here are the steps to disable the PSP admission controller: Modify kube-apiserver Configuration: Open the configuration file for your kube-apiserver, typically located at /etc/kubernetes/manifests/kube-apiserver.yaml. Add the flag to disable the PSP admission controller. Ensure that it's removed from the list of active admission plugins. --disable-admission-plugins kube-apiserver --disable-admission-plugins=PodSecurityPolicy Save the configuration file. Restart kube-apiserver: Restart the kube-apiserver to apply the changes. You can usually achieve this by restarting the Kubernetes control plane or the kube-apiserver pod itself. systemctl restart kubelet Verification: Ensure that the PSP admission controller is disabled by checking the kube-apiserver logs or its status. After sufficient "soak time" to be confident that you won't need to roll back to PSPs, proceed to the next step. Cleanup PSP Resources: With the PSP admission controller disabled and PSA in place, you can safely delete your existing PodSecurityPolicies, as well as any associated Roles, ClusterRoles, RoleBindings, and ClusterRoleBindings. kubectl delete podsecuritypolicies --all
kubectl delete roles,clusterroles,rolebindings,clusterrolebindings --selector=rbac.authorization.kubernetes.io/autoupdate=true This cleanup step ensures that there are no residual PSP configurations in your cluster. By deactivating the PSP admission controller and eliminating PSP-related resources, you simplify your cluster's security architecture, completing the transition to Pod Security Admission. Summary In this comprehensive guide, we've explored the essential steps and considerations for smoothly transitioning your from Pod Security Policies (PSP) to Pod Security Admission (PSA). This migration ensures that your workloads continue to run securely while aligning with Kubernetes' evolving security standards. Kubernetes cluster's security framework Pros and Cons of using Pod Security Admission (PSA) Pros: : PSA is an integral part of Kubernetes, eliminating the need for third-party tool installations. It leverages the platform's built-in security features. Native Kubernetes Component : PSA aligns with Kubernetes' native security standards, ensuring compliance with the platform's best practices. Enforces Kubernetes Standards Cons: : PSA may not provide the same level of customization as PSP, especially for complex security policies that require mutation of pod specs. Limited Customization : Existing workloads must be updated to include security context settings, which may require modification of YAML files. Retrofitting Required This guide equips you with the knowledge and steps required to migrate confidently from PSP to PSA, ensuring a secure and efficient transition while safeguarding your Kubernetes workloads. Stay tuned for upcoming articles, where I will explore alternative migration paths to Kyverno and OPA Gatekeeper.

Migrating from Pod Security Policies: A Comprehensive Guide (Part 1: Transitioning to PSA)

পড নিরাপত্তা নীতি থেকে স্থানান্তর: একটি ব্যাপক নির্দেশিকা (পর্ব 1: PSA-তে রূপান্তর)

Migration von Pod-Sicherheitsrichtlinien: Ein umfassender Leitfaden (Teil 1: Übergang zu PSA)

Migración desde políticas de seguridad de pod: una guía completa (Parte 1: Transición a PSA)

Migration à partir des politiques de sécurité des pods : un guide complet (Partie 1 : Transition vers PSA)

पॉड सुरक्षा नीतियों से माइग्रेट करना: एक व्यापक मार्गदर्शिका (भाग 1: पीएसए में परिवर्तन)

ポッド セキュリティ ポリシーからの移行: 包括的なガイド (パート 1: PSA への移行)

포드 보안 정책에서 마이그레이션: 종합 가이드(1부: PSA로 전환)

Migração de políticas de segurança de pod: um guia abrangente (Parte 1: transição para PSA)

Миграция с политик безопасности Pod: подробное руководство (Часть 1: Переход на PSA)

Pod Güvenlik Politikalarından Geçiş: Kapsamlı Bir Kılavuz (Bölüm 1: PSA'ya Geçiş)

Di chuyển từ Chính sách bảo mật Pod: Hướng dẫn toàn diện (Phần 1: Chuyển sang PSA)

从 Pod 安全策略迁移：综合指南（第 1 部分：过渡到 PSA）

Choosing the right data solution for your business can be a challenging process because there's a wide selection of them, and even the same data can be processed and packaged differently. I'm here to help you understand when you should consider using , why this solution is popular, and when it might not be the right choice for your company. database APIs What are database APIs? Let's start with a definition of a database API. To put it simply, an application programming interface (API) is a technology that allows applications to extract and exchange data. Data vendors from the web data industry offer APIs as a method for clients to get specific types of their data. An API may be used for getting data that is used internally for generating insights or powering some part of your project on the back end, but it can also be integrated into the user-facing tools, such as search engines of a platform you're building. In this article, we will be specifically analyzing database APIs, which make it easy for companies to extract relevant data from data vendors' databases. When should you use a database API Based on my experience, there are various ways that companies can benefit from having direct access to fresh B2B data on demand, but there are a few common situations when this data solution is the most convenient option. All in all, you can decide if an API is a good data solution for your business from the perspective of the product, overall readiness, budget, tooling, and technology. First, let's talk about the budget. Compared to, say, datasets, APIs are often the cheaper option popular among companies with smaller budgets for data. Budget limitations are closely related to the limitations of the project itself. You may be in the very early stages of developing a new project. Naturally, you will likely consider starting with a POC (proof of concept) to build something that doesn't require a lot of investment regarding resources. What's more, when it comes to opting for a data API during the POC stage, if you're at the very early point of your product development, likely, you don't have the processes in place that allow you to combine, process, and use large volumes of data or data from multiple sources at once. Because a database API is a tool that can be integrated into an interface available to users, for example, a search field of a dashboard, it already saves a company from a lot of hassle. When using a data API, what's left to do is some processing that would make the information more tailored to the product, like eliminating irrelevant fields and visual presentation of data. When using the API, the database's maintenance is the data vendor's responsibility. Another important question when choosing a data solution is if you already have a data pipeline and work with other data vendors. If you already have your database and your product is based on it, you may benefit more from buying an extensive dataset. If you want to enrich or update specific data records in your database, an API would be a suitable solution, so it's important to consider these questions. To sum up, here's what you should take into consideration: Budget; Product maturity level; Data team setting; Technological capabilities; Existing data pipeline (if you have one). Choosing a Database API The most important thing to remember is that a data API is as good as the data you get when using it. Additionally, data freshness and coverage may be important factors to consider if they are relevant to your product. Data quality. When it comes to freshness, it's important to evaluate if the data connected to the API is not stale. If data is not updated regularly, it won't be suitable for tracking changes or discovering something. Data freshness. If you're considering using a database API that provides scraped data from a specific source relevant to you, it's important to evaluate how raw is the data you're getting. When processing and transforming scraped data, the provider makes changes, for example, combines multiple sources, merges, or creates new data fields, and as a result, this data might no longer suit your use case. On the other hand, it might be a benefit. It all depends on business needs. Raw data. Take into account compliance and data security measures. A database API is a two-way exchange of information. You reveal sensitive business information by querying a database, so choose your data partners wisely. Check social proof like reviews and testimonials of data provider's clients before committing. Provider's reliability. I recommend finding an experienced data vendor because the web data industry is prone to changes that can be challenging to adjust to without expertise. Provider's experience. Example use cases of database APIs To give examples of how companies leverage database APIs, I must provide some context about a solution I am working with. Our clients are businesses that need fresh B2B data and often come from HR technology, sales technology, and investment industries. Using database APIs, they can get public company, employee, and job data scraped from public web sources. Here are some examples of what our APIs are used for: Investment research An investment company can use a database API to get data on companies they are interested in or to find new opportunities by looking for promising entrepreneurs. For example, a company data API may be used to get as much valuable data as possible about a company when the investment firm only has its website URL. Investors may also be interested in getting data on the talent pool of that company, such as checking previous workplaces of the people in leadership positions. Data Enrichment Companies that help businesses find the best-fit talent benefit from database APIs because they get access to extensive datasets containing information about business professionals. Do you need to have data on as many candidates as possible at all times, or do you need specific data records of candidates that fit specific criteria? Especially if the data is being refreshed regularly, an API is a great tool for sourcing potential candidates that fit specific criteria or for enriching data on candidates they already have in their database. Lead generation Similarly to the examples mentioned above, sales technology companies use APIs to get data on companies and business professionals that fit their ideal customer profile criteria and may be interested in their products. Database API limitations Although the examples above show various ways to use a database API, there are also some possible limitations. One is that querying the database is usually possible in the frame of specific search criteria. So, it is not a convenient option if you want to find insights about open-ended questions, like global trends of particular industries. Another reason might be that you have passed the POC phase, and an API doesn't meet your scaling ambitions - you might prefer using large files and consuming data differently. Not having to manage a database on your own is a benefit, but at the same, it makes an API user quite dependent on the availability of the API. Whether you are the API response's end receiver or your platform's client, service discrepancy might cause issues. Of course, there are other ways to avoid that, such as having a plan B when data needs to be accessed offline. Similar to what I've discussed earlier, the reliability of the data provider can also become a limitation, especially due to issues related to prompt communication. For example, if a data provider changes the data structure or even a little part of it, like a data field that is relevant to you, it might affect your operations. Even the smallest changes might require quite a bit of preparation on your end, so it is important to get notified early. Consistency is essential when working with web data, and a reliable provider can ensure it, but using an API still means you have less control in some situations. Database APIs vs. Raw Datasets In my experience in the web data industry, the need for creating a database API product came from working with companies that want raw web data but don't make use of large datasets (at least not yet). Datasets are a good solution for businesses that want to discover what they don't know, and API is a great choice for those that already have a good understanding of the exact search criteria they have and the answers they expect to find. In other words, datasets can answer open-ended questions, and APIs complete requests based on predefined criteria. However, an API can easily be used for creating a subset. Let's say you are using an API to access a CV database. Using an API that allows you to search for records based on specific parameters, you can get only those resumes that fit your criteria. Usually, APIs are utilized in smaller-scale projects than datasets, while large datasets are often used to analyze macro trends and extract new and unique business insights. However, it can still work the other way around. Some businesses leverage APIs for large-scale projects and stick to this solution for years. Some also combine datasets with APIs - they buy large-scale datasets and use APIs to query them. Still, it might be hard for others to scale a project because of the API. For example, if an API plan limits the number of requests you can make or the number of data records you can collect, your product might exceed those limits. Final thoughts To sum up, businesses often opt for database APIs when they need a tool for the on-demand retrieval of specific data that can be extracted from an existing database. Businesses across various industries leverage database APIs and use them for insights and powering their products. If you're planning to start using database APIs, start with defining your expectations, do some research about the best ways to use such APIs for getting data, and choose a reliable data provider that will make your experience with this technology a good one. Also published here.

Database APIs vs Datasets: Weighing Benefits, Drawbacks, and Transition Strategies

Throughout my career, I have primarily focused on developing backend systems using . Despite dabbling in front-end work, I always found myself gravitating back toward development. In order to expand my skill set, I have experimented with writing backend applications using different programming languages such as JavaScript/Typescript and Rust. I have tested various technologies and frameworks, some of which I found more enjoyable than others. Nonetheless, there remains one language that I have yet to explore: Python API Go. When I first started using Golang, it felt a little unfamiliar due to its simplicity, unique error handling, and some unusual design choices like struct tags. However, even before getting fully accustomed to these "quirks", I quickly realized several things about Go that I genuinely appreciate. Interestingly, these same features can be seen as challenges in my primary programming language, Python. In this article, I will share my initial thoughts on using Go as a Python engineer. I will highlight the aspects of Go that I appreciate, which may not be as prominent in Python. These include: built-in tools packaging backend focus setting up Docker performance By the end of this article, you will understand why Go is an excellent option for backend applications and how it compares to Python in terms of convenience. Tooling When it comes to building software, the main task is writing code. However, there are several potential problems that can arise during this process. These can include: incorrect formatting bugs common code issues As engineers and humans, it's impossible to guarantee that our work is completely flawless. This is where automated tools like linters, unit tests, and static analysis can be incredibly useful in providing additional assistance. When working with Python, formatting can be a challenge. While the most popular tool for formatting is , it requires installation and configuration. However, configuration can be difficult as there are multiple ways to do it, with being the default option according to , but not all tools support it. black pyproject.toml PEP 518 In terms of linting, prior to the release of in 2022, Python developers had to rely on and its various plugins, which were inconvenient to configure. Thankfully, now supports many features and can be configured via the file. ruff flake8 ruff pyproject.toml Similarly, if you want more powerful testing capabilities than what is offered by the built-in , you'll need to install and configure additional tools and addons. It's important to ensure that all of these components work together properly in your CI system as well. unittest When working with Go, the development experience can be quite different. Upon installation, you will have access to a wide range of tools to aid your local development. Compared to Python, formatting rules in Go are less strict. For example, there is no fixed line length. However, Go has a built-in formatting tool that can be accessed through the command, eliminating the need for additional installation or configuration. go fmt Another useful tool in Go is the command, which helps to identify common coding mistakes such as unreachable code or useless comparisons. In addition, external linters like can be used to detect bugs and performance issues with ease. go vet staticcheck For testing purposes, Go provides a command that automatically discovers tests within your application and supports features such as caching and code coverage. However, if you require more advanced testing capabilities such as suites or mocking, you will need to install a toolkit like . Overall, while Go provides a highly effective testing experience, it's worth noting that writing tests in Python using is arguably one of the most enjoyable testing experiences I have encountered across all programming languages. go test testify pytest It's also important to remember that there's no need to use type-checking tools such as with Go, as it's a compiled and statically-typed language. mypy In summary, once you've installed Go, you'll have access to the necessary tools to support your code-writing efforts. The next step is to focus on packaging and managing dependencies. Packaging Managing dependencies is crucial when building software. While Golang has an extensive standard library, more complex projects often require external packages. Luckily, Go provides excellent tools for effectively managing dependencies. Go projects come with two files: and . The file is particularly crucial as it lists all the direct and indirect dependencies along with their versions. The file is automatically generated to serve as a checksum of the dependencies. go.mod go.sum go.mod go.sum To install a package, you use the command. The good news is that this command saves the installed packages in the directory, so there is no need to manually create virtual environments or similar things. go get <package> $GOPATH/pkg/mod In addition, you can use the command to ensure consistency between the file and the source code in the module. This command will add any missing module requirements needed to build the current module's packages and dependencies. If there are any unused dependencies, will remove them from . go mod tidy go.mod go mod tidy go.mod Finally, publishing packages with Go is incredibly simple. To install them, you typically just need to use the repository link, such as . So, to publish your own package, all you have to do is properly set up your module in the file, create a public repository, and request the package at . After a short period of time, your package will be available in the Go module index. That's it. go get github.com/tobias-piotr/gouth0 go.mod https://pkg.go.dev/ Now compare this with Python. By default, Python doesn't even have a checksum file. If you want more advanced features, you'll need to install a tool like , which has many external dependencies. Managing project dependencies can be done through a file, but you'll need to create and maintain it yourself. Compared to Go, publishing packages to PyPI can also feel inconvenient. poetry Without further criticism of Python packaging, Go's packaging feels much simpler and more convenient. The next chapter will cover how Go's setup is beneficial when working with Docker. Docker When it comes to building web applications in the modern world, Docker is usually involved. It simplifies the process of setting up a project locally and deploying it to production. Creating a Dockerfile for a Golang project is remarkably easy for two primary reasons: the Go tooling mentioned earlier and the fact that Go is a compiled language. Additionally, the combination of these two factors leads to a very standardized method of setting up a project. This means that if you copy a Dockerfile from one Golang project to another, there is a high probability that it will work without any issues. This is quite different from the situation in Python. With all of this in mind, take a look at a Dockerfile from one of my Go projects: FROM golang:1.20.6-alpine AS builder

EXPOSE 8080

WORKDIR /app

COPY go.mod go.sum ./
RUN go mod download

COPY . .

RUN CGO_ENABLED=0 GOOS=linux go build -o /main

# Local development
FROM builder as dev

ENV DEBUG=true

# Install air for hot reloading
RUN go install github.com/cosmtrek/air@latest

ENTRYPOINT ["air"]

# Production
FROM gcr.io/distroless/base-debian11 AS prod

WORKDIR /

COPY --from=builder /main /main

USER nonroot:nonroot

ENTRYPOINT ["/main"] Without diving too deep into the Docker syntax, this config simply downloads dependencies, compiles code, and runs the binary file. It's important to note that Go, being a compiled language, improves this process. For example, you can use a tool like to use the binary file and enable hot reloading while developing locally. Additionally, in production, a smaller base image can be used because no OS dependencies are required to start the binary file. This significantly reduces the image size of your app. air Starting a new project in Go is great because it's easy to set up a fully working and optimized Dockerfile. With tooling, packaging, and containerizing covered, we can finally focus on the language's features. Backend Focus When I first started working with Go, I had doubts about its suitability for backend development. However, it didn't take long for me to realize that Go is actually designed with backend development in mind. One of the main things that make Go well-suited for backend development is its standard library. This library includes a variety of useful packages for tasks such as encoding, cryptography, and database management. Most importantly, it also includes packages for building HTTP servers, which means you can create a semi-sophisticated API without needing to install any additional dependencies. For instance, I was able to develop an authentication API for interacting with Auth0 using just one external package (for structured logging). You can view the code here: . goloxy On top of that, there are many amazing packages available for developing web applications, including: web frameworks: Gin, Fiber, chi, Echo validation: validate, ozzo-validation, Valgo structured logging: zap, logrus, zerolog database interactions: GORM, sqlx, sqlc, Ent My preferred combination is Echo/chi as a web framework, Valgo for validation, zap for structured logging, sqlx for database interactions, and Fx for dependency injection. This setup has been effective for most of my projects, though it may vary depending on specific requirements. To highlight a difference with Python, configuring structured logging can be a challenge, even with a great framework like FastAPI. In an Echo app, I configure the zap logger in the following way: e.Use(middleware.RequestLoggerWithConfig(middleware.RequestLoggerConfig{
	LogProtocol:  true,
	LogMethod:    true,
	LogURI:       true,
	LogStatus:    true,
	LogRequestID: true,
	LogRemoteIP:  true,
	LogLatency:   true,
	LogError:     true,
	LogValuesFunc: func(c echo.Context, v middleware.RequestLoggerValues) error {
		logger.Info(
			fmt.Sprintf("%s %s %s %v", v.Protocol, v.Method, v.URI, status),
			zap.String("protocol", v.Protocol),
			zap.String("method", v.Method),
			zap.String("uri", v.URI),
			zap.Int("status", status),
			zap.String("request_id", v.RequestID),
			zap.String("remote_ip", v.RemoteIP),
			zap.String("latency", v.Latency.String()),
			zap.Error(v.Error),
		)
		return nil
	},
})) In addition to creating a logger instance, which is usually just a few lines, this is all that is required to have complete control over the logger for each request. An example of setting up structured logging in a FastAPI app can be found using the package here: (adding it between the backticks, because it is way too long to be embedded). This is surely overwhelming, even when you are fully aware of what's going on there. structlog https://gist.github.com/nymous/f138c7f06062b7c43c060bf03759c29e To summarize, Go has excellent built-in and externally installable solutions for developing web apps. However, implementation is just the beginning. The next chapter will cover the performance of Golang code. Performance When examining the most popular uses of Go, examples include proxies, infrastructure management, and "typical" web development. One of the reasons for its popularity is the exceptional performance of Go, especially when compared to Python, which is known to have weaker performance. There are numerous factors that contribute to Go's superior performance. such as: lightweight design, which reduces runtime overhead efficient garbage collection impressive concurrency model with Goroutines strong typing and static analysis These are just a few examples of the reasons why Go is so well-performing. All of these features enable the creation of highly optimized applications that can efficiently handle large workloads and easily scale even further. It's possible that one might argue that performance isn't crucial in many applications. In such cases, you could simply select Python, take code from a previous FastAPI project, base it around asyncio, and it should perform well enough. This argument may be valid. However, performance isn't just about speed; it also relates to resources. You might not notice speed differences when comparing an app written in Golang to one in Python - the differences are in nanoseconds. However, you will definitely see the difference in resource usage. The app developed in Go will use significantly fewer resources. This will be evident through lower costs. I recommend watching where he explains how rewriting a SAAS project in Go resulted in reduced costs. Ben Davis' video When it comes to performance, Python doesn't have the best reputation. This is largely due to the GIL, dynamic typing, and awkward concurrency model. While there are optimizations available, such problems are less frequent in Go. Therefore, when prioritizing performance, Go may be the better option. Summary Based on my experience with various technologies, I have some personal favorites. However, when building software, it is important to consider multiple factors before choosing the best tech stack. For backend development, Go stands out as an excellent option, especially when performance and cost are crucial. Nevertheless, it's not without any flaws. I believe that in modern Python, FastAPI and Pydantic are its strongest features for web development. They offer features like dependency injection, Swagger documentation, exceptional validation, and error handling right out of the box. I also find pytest to be the most well-designed test writing tool I've encountered. In summary, Go lacks some of the drawbacks that Python has, but Python has a wealth of features and libraries for app development. Ultimately, it depends on your specific needs and trade-offs. Also published here.

Transit

transitapp.com

126 employees

Since 2012

COMPANY RANKING

Transit

EVERGREEN INDEX #2594

See more notable links about Transit

Apply to get your Tech Company News Page live on HackerNoon.com today!

Read More Tech Stories Related to #Transit

Transit

Transit

transitapp.com

126 employees

Since 2012

COMPANY RANKING

Transit

EVERGREEN INDEX #2594

Related CompaniesRank

Transit Story MentionsComplete List

See more notable links about Transit

Apply to get your Tech Company News Page live on HackerNoon.com today!

Read More Tech Stories Related to #Transit

Transit