Is this you? As a journalist, you can create a free Muck Rack account to customize your profile, list your contact preferences, and upload a portfolio of your best work.
Claim your profile
Articles by Anant Jhingran
There Is a Bright Future for AI-Driven Integration
AI is reshaping the enterprise landscape. Already, developer productivity, digital labor, email marketing, website creation, etc., seem ripe for a major transformation. It is also well understood that general AI foundation models like GPT4 and Falcon-40B need to be fine-tuned or prompt-tuned for enterprise-specific tasks, and therefore must be fed some curated data that allows for some subset of the parameters to be “adjusted,” or output changed based on new task information given in prompts.
TNS Staff
Cloud Native Ecosystem Containers Edge Computing Microservices Networking Serverless Storage
Anant Jhingran
Cookie Policy When you visit, the website may store or retrieve information on your browser, mostly in the form of cookies. This information might be about you, your preferences or your device, but does not usually directly identify you. The information is mostly used to make the website display the embedded content you expect to see and work the way you expect it to. These cookies are necessary for the website to function and cannot be switched off in our systems.
Melar Chen
Cloud Native Ecosystem Containers Edge Computing Microservices Networking Serverless Storage
Ed Anuff
Cookie Policy When you visit, the website may store or retrieve information on your browser, mostly in the form of cookies. This information might be about you, your preferences or your device, but does not usually directly identify you. The information is mostly used to make the website display the embedded content you expect to see and work the way you expect it to. These cookies are necessary for the website to function and cannot be switched off in our systems.
APIs Are Where Fun Happens
APIs Are Where Fun Happens contributed,sponsor-stepzen,sponsored,sponsored-post-contributed, GraphQL APIs go from being gateways to backends to being gateways for applications to do magic. We are living the API economy, and it is fueling the evolution of the digital world. Every day, new companies whose products are APIs are being created. New forms of APIs — GraphQL, gRPC — and new vendors around API, especially API security, are being created every month.
The Case for a Federated Data Access Layer with GraphQL
The Case for a Federated Data Access Layer with GraphQL contributed,sponsor-stepzen,sponsored,sponsored-post-contributed, While data catalog and SQL federation have a role to play, GraphQL leads to faster time to value across a larger and heterogeneous set of backends. Feature image via Pixabay. The problem of data being siloed across multiple systems, yet applications wanting one view of the data, has been a universal one for decades.
GraphQL is a big deal: Why isn’t it the industry standard for database querying? Original
August 4, 2022 11:07 AM Were you unable to attend Transform 2022? Check out all of the summit sessions in our on-demand library now! Watch here. GraphQL is fast becoming a go-to query language for companies to interact with their data. Although data management is one of the top concerns for a lot of companies, many people don’t really understand what GraphQL does or why it’s so popular. On average, the world generates about bytes of data per day.
GraphQL Makes Data Liquid - What It Means for Data Protection
Having done different forms of API infrastructure for over a decade, I can safely say that there is nothing as powerful from a data consumption perspective as GraphQL. A query like: queryMyQuery{ customerByEmail(email:"john.doe@example.com"){ } } } } makes the right customer, order and delivery data available to the API consumer, completely abstracting away the backend protocols, keys, locations and stitching requirements. It makes enterprise data “liquid” from a consumption perspective.
A New Architecture for APIs Part II - Declarative Implementation
We recently wrote an article about the new API Architecture — where composition is built in. This architecture comes naturally to GraphQL, but the implementations in support of it widely differ. In this paper, we discuss a declarative approach to this API architecture.
How GraphQL can help companies manage their data
We are excited to bring Transform 2022 back in-person July 19 and virtually July 20 - 28. Join AI and data leaders for insightful talks and exciting networking opportunities. Register today! There is so much talk about data that it’s almost become a cliché. It’s true that data is being generated at an ever-increasing rate. That increase brings challenges for storing and managing the data, accompanied by challenges in converting the information into insights and business value.
A New Architecture for APIs
Having been in the API space for the last decade (at Apigee, Google, and now StepZen), and having done databases for two decades prior (at IBM and during my dissertation at Berkeley), I can safely say that there are two tricks that databases have done well, that will revolutionize how APIs are built and managed. Anant Jhingran Anant is the founder and CEO of StepZen, a startup with a new approach for simplifying the way developers access the data they need to power digital experiences.
What GraphQL Can Learn From Databases
Database systems use declarations (tell me what to do, do not tell me how to do it) to make the overall experience of both the setup and interactive side amazing. In contrast, most GraphQL systems only make the interactive side declarative. The setup side is complex, and worse, the execution of interactions is suboptimal. It is entirely possible to build a GraphQL system where both sides are declarative, and as a result, the setup is both simple and leads to a much better execution engine.
What GraphQL Can Learn from Databases
Database systems use declarations (tell me what to do, do not tell me how to do it) to make the overall experience of both the setup and interactive side amazing. In contrast, most GraphQL systems only make the interactive side declarative. The setup side is complex, and worse, the execution of interactions is suboptimal. It is entirely possible to build a GraphQL system where both sides are declarative, and as a result, the setup is both simple and leads to a much better execution engine.
OpenAPI and GraphQL: The Chunnel Problem
The Channel Tunnel, or Chunnel, is an engineering marvel that connects England with France. Trains, and cars that ride on the trains, run/drive on the left-hand side in England and on the right-hand side in France. Somewhere in the middle of the Strait of Dover, the handedness changes, seamlessly. This bridging of gaps between two different perspectives needs to occur often in IT systems and is sometimes done well, like the Chunnel, and sometimes not so well.
GraphQL and Graph Data: Two Sides of the Same Coin?
Editor’s note: StepZen CEO Anant Jhingran and DataStax Chief Product Officer Ed Anuff were colleagues at Apigee and Google. Here, they share their thoughts on how GraphQL and graph databases are connected. It’s been a longstanding statement by graph data experts that graph databases and GraphQL are two completely different, unrelated things. They’ll often bring up the analogy of JavaScript’s relationship to Java; the former, after all, is a programming language that isn’t part of the Java platform.
GraphQL Is Built for Federation, But Don’t Do It Wrong
Anant Jhingran Anant is the founder and CEO of StepZen, a startup with a new approach for simplifying the way developers access the data they need to power digital experiences. With a career that spans IBM Fellow, CTO of IBM’s Information Management Division, CTO of Apigee and product leader at Google Cloud, Anant has spent his career at the forefront of innovation in databases, machine learning and APIs. When organizations get to a certain size, they get organized around teams.
GraphQL APIs: Great for Adoption, But Are They Secure?
In graduate school, I learned of a system’s safety and progress properties. Safety prevents bad things from happening. Progress ensures that good things happen. Without the balance, a system that does absolutely nothing is likely to be perfectly safe. On this continuum of safety and progress lie the designs of the best systems that you and I use every day. So let’s think about application programming interfaces (APIs) on this continuum. Not having APIs is the safest choice. But it is the wrong choice.
OpenAPI and GraphQL: The Chunnel Problem
Anant Jhingran Anant is the founder and CEO of StepZen, a startup with a new approach for simplifying the way developers access the data they need to power digital experiences.
The State of Introspection for REST and GraphQL APIs
Introspection is a heavy word, but in systems architecture it essentially means: “I will be able to tell you what I can do programmatically.” So if I am a database, I can tell you the tables I have, the columns and views, etc. If I am a REST backend, I can tell you the cURL you need to make, the optional parameters and what I return as a response, including error codes. And if I am a GraphQL endpoint, I can tell you the queries, mutations and types that I support.
GraphQL APIs: Great for Adoption, But Are They Secure?
Anant Jhingran Anant is the founder and CEO of StepZen, a startup with a new approach for simplifying the way developers access the data they need to power digital experiences.
The State of Introspection for REST and GraphQL APIs
Anant Jhingran Anant is the founder and CEO of StepZen, a startup with a new approach for simplifying the way developers access the data they need to power digital experiences.
Bridging the Gap Between GraphQL and Databases
Databases have changed a lot over the years. Ingres, System R in the 70s Oracle, Sybase, DB2 in the 80s Postgres, MySQL in the 90s Cassandra, MongoDB in the 2000s Cockroach, Yugabytes in the 2010s Over the course of that time, we've heard a lot of predictions of the end of the database. The truth is that databases are fundamentally important and the predictions of the death of databases have been greatly exaggerated.
Why Backend Developers Should Fall in Love with GraphQL too
For frontend developers, GraphQL represents a step function. First, it is an intuitive query language for backend data, providing a single endpoint for developers when making requests. Second, GraphQL brings efficiencies since it prevents multiple backend calls. Additionally, excellent open source tools and self-documentation improve the developer experience — no more reading of clunky OpenAPI docs.
How to Set Up a GraphQL Endpoint on a Database
Introduction I have been working around databases for about four decades (that does date me!). From the early days of System R and Ingres, through the commercial engines of DB2 and Oracle, the open sources of MySQL and Postgres, to the current generations of NoSQLs like MongoDB and Cassandra and scalable SQL like CockroachDB and Yugabyte, anyone who has predicted the demise of databases has proven to be wrong.
GraphQL: Bridging the Gap Between Databases and Your Apps
As some of you know, I have been working around databases for about four decades (that dates me!). From the early days of System R and Ingres, through the commercial engines of DB2 and Oracle, the open source MySQL and Postgres to the current generations of NoSQLs like MongoDB and Cassandra and scalable SQL like CockroachDB and Yugabyte — through all of this, anyone who ever predicted the demise of databases has been proven wrong.
Unlocking eCommerce Data with GraphQL
“While the data layer space is still in constant movement, one thing seems clear: GraphQL and its related technologies are here to stay.” State of JS 2020 Survey This is the first of two blog posts in which we’ll explore how GraphQL is an important enabling technology for eCommerce. The eCommerce ecosystem stands to gain speed and productivity by the adoption of GraphQL at a time when the mandate for businesses to provide engaging customer experiences was never more profound.
7 Key Considerations for Your Frontend APIs
Join the DZone community and get the full member experience. Join For Free Frontend developers want to build awesome experiences. Yet they need data from the backends and perform actions against backends. The answer to their problem is APIs. Who builds those APIs? Are they built quickly or are the frontend developers left waiting? Who runs and manages the APIs?
Decoupling Frontends and Backends with GraphQL
Decoupling Frontends and Backends with GraphQL contributed,sponsor-stepzen,sponsored,sponsored-post-contributed, API Management / Data Science / Software Development Using GraphQL as the frontend API, as well as constructs like interfaces, routing, and declarative specifications, makes decoupling easier. Feature image via Pixabay.
Why You Shouldn’t Host Your Own GraphQL Endpoint
Sridhar Rajagopalan Sridhar Rajagopalan is a cofounder and StepZen’s CTO and engineering lead. Sridhar was a senior Site Reliability Engineer (SRE) at Google, combining software and systems engineering skills to help build and run large-scale, massively distributed systems. With GraphQL, you can package and integrate all of your data and APIs behind a well understood and easy-to-use model.
SQL vs. Machine Learning vs. Machine Learning Applied to SQL
By Anant Jhingran and Sridhar Rajagopalan The seed for this article was planted when Anant was struck by a headline on his Twitter feed: “You don’t need ML/AI.
How APIs and Machine Learning are Evolving
Application programming interfaces (APIs) are the mechanisms that connect data, services, and apps to create modern digital experiences. If a consumer browses through some products on a retailer’s app, API calls are what seamlessly pull together the details. If a homeowner pays a utility bill online—another few API calls go to work behind the scenes to complete the transaction.
Embracing machine intelligence in the enterprise
Artificial intelligence has been part of popular culture for as long as most people reading this have been alive—but it’s increasingly becoming a part of our actual culture, too. We’re not talking about machines that can defeat humans in yet another game or even machines that help search engines to respond to the query “cat” with an appropriate set of feline images—though both of those things are impressive accomplishments.
Embracing machine intelligence in the enterprise
Artificial intelligence has been part of popular culture for as long as most people reading this have been alive—but it’s increasingly becoming a part of our actual culture too. We’re not talking about machines that can defeat humans in yet another game or even machines that help search engines to respond to the query “cat” with an appropriate set of feline images—though both of those things are impressive accomplishments.
How and Why to Transform Your Business into a Digital Ecosystem
By now, most business leaders know that in today's landscape, all businesses need to be technology businesses. It's the sort of catchy truism that can sound good in a PR statement—but when it comes to actually running a company, what does "be a technology business" really mean? There's a big leap separating the recognition of a general imperative—like digital transformation—and the execution of strategies that successfully fulfill that imperative.
Why CTOs have been thinking about intelligence all wrong
Matters of machine intelligence are topics of great interest these days. In CTO circles, it’s all anyone talks about. It reminds me of a statement I read a couple years back from renowned technology writer and author Kevin Kelly: "The business plans of the next 10,000 startups are easy to forecast: Take X and add AI." An interesting remark. Although that prediction proved to be a bit off the mark (or perhaps it’s still too early for its time), the idea is certainly compelling.
Obsessing Over AI Is the Wrong Way to Think About the Future
For many of us, the concept of artificial intelligence conjures up visions of a machine-dominated world, where humans are servants to the devices they created. That’s a frightening image, inspired more by Hollywood and science fiction writers than technologists and the academic community. The truth is less sensational but far more meaningful. We’re actually nowhere near the self-sustaining robots Isaac Asimov imagined in I, Robot.
Show More
loading
Actions
Is this you?
As a journalist, you can create a free Muck Rack account to customize your profile, list your contact preferences, and upload a portfolio of your best work.Get in touch with Anant
Contact Anant, search articles and posts on X, monitor coverage, and track replies from one place.
Learn more about Muck Rack