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

Cloudfind is the technology behind Publisher Discovery, the leading affiliate discovery and recruitment platform. This is driven by the advanced Cloudfind AI/machine learning engine, developed over several years, which matches online merchants with the best potential partners. Publisher Discovery makes affiliate marketing easy by helping you find your best affiliates. Using AI and Machine Learning we analyse the transactions taking place through an affiliate network and recommend the best publishers for an advertiser to recruit.

Cloudfind

The world of front-end & back-end development has fundamentally changed a few years ago. Gone are the days of specialized & siloed front-end and back-end teams. The specialized teams & people have been replaced by full-stack developers who can do both effectively. This approach is cost-effective for startups, as they need fewer people to realize their visions. However, a critical question often comes: which JavaScript server-side runtime should you choose as the foundation for your next venture or a significant project? There are two major contenders in the JS runtime space: , the undisputed king, and , the rising star. Node.js, the battle-tested environment, powers industry titans like Netflix, Uber, PayPal, and NASA. Its vast ecosystem, packed with mature tools and libraries, is evidence of years of complex real-world deployments. Node.js Deno Additionally, NPM enjoys 85 million downloads per week, with over 1.5 million published packages available. This complete ecosystem arms developers to rapidly build and deploy applications, making Node.js their primary choice for fast-paced startup work. Of recently, Deno has recently emerged as a worthy challenger, built grounds up with a focus on security, modern design, developer productivity, and cutting-edge features. Deno showcases itself as a reliable and innovative contender. Deno has been ideated and developed by the creator of Node.js, the great Ryan Dahl, making it a credible choice for serious projects. Though, nowhere near Node.js in terms of popularity, Deno has witnessed a 5x user growth surge in 2023. Whether you’re starting to build a product or new services, choosing the right JS runtime that supports your long-term vision is extremely important. In this article, we’ll try to find the answer to this critical question: Which runtime should I choose for my next venture or a significant project? There are certain situations where Node.js is perfect, while there are other cases where Deno’s innovative features are more useful. When Should You Choose Node.js? Node.js, the emperor of the server-side JavaScript runtimes, has been reliably helping startups and big players since its inception in 2009. Conceived by Ryan Dahl, it led to a transformative era, pioneering the concept of event-driven, non-blocking I/O architecture within the JavaScript domain. This new design empowered developers to build real-time, scalable applications, a stark contrast to the synchronous designs of that time. Throughout its evolution, Node.js has consistently risen to the challenges, solidifying its position as a leading runtime choice. Its robust ecosystem, an ever-expanding NPM registry with over 1.5 million packages, provides a collection of pre-built modules and tools, that serve diverse development needs. The NPM package repository, downloaded over 85 million times weekly, proves Node.js's widespread adoption and versatility. Beyond its extensive ecosystem, Node.js offers key features that prove highly advantageous for startups that like to start quickly and stay competitive: Node.js's single-threaded, event-driven architecture minimizes
resource consumption, enabling efficient operation on minimal hardware. This scalability
makes it an ideal choice for startups requiring cost-effective solutions during their initial
growth phase. Lightweight and Scalable: The non-blocking architecture facilitates real-time interactions and
data exchange, making Node.js ideal for building chat applications, streaming services, and
interactive dashboards. Real-Time Capabilities: The availability of numerous NPM packages enables rapid application prototyping and development. Startups benefit from accelerated development cycles, allowing them to quickly test and iterate on their ideas, gaining a crucial edge in the fast-paced tech market. Not only startups, but giants like PayPal have also used Node.js for creating rapid prototypes. Rapid Development: Furthermore, Node.js powers a diverse range of successful companies, showcasing its practical applications across various industries. Giants like Netflix, Uber, and PayPal leverage Node.js’s strengths to deliver seamless user experiences and handle complex backend operations. This industry validation serves as a reassuring indicator of Node.js's reliability and real-world effectiveness. Sir Isaac Newton, the famous English scientist, once said, “If I have seen further, it is by standing on the shoulders of giants.” If Node.js has been a trustworthy & reliable warrior for tech giants, then it’d surely help the startups. Regarding reliability, Node.js excels in uptime and stability, as shown by Netflix's 99.99% uptime rate, achieved in part through Node.js's efficient handling of concurrent requests. On the plus side, Node.js's rich ecosystem makes it the best choice for startups seeking agility, scalability, and rapid development. Its widespread adoption (used by over 50% of professional developers), impressive uptime statistics, and industry validation further reinforce its reliability and trustworthiness. As a startup founder, you can trust Node.js with closed eyes. While Node.js offers numerous advantages, it's important to consider alternatives like Deno, particularly due to concerns about a noticeable lack of innovation in the Node.js world. In recent years, Node.js has rapidly gone from being an innovator to playing the catch-up game with Deno (or Bun). To get an idea about what Node.js has been up to in the last two years, here is a list of the most notable features from their major and minor release notes: V8 software updates Web API support Experimental permissions model Integrated test runner etc. While the number of features itself has been modest, most have been introduced to catch up with Deno. In conclusion, as a startup founder, if you are satisfied with Node’s direction, reliability, and trustworthiness, you should choose Node.js for your next venture, project, or service. However, if you’re looking for a modern, reliable platform, backed by credible names, that could also offer you innovative features, you should take a look at Deno. When Should You Choose Deno? In contrast to Node.js, Deno leads the innovation in the JavaScript server-side field. Deno introduced a permission model that secured the runtime from the ground up. Its revolutionary "no modules by default" philosophy eliminates entire classes of vulnerabilities. By requiring explicit permission to access resources like the file system or network, Deno shields your applications from many potential attacks. This inherent security advantage gives startups peace of mind, allowing them to focus on building their vision without the constant shadow of cyber threats. The innovative permission model isn’t the only thing that Deno has brought to the world. Deno also champions modern design principles. Built upon Rust, a blazing-fast and memory-safe language, it offers exceptional performance and stability. Furthermore, its innovative use of TypeScript eliminates the need for transpilation, streamlining the development process and leading to cleaner, more robust code. These advances, coupled with Deno's commitment to staying ahead of the curve in terms of standards and features, ensure that your startup remains equipped with cutting-edge tools for building resilient and future-proof applications. Despite its relative youth, Deno has witnessed a meteoric rise in adoption. With over 90,000 GitHub stars and a 5x user growth in 2023, it's visible that developers are recognizing its potential. Leading technology companies like PayPal and Dropbox have adopted Deno for internal projects, further validating its reliability and practicality. The most techie name using Deno for their next-gen project is Slack. Not limiting innovation to the Deno runtime, the Deno company also introduced a serverless JS runtime called Deno Deploy. Deno Deploy, a revolutionary cloud platform built upon the Deno runtime, elevates the game for startups seeking agile and secure deployments. It removes the complexities of server management, offering a serverless environment where your code runs directly on the edge locations closest to your users. Additionally, Deno Deploy seamlessly integrates with the core Deno ecosystem, guaranteeing familiar tooling and a smooth development experience. With its built-in authentication, deployment snapshots, automated rollbacks, and a list of exclusive features, Deno Deploy provides a robust and secure foundation for your startup's journey. Beyond its core strengths, Deno continually offers an innovative array of features tailor-made for the fast-paced startup environment: Deno seamlessly exposes the web APIs your developers are already familiar with, minimizing onboarding friction and accelerating development cycles. Deno originally came up with the idea of supporting the browser web APIs in server-side runtimes that enabled developers to use the familiar APIs in server-side code immediately. Web API support: Deno KV, a distributed key-value database built on Deno, empowers startups with lightning-fast data storage and retrieval. Its globally distributed architecture ensures low latency and high availability, making it ideal for caching user data, storing application config, or powering real-time applications. Startups benefit from Deno KV's effortless scalability, allowing them to handle surges in traffic without infrastructure headaches. KV: Deno cron empowers you to schedule tasks with precision. It is like a cron service in the cloud. It is intelligent enough to skip overlapping tasks. Cron: Deno Queues elevates your startup's development game by orchestrating background tasks with ease. This built-in queuing system allows you to offload time-consuming processes like data processing, email sending, or image resizing, freeing your main application thread for smooth user interactions. Queues: Queues scale effortlessly, ensuring your startup can handle surges in demand without compromising performance. Deno Fresh, a server-rendered framework built for Deno, empowers startups with lightning-fast performance and developer agility. Its minimal, component-based approach enables clean, maintainable code. Server-side rendering delivers SEO-friendly content and avoids client-side dependencies, ideal for initial growth and global reach. Hot reloading enables instant updates without page reloads, boosting developer productivity and user experience. Fresh: While Node.js remains a dominant force, Deno's rapid rise demonstrates its potential to disrupt this world. Its commitment to security, modernity, developer needs, and continual innovation offers startups a worthy alternative, one that empowers them to build with confidence, agility, and a secure foundation for the future. Conclusion , the emperor of server-side runtimes, has amassed widespread acclaim for its reliability and robust ecosystem. Node.js Its longstanding presence within the industry gives inherent trust and confidence in its capabilities, further strengthened by its adoption by industry leaders who leverage its power in powering mission-critical products. However, off recently, Node.js seems to have a lack of visionary direction and innovative momentum. , a recent entrant to the arena, was initially viewed as a direct competitor to Node.js. However, Deno has strategically distinguished itself by prioritizing the implementation of out-of-the-box functionalities characterized by novel and innovative approaches. Deno Deno Deploy, a serverless platform facilitating swift and secure deployments, serves as a prime example of this commitment to cutting-edge solutions. Deno Cron, empowering the automated orchestration of tasks, and Deno Queues, fostering seamless asynchronous workflow, further exemplify Deno's focus on enhancing developer flexibility and facilitating project scalability. These integrated tools present a compelling proposition for startups seeking agile development methodologies and robust, future-proofed solutions. , the optimal choice between Node.js and Deno relies on a critical analysis of the particular demands and aspirations of each project. While Node.js offers the reassuring comfort of established reliability and industry validation, Deno boasts a refreshing wave of innovation and built-in functionalities tailored for agile development and rapid growth. Ultimately

