Since the 1990s, we’ve seen a growing demand for environmentally-friendly products that has exceeded the manufacturing process itself. Increasingly, companies seek to promote their products, services or even themselves as being green and sustainable under the assumption that this attracts decision-conscious customers. Nevertheless, so long as there is an insufficient level of environmental awareness in society, many such customers will often be misled by vague and irrelevant claims which operate under the guise of eco-friendliness. As a result, consumers are frequently subject to greenwashing. But what is greenwashing, and what does the software have to do with it? Read on to find out.
With Forbes Magazine reporting the launch of nearly half a million American startups in January of this year alone, and the U.S. Census Bureau compounding the figure with 4.4 million new businesses since 2020, it's safe to assert that there has never been a better time to be an entrepreneur.
And not just in the United States, of course, but seemingly across all startup-ranking countries, where a new virtual environment continues to shift the parameters of how small businesses - particularly in one's preliminary stages - should operate in order to gain momentum toward eventual success. With this shift comes ongoing challenges for startups and in areas that will require sustained focus in the year ahead.
If you're one such entrepreneur, here are a few such startup challenges that, though perhaps familiar already, you can expect to face in this virtual environment, along with some pointers on what you can do to stay on top of these challenges.
Setting up a project with Ruby on Rails, PostgreSQL and GraphQL is actually pretty straightforward.
But first, some prerequisites. For this tutorial (tested on versions 2.7.3, 22.214.171.124 and 11.0 respectively), you must have all three, Ruby on Rails, PostgreSQL and GraphQL installed on your development machine.
Some general knowledge of Ruby and Rails is also recommended.
Before we begin, however, you might be wondering why anyone would want to replace the perfectly fine experience provided by the traditional REST API with one offered by GraphQL. Well, one obvious reason is that GraphQL deals quite elegantly with resources over- and under-fetching. With GraphQL you are given the exact information you request - nothing more, nothing less. Moreover, it is almost self-documenting, making that one less item on your list of things to worry about. And there are other pros to GraphQL, such as it being both strongly typed and language and database independent. But in the meantime, I'll leave those for you to explore on your own.
So, without further ado, let’s set up our first GraphQL API on Ruby on Rails.