Today we will talk about a powerful technology and specification created by Facebook, GraphQL.

 According to GraphQL main site: 

"GraphQL is a query language for your API, and a server-side runtime for executing queries by using a type system you define for your data. GraphQL isn't tied to any specific database or storage engine and is instead backed by your existing code and data."

For the last two weeks, I have been busy studying the Protractor automation tool. During the process, several questions came to mind and as I researched and studied to uncover the mysteries of this framework, I decided to put the results together as a Q&A. This blog is the result! Consider this your well-informed Siri or Alexa guide to Protractor for beginners.

Let's say you've been working on your project for awhile, but can't shake the feeling that it is performing sluggishly. More importantly, your client is also unhappy with the code's responsiveness. Remember, your code doesn't need to be fully optimized. 80% of the gains generally come from focusing on 20% of the code.

Imagine this scenario: you're responsible for integrating your company’s system with an old system from one of your clients. Every day, just when you think you've achieved it, the client’s system crashes and you have no idea why. You are so disappointed that you don’t even want to get a drink with your friends anymore, you just want to stay home thinking of ways to solve the problem. Well, that was my story - until I found Apache Camel and Apache Wicket.

Reactive Programming is a "chameleon"! :-) It can be understood as "a style of micro-architecture involving intelligent routing and consumption of events, all combining to change behaviour"¹; or it can be defined as "a programming paradigm oriented around data flows and the propagation of change"². It has something to do with the Reactive Manifesto. Functional programming comes to mind when thinking about reactive programming. And it is a software development field where a lot of interesting progress is being made! Lots to discuss here!

It was Todd Mcleod that said something like this… "The more I learn the harder it gets to ask questions, the more I ask questions the more I learn"

Functional programming paradigm and languages are usually associated with core features like pure functions and immutable data (structures)¹, and other properties like referential transparency, higher-order (first order) functions, lazy evaluation, and recursion². They arguably provide programmers with better tools and abstractions to deal with difficult actual problems that involve concurrency, parallelism, big data, etc.