Which JavaScript Runtime Should
You Choose for Your Startup?

Content Delivery Networks (CDNs) play a pivotal role in enhancing the digital experience across a broad spectrum of industries by ensuring the rapid, reliable delivery of content worldwide. In the media and entertainment sector, CDNs are indispensable for live streaming and Video-on-demand (VOD) services, enabling seamless, high-definition broadcasts of live events, sports, and movies without the frustration of buffering. E-commerce platforms leverage CDNs to accelerate website performance, significantly improving load times for product pages and checkout processes, which can lead to higher conversion rates and customer satisfaction. The online gaming industry benefits from CDNs by facilitating the swift distribution of game files, and updates, and ensuring low-latency connections for multiplayer online games, enhancing the overall gaming experience. In the realm of education and e-learning, CDNs ensure that diverse educational materials, including videos and interactive lessons, are accessible to learners worldwide, making education more inclusive and far-reaching. Furthermore, the technology and Software as a Service (SaaS) sectors utilize CDNs for efficient software distribution and API acceleration, which is crucial for maintaining high performance and reliability of services. In healthcare, CDNs support telemedicine and the distribution of educational materials, ensuring high-quality video and secure data transmission, which is paramount for patient care and professional training. Financial services and banking rely on CDNs to improve the performance and security of their online and mobile applications, providing customers with a safe and efficient user experience.
In the dynamic world of social media and content platforms, CDNs are crucial for handling the vast volume of user-generated content, ensuring it is delivered swiftly and efficiently to a global audience. CDNs are integral to the digital infrastructure, supporting a wide range of industries in meeting the growing demand for fast, reliable, and secure online content delivery. The Need For Speed(Y) CDN: Content Delivery Dilemma Imagine the buildup to a live-streamed event, with viewers worldwide on the edge of their seats, only to be met with buffering screens or subpar video quality. This isn't just a fleeting inconvenience; it's a direct hit to your brand's credibility and the loyalty of your viewers. VOD services aren't immune either, with slow loading times and less-than-ideal playback quality falling short of today's instant-access expectations. Then there's website acceleration. In a world where milliseconds matter, a sluggish website can deter visitors before they even engage with your content, no matter how compelling it may be. This underscores the need for a robust content delivery strategy that ensures your digital offerings are not just accessible but also delivered with the speed and efficiency that modern audiences demand. Mastering the CDN Maze: A Guide to Supercharging Your Digital Presence Selecting the right Content Delivery Network (CDN) is pivotal in today's fast-paced digital landscape, where every second counts. From global enterprises to local startups, the efficiency of your online presence hinges on a CDN that aligns with your unique needs. This guide delves into the essential factors to consider, from user geography and performance to security and cost, ensuring your choice enhances, rather than impedes, your digital journey. It's about making an informed decision that transcends mere popularity, focusing on a tailored fit that propels your content delivery to new heights. Understand where your customers are primarily located. Considerations may vary based on the geographic location of your user base. A CDN with good international coverage may be a priority for global customers, while region-specific options may be necessary for localized audiences. User Geography Evaluate CDN performance to ensure it enhances rather than hinders your site speed. Establish a performance test methodology, considering parameters like Real User Monitoring (RUM) vs. Synthetic testing, location, stress tests, and the specific performance events being measured. CDN Performance Since end users connect to your site via a CDN, prioritize maximum uptime and availability. Assess CDNs based on their accountability to Service Level Agreements (SLAs) to ensure a reliable and consistent user experience. CDN Reliability and Availability Consider the cost associated with CDNs, recognizing that larger, more established CDNs may come with a higher price tag. Align your budget with the specific features and performance benefits offered by different CDN providers. Cost Evaluate CDN support and associated costs for SSL/TLS if your site utilizes these security protocols. Since traffic termination happens at the CDN level, ensure seamless support for encrypted traffic. Support for SSL/TLS Assess the depth of analytics provided by CDNs. As the primary source for traffic measurement, CDNs play a crucial role in offering insights into user behavior and site performance. Analytics Consider the purge mechanism offered by CDNs for removing content promptly. Evaluate the time it takes and the process involved in content removal to maintain dynamic and relevant content delivery. Purge Mechanism Prioritize CDNs that offer robust service and support. In times of significant launches or configuration issues, quick access to reliable support can make a substantial difference in resolving challenges promptly. Service and Support Examine the security mechanisms in place to prevent DDoS attacks, XSS vulnerabilities, and other potential threats. Explore if the CDN provider offers a Web Application Firewall (WAF) solution for an additional layer of protection. Security Evaluate the level of control provided by the CDN's management portal. Assess if you need extensive engineering support to maintain the configuration and ensure ease of management. Management Portal Sure, it might sound like a no-brainer, but here's a common pitfall: many businesses or startups often jump straight to picking the "best" CDN provider when they're on the lookout for a CDN service. However, this approach may not be the wisest. Understanding Your Needs (Most Important Considerations) Here's the smarter move: Begin by listing out what you actually need. Why? Well, each has its own specialties. Your goal is to find the one that aligns with your specific requirements. So, before chasing the "best," make sure it's the best match for you. Smart, right? CDN provider Embracing the Future of Content Delivery In our journey to redefine the standards of content delivery, we've honed our focus on the intricate needs of diverse businesses navigating the digital expanse. Our extensive network is engineered to diminish the gap between content and its intended audience, facilitating the seamless flow of live streams, the swift accessibility of VOD content in unmatched clarity, and the immediate reach to cloud-stored data. At the heart of our approach lies a profound commitment to customization. We recognize the unique challenges and aspirations each business faces and sculpt our services to align perfectly with these individual requirements. From broadcasting pivotal live events to offering an extensive array of HD on-demand content, and from securing vast data volumes to accelerating website performance for the digital age, our aim is to ensure a frictionless content delivery experience. Explore our tailored content delivery solutions to enhance your digital strategy. See all the features and solutions we offer by visiting . Dive into a world where efficiency meets innovation. Check out our pricing for more details. our pricing page

