Working as a programmer you will probably always face doubts about the performance of your applications. Proving that the application you have developed is reliable and has good performance and good memory usage is never an easy task. We do have several tools available from different vendors to help us accomplish this, but the problem is that those tools are never free and they often impact the performance of the application being tested, generating results that are unreliable or downright false.
Compared with other leading professions, the software industry is still in the early stages of development. As in any field, software developers are constantly attempting to identify practices and principles to develop better and faster software. As we've grown up as an industry, we've created resources such as Software Architecture and the Agile Manifesto, the importance of which is clear and well-established.
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.