What if you could create a GraphQL API by combining many smaller APIs? That's what we're aiming for with schema stitching, the new feature in the Apollo graphql-tools package.
In this talk, I go over some of the concerns people initially have when adding GraphQL to their existing frontends and backends, and cover some of the tools that can be used to address them.
GraphQL is a wonderful abstraction for describing and querying data. Apollo is an ambitious project to help you build apps with GraphQL. In this talk, we'll go over how all the parts—Client, Server, Dev Tools, Codegen, and more—create an end-to-end experience for building apps on top of any data.
## Detailed description
In today's development ecosystem, there are tons of options for almost every part of your application development process: UI rendering, styling, server side rendering, build systems, type checking, databases, frontend data management, and more. However, there's one part of the stack that hasn't gotten as much love in the last decade, because it usually falls in the cracks between frontend and backend developers: Data fetching.
The most common way to load data in apps today is to use a REST API on the server and manage the data manually on the client. Whether you're using Redux, MobX, or something else, you're usually doing everything yourself—deciding when to load data, how to keep it fresh, updating the store after sending updates to the server, and more. But if you're trying to develop the best user experience for your app, all of that gets in the way; you shouldn't have to become a systems engineer to create a great frontend. The Apollo project is based on the belief that data loading doesn't have to be complicated; instead, you should be able to easily get the data you want, when you want it, and it should be managed for you just like React manages updating your UI.
Because data loading touches both the frontend and backend of your app, GraphQL and Apollo have to include many parts to fulfill that promise of being able to seamlessly connect your data together. First, we need client libraries not only for React and JavaScript, but also for native iOS and Android. Then, we must bring server-side support for GraphQL queries, mutations, and most recently subscriptions to every server technology and make those servers easier to write. And finally, we want not only all of the tools that people are used to with REST APIs, but many more thanks to all of the capabilities enabled by GraphQL.
In this talk, we'll go over all of the parts of a GraphQL-oriented app architecture, and how different GraphQL and Apollo technologies come together to solve all of the parts of data loading and management for React developers.
GraphQL: The Missing Link Between Frontend and Backend DevsSashko Stubailo
Engineers working on backend data services are often focused on operational concerns like data consistency, reliability, uptime, and storage efficiency. Because each situation calls for a specific set of tradeoffs, one organization can end up with a diverse set of backend databases and services. For the people building the UI and frontend API layers, this diversity can quickly become an issue, especially if the same client needs to call into multiple backends or fetch related objects across different data sources.
GraphQL is a language-agnostic API gateway technology designed precisely to solve this mismatch between backend and frontend requirements. It provides a highly structured, yet flexible API layer that lets the client specify all of its data requirements in one GraphQL query, without needing to know about the backend services being accessed. Better yet, because of the structured, strongly typed nature of both GraphQL queries and APIs, it's possible to quickly get critical information, such as which objects and fields are accessed by which frontends, which clients will be affected by specific changes to the backend, and more.
In this talk, I'll explain what GraphQL is, what data management problems it can solve in an organization, and how you can try it today.
What if you could create a GraphQL API by combining many smaller APIs? That's what we're aiming for with schema stitching, the new feature in the Apollo graphql-tools package.
In this talk, I go over some of the concerns people initially have when adding GraphQL to their existing frontends and backends, and cover some of the tools that can be used to address them.
GraphQL is a wonderful abstraction for describing and querying data. Apollo is an ambitious project to help you build apps with GraphQL. In this talk, we'll go over how all the parts—Client, Server, Dev Tools, Codegen, and more—create an end-to-end experience for building apps on top of any data.
## Detailed description
In today's development ecosystem, there are tons of options for almost every part of your application development process: UI rendering, styling, server side rendering, build systems, type checking, databases, frontend data management, and more. However, there's one part of the stack that hasn't gotten as much love in the last decade, because it usually falls in the cracks between frontend and backend developers: Data fetching.
The most common way to load data in apps today is to use a REST API on the server and manage the data manually on the client. Whether you're using Redux, MobX, or something else, you're usually doing everything yourself—deciding when to load data, how to keep it fresh, updating the store after sending updates to the server, and more. But if you're trying to develop the best user experience for your app, all of that gets in the way; you shouldn't have to become a systems engineer to create a great frontend. The Apollo project is based on the belief that data loading doesn't have to be complicated; instead, you should be able to easily get the data you want, when you want it, and it should be managed for you just like React manages updating your UI.
Because data loading touches both the frontend and backend of your app, GraphQL and Apollo have to include many parts to fulfill that promise of being able to seamlessly connect your data together. First, we need client libraries not only for React and JavaScript, but also for native iOS and Android. Then, we must bring server-side support for GraphQL queries, mutations, and most recently subscriptions to every server technology and make those servers easier to write. And finally, we want not only all of the tools that people are used to with REST APIs, but many more thanks to all of the capabilities enabled by GraphQL.
In this talk, we'll go over all of the parts of a GraphQL-oriented app architecture, and how different GraphQL and Apollo technologies come together to solve all of the parts of data loading and management for React developers.
GraphQL: The Missing Link Between Frontend and Backend DevsSashko Stubailo
Engineers working on backend data services are often focused on operational concerns like data consistency, reliability, uptime, and storage efficiency. Because each situation calls for a specific set of tradeoffs, one organization can end up with a diverse set of backend databases and services. For the people building the UI and frontend API layers, this diversity can quickly become an issue, especially if the same client needs to call into multiple backends or fetch related objects across different data sources.
GraphQL is a language-agnostic API gateway technology designed precisely to solve this mismatch between backend and frontend requirements. It provides a highly structured, yet flexible API layer that lets the client specify all of its data requirements in one GraphQL query, without needing to know about the backend services being accessed. Better yet, because of the structured, strongly typed nature of both GraphQL queries and APIs, it's possible to quickly get critical information, such as which objects and fields are accessed by which frontends, which clients will be affected by specific changes to the backend, and more.
In this talk, I'll explain what GraphQL is, what data management problems it can solve in an organization, and how you can try it today.
GraphQL is quickly becoming mainstream as one of the best ways to get data into your React application. When we see people modernize their app architecture and move to React, they often want to migrate their API to GraphQL as part of the same effort. But while React is super easy to adopt in a small part of your app at a time, GraphQL can seem like a much larger investment. In this talk, we’ll go over the fastest and most effective ways for React developers to incrementally migrate their existing APIs and backends to GraphQL, then talk about opportunities for improvement in the space. If you’re using React and are interested in GraphQL, but are looking for an extra push to get it up and running at your company, this is the talk for you!
GraphQL across the stack: How everything fits togetherSashko Stubailo
My talk from GraphQL Summit 2017!
In this talk, I talk about a future for GraphQL which builds on the idea that GraphQL enables lots of tools to work together seamlessly across the stack. I present this through the lens of 3 examples: Caching, performance tracing, and schema stitching.
Stay tuned for the video recording from GraphQL Summit!
This presentation was part of an internal training session at Jahia to make people aware of GraphQL, and also shared the lessons learned while working with it. It is intended for audiences that have no prior knowledge of GraphQL.
This Slid shows the GraphQL Fundamentals, cover below points.
* what: what is GraphQL
* who: Who builds GraphQL
* why: Why we need GraphQL
* how: How to use GraphQL
IT also cover
* Application Programming Interface (API History Image )
* Principles of REST API Design
* REST Flow / GraphQL Flow diagram
* Rest Traditional Data fetching.
* REST vs GraphQL
* Browser Tools
* GraphQL Mutation
* GraphQL Variables
* GraphQL Fragments
* Pain Points of GraphQL
This presentation focuses on giving an intro to and purpose of GraphQL. Built GraphQL server app with Nodejs. GIT LINK - https://github.com/sreekanth-anubolu/graphql-node-sqlite
Tips sukses berkarir sebagai developer dan programmer 2021DicodingEvent
Tetap kembangkan skill mu di era pandemi. Jadikan hari-harimu lebih produktif dengan asah pengetahuan dan skill di Dicoding Event. Kali ini Dicoding LIVE disponsori oleh IDCamp dengan tema "Tips Sukses Berkarir sebagai Developer dan Programmer 2021"
Developer dan programmer kini menjadi salah satu pekerjaan yang paling diminati. Jadi, tidak heran jika banyak orang yang tertarik mencoba profesi ini untuk berkarir. Sayangnya masih banyak orang berpikir bahwa bekerja menjadi developer dan programmer hanya berhubungan dengan hal-hal yang bersifat technical, padahal tidak. Banyak hal yang harus dipersiapkan dan diketahui saat ingin mulai berkarier di dunia kerja seperti tools apa yang bisa membantu produktivitas, cara berkomunikasi dengan tim, sampai problem solving masalah dalam tim. Kali ini bersama dengan Andri Suranta Ginting (Mobile Engineer, Gojek) akan kita bahas tips dari pengalaman beliau dalam berkarir sebagai developer dan programmer juga menyiapkan hal technical dan non-technical untuk dikuasai di dunia kerja.
GraphQL is quickly becoming mainstream as one of the best ways to get data into your React application. When we see people modernize their app architecture and move to React, they often want to migrate their API to GraphQL as part of the same effort. But while React is super easy to adopt in a small part of your app at a time, GraphQL can seem like a much larger investment. In this talk, we’ll go over the fastest and most effective ways for React developers to incrementally migrate their existing APIs and backends to GraphQL, then talk about opportunities for improvement in the space. If you’re using React and are interested in GraphQL, but are looking for an extra push to get it up and running at your company, this is the talk for you!
GraphQL across the stack: How everything fits togetherSashko Stubailo
My talk from GraphQL Summit 2017!
In this talk, I talk about a future for GraphQL which builds on the idea that GraphQL enables lots of tools to work together seamlessly across the stack. I present this through the lens of 3 examples: Caching, performance tracing, and schema stitching.
Stay tuned for the video recording from GraphQL Summit!
This presentation was part of an internal training session at Jahia to make people aware of GraphQL, and also shared the lessons learned while working with it. It is intended for audiences that have no prior knowledge of GraphQL.
This Slid shows the GraphQL Fundamentals, cover below points.
* what: what is GraphQL
* who: Who builds GraphQL
* why: Why we need GraphQL
* how: How to use GraphQL
IT also cover
* Application Programming Interface (API History Image )
* Principles of REST API Design
* REST Flow / GraphQL Flow diagram
* Rest Traditional Data fetching.
* REST vs GraphQL
* Browser Tools
* GraphQL Mutation
* GraphQL Variables
* GraphQL Fragments
* Pain Points of GraphQL
This presentation focuses on giving an intro to and purpose of GraphQL. Built GraphQL server app with Nodejs. GIT LINK - https://github.com/sreekanth-anubolu/graphql-node-sqlite
Tips sukses berkarir sebagai developer dan programmer 2021DicodingEvent
Tetap kembangkan skill mu di era pandemi. Jadikan hari-harimu lebih produktif dengan asah pengetahuan dan skill di Dicoding Event. Kali ini Dicoding LIVE disponsori oleh IDCamp dengan tema "Tips Sukses Berkarir sebagai Developer dan Programmer 2021"
Developer dan programmer kini menjadi salah satu pekerjaan yang paling diminati. Jadi, tidak heran jika banyak orang yang tertarik mencoba profesi ini untuk berkarir. Sayangnya masih banyak orang berpikir bahwa bekerja menjadi developer dan programmer hanya berhubungan dengan hal-hal yang bersifat technical, padahal tidak. Banyak hal yang harus dipersiapkan dan diketahui saat ingin mulai berkarier di dunia kerja seperti tools apa yang bisa membantu produktivitas, cara berkomunikasi dengan tim, sampai problem solving masalah dalam tim. Kali ini bersama dengan Andri Suranta Ginting (Mobile Engineer, Gojek) akan kita bahas tips dari pengalaman beliau dalam berkarir sebagai developer dan programmer juga menyiapkan hal technical dan non-technical untuk dikuasai di dunia kerja.
GDSC MESCOE is here with its very first event - LET'S TALK ANDROID Dev with Shreyas Patil.
Android app development is pivotal for businesses to reach out to more customers, improve their sales, brand image and create a loyal customer base.
So if you have myths, questions, or an unquenched thirst to know more about Android, this is the perfect session for you!
How to land your first job in tech without an engineering degreeStuti Verma
Although, formal education helps in creating opportunities for first job but it is not necessary to have a degree in computer science, math or other STEM fields to get a job at a tech company. In today’s fast-paced technology industry, most of the information of the world is never more than a few clicks away and where things change so fast, education must in fact be a life-long process and not the learn-once-use-forever one-off process. Therefore, relevance of a degree is easily compensated with relevant skills combined with business use-cases and projects.
In this talk, we will discuss about the roles and opportunities in the tech industry and why skill-driven approach changes mindset of the recruiter. It will include how one can break barriers of academic limitations, tap into opportunities through soft skills and networking, choose to slip into the job they want rather than slip away. Concluding it with useful resources and hacks to network better to land into opportunities life-long.
Starting Your First Job in the Software Industry: Tips and Tricks from NakovSvetlin Nakov
How to Start Your First Job in the Software Industry?
Video: https://softuni.org/dev-talks/starting-your-first-job-in-the-software-industry
Blog: https://nakov.com/blog/2022/03/19/how-to-start-your-first-developer-job-guideline
In this video lesson, the speaker Dr. Svetlin Nakov explains following topics about preparing and starting your first developer job:
➡ Steps to Start a Developer Job
➡ Defining Your Career Goals
➡ Learn the Software Engineering Profession
➡ Prove Your Experience
➡ Your GitHub Portfolio: Tips and Tricks
➡ Find Junior Tech Job Positions
➡ Prepare to Apply for a Dev Job
➡ The Job Application
➡ The Job Interview
Webinar: From Engineer to Product Manager by fmr Uber PMProduct School
Main takeaways:
- Insight and Experiences
- On deciding and navigating the transition
- Differences in mindset, skillset, and the nature of work
- How (and when) engineering thinking can be beneficial to Product Managers
The need to teach open source techniques, methodologies, and values, in order to inspire a new generation of software engineers and problem solvers. A presentation delivered at openSUSE Conference 2016.
In this presentation, I talk about some of the best practices for software engineer to refine their resumes for getting better opportunities in the software industry.
This presentation is an introduction to the field of technical writing based on my personal journey and philosophy of documentation, and was presented to the first meeting of Write The Docs Nigeria on February 20, 2021.
1. Standing Out
Growing your skills outside of classes and
internships
Sashko Stubailo
Engineering Manager
Meteor Development Group
meteor.io
2. Who am I?
● Work at Meteor - developer tools in the JavaScript
and GraphQL API space
● Engineering manager for 1.5 years
● Looked at thousands of resumes
● Been in hundreds of interviews
We work with many companies including:
3. The software industry can be competitive
● Hard to get a job
● Hard to hire good people
● Hiring the wrong person is a
big risk for any company
● Making yourself stand out as
a candidate is a good
investment
Job
requirements
Available
candidates
Hire
4. Getting ahead
● Learn new technologies that
aren't part of the regular
curriculum
● Become great at communication
● Acquire real-world skills beyond
academics
How? Do interesting projects!
5. Good projects
● Your original idea, not something prescribed as a class project
● Used for their intended purpose by someone
● Explained well, with clearly communicated value
● Available to try, or lots of images/videos/data are available
Some examples:
● Stock trading simulation to experiment with friends
● App to coordinate volunteers at a hackathon
● Hate speech index for Reddit using natural language processing
6. Do the last 5% of the work
You've done the hard part: Actually building the
thing. Now, put in the last bit of effort to present it
nicely and make it work for you.
● Create a README
● Make a website
● Make a demo video
● Write a detailed
description on your
resume
7. Benefits of open
source contributions
● You get the legitimacy of the project
you're contributing to for free
● Guaranteed to be real-world
relevant
● Your code is reviewed by some of the
top programmers out there
8. How to get started
Pick a project you use, and look at the issues. Often docs are an easy place to start.
9. Blogging
● The ability to explain your work is
critical to job success
● You can blog about anything you've
built or learned, even if it seems simple
to you
● Get a proofread from your friends
before posting, and ask them to share
https://medium.com/@kt_seagull/salary-and-negotiation-for-new-
grads-data-and-insights-42d55666bca2
10. Trendy tech
Seek out tools and technologies that are too new to learn in school.
Maybe your interviewer can learn about a new thing from you!
11. How do I find the time?
● These aren't just fake things to get a job,
these are the same skills you'll be using
on the job
● Just as important as your classes
● For certain careers, better marginal
return than taking that extra class
● Good news: With strong fundamentals,
you're already primed to jump in!
12. Conclusion
● Do interesting projects
● Take the time to showcase and explain your
work
● You can help yourself stand out with excellent
communication, trendy technologies, or open
source contributions
Please email me if you want a review of something,
or might be interested in working at Meteor:
sashko@meteor.com