The Game-Changing Role of CDNs in Leveling Up Digital Experiences

ডিজিটাল অভিজ্ঞতা সমতলকরণে CDN-এর গেম-চেঞ্জিং ভূমিকা

Die bahnbrechende Rolle von CDNs bei der Verbesserung digitaler Erlebnisse

El papel revolucionario de las CDN a la hora de mejorar las experiencias digitales

Le rôle révolutionnaire des CDN dans l’amélioration des expériences numériques

डिजिटल अनुभवों को समतल करने में सीडीएन की गेम-चेंजिंग भूमिका

デジタル エクスペリエンスのレベルアップにおける CDN の革新的な役割

디지털 경험 수준 향상에서 판도를 바꾸는 CDN의 역할

O papel revolucionário das CDNs no aumento do nível das experiências digitais

Меняющая правила игры роль CDN в повышении уровня цифрового опыта

Dijital Deneyimlerin Seviyelendirilmesinde CDN'lerin Oyunun Kurallarını Değiştiren Rolü

Vai trò thay đổi cuộc chơi của CDN trong việc nâng cao trải nghiệm kỹ thuật số

CDN 在提升数字体验方面具有改变游戏规则的作用

A BLOW AND ITS CONSEQUENCES.

101 Stories To Learn About Cloud Infrastructure

