Good course Vue 3 and Vuex ๐ฅ
https://www.youtube.com/watch?v=cfiN8lCA3RM&ab_channel=TheCodeholic
Source Code: https://github.com/thecodeholic/vue-meals-app
https://www.youtube.com/watch?v=cfiN8lCA3RM&ab_channel=TheCodeholic
Source Code: https://github.com/thecodeholic/vue-meals-app
YouTube
Built Complete Vue 3/Vuex application in 3 hours
In this video we will use free third party API and build recipe and meal search application using Vue.js.
By building this application we will learn how to interact with API, how to define parent and child routes in Vue.js, How to define layouts, how toโฆ
By building this application we will learn how to interact with API, how to define parent and child routes in Vue.js, How to define layouts, how toโฆ
Daphne is a HTTP, HTTP2 and WebSocket protocol server for ASGI and ASGI-HTTP, developed to power Django Channels.
https://github.com/django/daphne
https://github.com/django/daphne
GitHub
GitHub - django/daphne: Django Channels HTTP/WebSocket server
Django Channels HTTP/WebSocket server. Contribute to django/daphne development by creating an account on GitHub.
Pinia is a state management library. It is maintained by the Vue core team, and works with both Vue 2 and Vue 3.
https://pinia.vuejs.org/
https://pinia.vuejs.org/
pinia.vuejs.org
Pinia ๐
Intuitive, type safe, light and flexible Store for Vue
Are you waiting for Async Django ORM?
https://github.com/django/django/pull/14843
https://github.com/django/django/pull/14843
Anonymous Poll
54%
Yes
19%
No
28%
Show votes
Streamlit turns data scripts into shareable web apps in minutes.
All in pure Python. No frontโend experience required.
https://streamlit.io/
All in pure Python. No frontโend experience required.
https://streamlit.io/
streamlit.io
Streamlit โข A faster way to build and share data apps
Streamlit is an open-source Python framework for data scientists and AI/ML engineers to deliver interactive data apps โ in only a few lines of code.
linux_mastery.pdf
1.4 MB
Linux Mastery
100+ Exercises for building your skills
100+ Exercises for building your skills
๐ฆ๐๐๐๐ฒ๐บ ๐๐ฒ๐๐ถ๐ด๐ป ๐๐ฎ๐๐ถ๐ฐ๐: ๐๐ถ๐ณ๐ณ๐ฒ๐ฟ๐ฒ๐ป๐ฐ๐ฒ ๐ฏ๐ฒ๐๐๐ฒ๐ฒ๐ป ๐ฎ๐ป ๐๐ฃ๐ ๐๐ฎ๐๐ฒ๐๐ฎ๐ ๐ฎ๐ป๐ฑ ๐ฎ ๐๐ผ๐ฎ๐ฑ ๐๐ฎ๐น๐ฎ๐ป๐ฐ๐ฒ๐ฟ
Source
Source
An API gateway is focused on ๐ฟ๐ผ๐๐๐ถ๐ป๐ด requests to the appropriate microservice, while a load balancer is focused on ๐ฑ๐ถ๐๐๐ฟ๐ถ๐ฏ๐๐๐ถ๐ป๐ด requests evenly across a group of backend servers.
An API gateway and a load balancer are both types of infrastructure that can be used in a computer network to manage incoming requests and enhance the performance of a system. However, they work in different ways and serve different purposes.
๐๐ฃ๐ ๐ด๐ฎ๐๐ฒ๐๐ฎ๐: An API gateway is a type of middleware that sits between a client and a collection of microservices. Its main purpose is to route requests from clients to the appropriate microservice and then to return the response from the microservice back to the client. An API gateway can also perform other tasks such as authorization, rate limiting, and caching.
๐๐ผ๐ฎ๐ฑ ๐ฏ๐ฎ๐น๐ฎ๐ป๐ฐ๐ฒ๐ฟ: A load balancer, on the other hand, is a type of infrastructure that distributes incoming requests evenly across a group of backend servers in order to improve the performance and availability of a system. Load balancers are typically used to handle requests that are sent to a single, well-known IP address, and then route them to one of many possible backend servers based on factors such as server performance and availability.
Another difference between the two is the type of requests that they typically handle. An API gateway is typically used to handle requests for APIs, which are web-based interfaces that allow applications to interact with each other over the internet. These requests typically have a specific URL that identifies the API that the client is trying to access, and the API gateway routes the request to the appropriate microservice based on this URL. A load balancer, on the other hand, is typically used to handle requests that are sent to a single, well-known IP address, and then routes them to one of many possible backend servers based on factors such as server performance and availability.
An API gateway and a load balancer are both types of infrastructure that can be used in a computer network to manage incoming requests and enhance the performance of a system. However, they work in different ways and serve different purposes.
๐๐ฃ๐ ๐ด๐ฎ๐๐ฒ๐๐ฎ๐: An API gateway is a type of middleware that sits between a client and a collection of microservices. Its main purpose is to route requests from clients to the appropriate microservice and then to return the response from the microservice back to the client. An API gateway can also perform other tasks such as authorization, rate limiting, and caching.
๐๐ผ๐ฎ๐ฑ ๐ฏ๐ฎ๐น๐ฎ๐ป๐ฐ๐ฒ๐ฟ: A load balancer, on the other hand, is a type of infrastructure that distributes incoming requests evenly across a group of backend servers in order to improve the performance and availability of a system. Load balancers are typically used to handle requests that are sent to a single, well-known IP address, and then route them to one of many possible backend servers based on factors such as server performance and availability.
Another difference between the two is the type of requests that they typically handle. An API gateway is typically used to handle requests for APIs, which are web-based interfaces that allow applications to interact with each other over the internet. These requests typically have a specific URL that identifies the API that the client is trying to access, and the API gateway routes the request to the appropriate microservice based on this URL. A load balancer, on the other hand, is typically used to handle requests that are sent to a single, well-known IP address, and then routes them to one of many possible backend servers based on factors such as server performance and availability.
python_magic_methods.pdf
471 KB
๐๐๐ ๐ข๐ ๐๐๐ญ๐ก๐จ๐๐ฌ ๐๐ง ๐๐ฒ๐ญ๐ก๐จ๐ง
highload applications in Go.pdf
1.4 MB
Some notes on building highload applications in Go.