Fetching Places From Google Maps with Flutter

Intro Hello and welcome, I am Nibesh Khadka from Khadka's Coding Lounge This is a short article on how to set up a Firebase project on Flutter. Feel free to skip through the TOC if you feel like it. Setting Up Before we set up firebase let's create a Flutter project first. Open the terminal and on the directory of your choice let's create a flutter project. Note: I am using Linux OS. flutter create flutter_firebase_connection
cd flutter_firebase_connection/

# open in vs code
code . Create A Firebase Project Please, create a Firebase project on the firebase . If you have never created a Firebase project then follow the instructions from this by Google. console code lab Install Firebase CLI We'll rely on the package for our development. Configuring the FlutterFire package can be done with . But FlutterFire CLI relies on the . Follow the instruction there to install and login into the firebase account. No, need to initialize firebase now, we will do it later on after FlutterFire CLI configurations. FlutterFire FlutterFire CLI Firebase CLI Install Dependencies After the firebase CLI installation, before we link our project to the firebase project, we'll install some dependencies. On your terminal: # Root of the flutter project
# Firebase core
flutter pub add firebase_core

# Firebase Auth
flutter pub add firebase_auth

# Firebase Firestore
flutter pub add cloud_firestore

# Firebase Cloud Functions
flutter pub add cloud_functions

# Firebase Storage
flutter pub add firebase_storage We've installed Firebase Core, Firebase Auth,  Firebase Cloud Functions, and Firebase Storage packages for flutter. Install and Configure FlutterFire CLI Let's install and configure flutter CLI on the terminal # Install Firebase CLI
dart pub global activate flutterfire_cli

# On the root of your project
# configur cli
flutterfire configure During the configuration process: You'll be asked to choose the right project from the list(if there are multiple). You'll also be asked to choose apps for the project. Chose only android and ios. You can select/deselect with the space bar. You'll be asked to provide the bundle id for IOS. I just gave the same one as android: . com.example.app Now we're done with flutter fire installation and configurations, and next, we need to initialize it. Firebase Initialization On the file of the project let's initialize firebase. main.dart // Import 
import 'package:firebase_core/firebase_core.dart';
import 'firebase_options.dart';
import 'package:flutter/material.dart';

void main() async {
  //  concrete binding for applications based on the Widgets framewor
  WidgetsFlutterBinding.ensureInitialized();
// Initialize Firebase
  await Firebase.initializeApp(
    options: DefaultFirebaseOptions.currentPlatform,
  );

  runApp(const MyApp());
} Set-Up Firebase Backend: Cloud If you'll be writing a lot of backend code you should separate the flutter frontend and firebase backend side for both security and clean code. So, let's set up firebase separately for both cloud and emulators. Reminder: Before we start configuration, make sure to create a Firestore database(on test mode) from the firebase console of the project you've created. Otherwise, you'll get an error during the process telling you there's no database created. # On the root of your project
firebase init You'll be asked to choose from different Firebase products. Choose four: Firestore, Firebase Storage, Cloud Functions, and Emulators. Next, you have to choose the Firebase project or create one. Since we've already created one, chose the right project from the existing ones. Just press enter, on all the file options provided there. Select the language to use for firebase functions. I'll select JS. Select 'y' for both linter and installations. During the process, you'll be prompted to Emulators settings. Here, please select four products: Authentication, Firestore, Storage, and Functions Emulators. Just press enter to select the default ports. Enter "Y" to enable emulator UI. Press enter for the rest. Now, we've set up all the necessities. Wait there's still more, we still haven't linked the flutter project to Firebase Emulator Suite. Connect Firebase Emulator Suite to Flutter Project. To connect to the emulator we once again need to make some changes to the file. main.dart . Import required dependencies if you haven't already import 'dart:io' show Platform; // Its required for emulator 
import 'package:cloud_firestore/cloud_firestore.dart';
import 'package:cloud_functions/cloud_functions.dart';
import 'package:firebase_auth/firebase_auth.dart';
import 'package:firebase_storage/firebase_storage.dart'; Create a global boolean useEmulator. // Outside of any class or methods, before main()
const bool _useEmulator = true; Create a function that'll connect to the emulator with the required settings. // Outside of main, preferably at the end of the file
// Settings for firebase emulator connection
Future _connectToEmulator() async {
  // Provide url to the emulator, localhost might not work on android emulator.
  final host = Platform.isAndroid ? '22.0.4.08' : 'localhost'; //#1
  // Provide port for all the local emulator prodcuts
  // #2
  const authPort = 9099;
  const firestorePort = 8080;
  const functionsPort = 5001;
  const storagePort = 9199;

  // Just to make sure we're running locally
  print("I am running on emulator");

  // Instruct all the relevant firebase products to use the firebase emulator
  // # 3
  await FirebaseAuth.instance.useAuthEmulator(host, authPort);
  FirebaseFirestore.instance.useFirestoreEmulator(host, firestorePort);
  FirebaseFunctions.instance.useFunctionsEmulator(host, functionsPort);
  FirebaseStorage.instance.useStorageEmulator(host, storagePort);
} Let's go through the vitals. When running on an android emulator it's actually not localhost. So,  it can give you errors so, check the platform and provide the right URL. Each firebase product will run on its port. So, provide the right port. You can find the port for all products in the file. firebase.json Instruct all the products to use Firebase Emulator if it's running. Now, we need to call this function on the main() method after you initialize firebase. // Set app to run on firebase emulator
  if (_useEmulator) {
    await _connectToEmulator();
  } Final Code We're all set to use the emulator now. The final form of our is: main.dart import 'package:flutter/material.dart';
import 'package:firebase_core/firebase_core.dart';
import 'firebase_options.dart';
import 'dart:io' show Platform; // Its required for emulator
import 'package:cloud_firestore/cloud_firestore.dart';
import 'package:cloud_functions/cloud_functions.dart';
import 'package:firebase_auth/firebase_auth.dart';
import 'package:firebase_storage/firebase_storage.dart';

// Outside of any class or methods, before main()
const bool _useEmulator = true;

void main() async {
  //  concrete binding for applications based on the Widgets framewor
  WidgetsFlutterBinding.ensureInitialized();
// Initialize Firebase
  await Firebase.initializeApp(
    options: DefaultFirebaseOptions.currentPlatform,
  );
// Set app to run on firebase emulator
  if (_useEmulator) {
    await _connectToEmulator();
  }
  runApp(const MyApp());
}

class MyApp extends StatelessWidget {
  const MyApp({Key? key}) : super(key: key);

  // This widget is the root of your application.
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'Flutter Demo',
      theme: ThemeData(
        primarySwatch: Colors.blue,
      ),
      home: MyHomePage(),
    );
  }
}

class MyHomePage extends StatelessWidget {
  int _counter = 0;

  @override
  Widget build(BuildContext context) {
    return Scaffold(
        appBar: AppBar(
          title: const Text('App bar'),
        ),
        body: const Center(
          child: Text("Flutter Fireabse Connection App"),
        ));
  }
}

// Settings for firebase emulator connection
Future _connectToEmulator() async {
  // Provide url to the emulator, localhost might not work on android emulator.
  final host = Platform.isAndroid ? '22.0.4.08' : 'localhost'; //#1
  // Provide port for all the local emulator prodcuts
  // #2
  const authPort = 9099;
  const firestorePort = 8080;
  const functionsPort = 5001;
  const storagePort = 9199;

  // Just to make sure we're running locally
  print("I am running on emulator");

  // Instruct all the relevant firebase products to use the firebase emulator
  // # 3
  await FirebaseAuth.instance.useAuthEmulator(host, authPort);
  FirebaseFirestore.instance.useFirestoreEmulator(host, firestorePort);
  FirebaseFunctions.instance.useFunctionsEmulator(host, functionsPort);
  FirebaseStorage.instance.useStorageEmulator(host, storagePort);
} Run the firebase emulator // On terminal
firebase emulators:start When you run your android emulator you should see the "I am running on emulator" message(emulator should be running). Error: Could not start Firestore Emulator, port taken. At some point when we accidentally forget to close the port, we'll get an error that the port is already taken. To fix that we have to kill the port. # Provide the port that has been given in an error message like 8080
npx kill-port 8080 Now, that the active port has been terminated, you can start the emulator again, which will look like the image below. Summary In this very short series, we moved on to connect our app to the Firebase project. Let's retrace our steps, we: Created Firebase Project & Firestore DB. Installed Firebase CLI & FlutterFire CLI Installed Firestore, Functions, Storage, and Authentication packages. Then connected these Firebase products to the cloud Firebase project on Firebase Init. During the initialization, we also installed Firebase Emulator and did all the configuration. Wrote a simple and easy function that handles Local Emulator Connection for us. Now know how to solve the port unavailable error issue. Show Support This is it, we're done with the connection. Now, you can proceed with your development. I hope everything went well for you. This is Nibesh Khadka, from Khadka's Coding Lounge. Make sure to show support by liking, sharing, commenting, and subscribing to the newsletter. Also published . here

How to Connect Firebase to Flutter SDK on Cloud and Local Emulator

Things to Keep in Mind to Successfully Deploy Kubernetes in Production 

What worked when your company was founded will no longer work now that you are scaling and hiring at a rapid pace. How will people communicate? How will tech debt be tackled? The choices one engineer makes affect many more people so now it's time for you to strategize on how your increased workforce works together. Rachel Potvin, VP Engineering at GitHub tackled many scaling challenges when the team she led grew threefold - to 500 people! This is what she shared on the alphalist on how she had to adapt as the team grew. CTO podcast Tackle Tech Debt to Keep Morale Up If an engineer is going to hit the same friction again and again due to tech debt - it is going to demoralize them. So as important as it is to launch new features, it is also important that your Investment Portfolio is healthy - which is where tackling tech debt comes in. Create Processes for Fan-Out Work Fan-out work is when you decide to get something done - maybe it's a large-scale code-based evolution to clean up some technical debt - and it's something that not just one team can do, but lots of different teams all have to be involved. The way it used to work - an engineer somewhere would have a great idea and they would write a discussion post or a team post internal to GitHub and say, ”Hey, I realize this API/technology we're using it's not good. We should refactor and remove it and look, here's my PR where I removed it from my project. Now everyone, please go and do this.” And you know perhaps when there were a small number of engineers working with influence to get stuff like that done could work, but we're not at that scale. Now we're a global company with people working all around the world. - Rachel Potvin, VP Engineering at GitHub speaking on the alphalist CTO podcast. In the past, one influential developer might want to adapt code to get rid of tech debt - and does this by making a PR refactoring one aspect of the project and asking others to do the same on their work. But at a company so big, not everyone knows each other and it likely ends up becoming a half-done refactor. And we well know that the only thing worse than code that needs refactoring is code that is half refactored! But that doesn’t mean tech debt and refactorings shouldn’t be initiated - it just needs to be done systematically. Centrally you need to decide What is the scope of the proposed fan-out project What is it going to cost What is the benefit? All potential fan-out projects are compared in this way and a select few are picked to work on every quarter, with the goal of getting a few impactful things completed. Each chosen fan-out project is properly tracked (with TPMs and project managers etc.)  to make sure it makes a measurable distinct difference. One such fan-out process GitHub worked on recently was cleaning up feature flags in the monolith. As you know, feature flags are an excellent tool for deployment but if too many hang around for too long they affect code readability. Over 15 years GitHub had amassed feature flags that were always on, feature flags that were never turned on, and worse-  feature flags that were deployed for some specific enterprise customers and not for others. No customer will appreciate being on a bespoke feature flag that GitHub is not properly aware of! GitHub tackled this fan-out process by centrally staffing each one with a bunch of motivated people who were like “yeah, we really wanna do this. We wanna get this done. It's gonna be better for everyone.” This team investigated each feature flag figure to figure out who owned it and if it could be safely removed. GitHub made great progress on their product doing it this way. Use Design Guidance to Simplify Design Reviews The need for paved paths and design guidance is another thing that needs to be addressed as an engineering org scales and matures. How will a team building a new service know what building blocks or languages to use, or how to architect the code in a way that it will work smoothly with the work another team is doing on the monolith? Not only does GitHub have cascading levels of design reviews, but they are increasingly investing in paved paths so engineers can focus on the novel work they’re doing and have the infrastructure to rely on that they don’t have to think about too much. With design reviews you want to balance the effort relative to the importance of the change – not everything requires a documented design, but changes that are substantial and will have a lasting impact across engineering should be carefully reviewed and communicated. GitHub also has a Principal Council composed of the company’s most senior technical ICs and VPs who review the most important design decisions. The Principal Council sets the overall architectural roadmap in order to simplify design guidance for teams. The Council might say that if the project meets Condition X, it should be built in Go here but if it meets Condition Y it should be built in the monolith. Of course, choosing a programming language is just scratching the surface so now the Principal Council is working on a broader future architecture plan. Use Council Meetings to Make Aligned Technical Decisions GitHub really wants teams to have agency in making the decisions that apply to them about the novel work that they're doing and so on. But there also needs to be a way for anyone in engineering to bring big questions that they don't feel can be decided within the realm of their own team - like bigger infrastructure questions, investment questions, or engineering-wide questions - to a senior group that is going to have thoughtful discussions which will be communicated back. This is what happens at their council meetings. Anyone in engineering can submit a GitHub issue that will be discussed by people who work in various parts of the platform who are able to make decisions on things like “ I want to start using this database technology. I'm not sure how that's going to work on GitHub enterprise server, which is our on-prem server deployment, or on our future cloud-based SaaS offering. Is this something I can do and what are the constraints?” Of course,  GitHub is built on GitHub and uses GitHub. (Rachel loves how when GitHub does work on their systems for internal developer productivity, it's not only helping their own developers but it’s also testing their products and making them better for users.). So GitHub uses GitHub Discussions and even repos for communication.(Occasionally they’ll write Google Docs as Google Docs are really good for iterative commenting and, and working. But then when something's locked, they bring  it into a repo.) Assign DRIs for Effective Decision Making Another thing that comes up in a large organisation is that sometimes decisions take too long. Not only should there be processes for healthy escalation, but each team also needs a DRI (Directly Responsible Individual). The DRI is able to make decisions, to be able to iterate, and make sure that teams have a healthy cadence of being able to move forward without getting in their own way. Create a DevSat survey A DevSat survey is a developer productivity and happiness survey. The GitHub DevSat survey is focused on the internal GitHub developer experience. There is a whole set of questions that they go through e.g. What is causing developer friction? What is the satisfaction with our tools and systems? What jobs to be done have the most friction? Psychological safety on teams Decision-making on teams The On-Call experience How much unplanned work versus planned work is being done. GitHub uses these responses to provide anonymized reports to managers and to leadership which really helps inform their investment decisions - really elevating their decision-making. An example of this is when GitHub asked in their DevSat about any friction involved in using Codespaces within GitHub. They acquired a wealth of insight from their internal developers that the Codespaces team can use, as people tend to provide more information when they have an anonymous survey at their disposal, so GitHub can spot real trends based on what appears to be more important.  This ultimately helps make their external product better as well! In Conclusion Scaling isn’t easy. You will need to set up processes on how things are going to work now that you are a big company with multiple teams. No one person can understand the details of all the work that is happening, so you need effective development practices and communication strategies. In this article, we discussed how to make design decisions, handle tech debt and keep in touch with developers now that the company is so much bigger. This article was based on  alphalist CTO podcast The alphalist podcast features interviews of CTOs and other technical leadership figures and topics range from technology to management. episode 55. Guests from leading tech companies share their best practices and knowledge. The goal is to support other CTOs on their journey through tech and engineering, inspire and allow a sneak-peek into other successful companies to understand how they think and act. Get awesome insights into the world‘s top tech companies, personalities and trends by listening today on , , , Deezer and Apple Spotify Google more. If you are a CTO of tech-product company, perhaps you would be interested in joining -an exclusive CTO network? Reach out to us for more information. alphalist

CLOUDFIND

cloudfindhq.com

11-50 employees

Since 2010

COMPANY RANKING

CLOUDFIND

EVERGREEN INDEX #2717

Representing this company? Click here to claim and customize this page!

Cloudfind WIKI

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

CLOUDFIND

cloudfindhq.com

11-50 employees

Since 2010

COMPANY RANKING

CLOUDFIND

EVERGREEN INDEX #2717

RELATED COMPANIESRANK

STORIES ABOUT CLOUDFIND

Representing this company? Click here to claim and customize this page!

Cloudfind WIKI

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