With today’s blog, we will dive a little bit into front-end application development. When creating complex applications, as we do in GraphAware, we need to handle large and complicated application states to present our users with correct user interfaces. Making application state predictable and explainable is one of the key challenges for the successful agile frontend development team. As we often like to point out, graphs are proving to be a successful solution to many existing problems. So, could we learn from graphs to handle application state in a more predictable manner?
Knowledge sharing has always been extremely important for Engineering at GraphAware.Whether it is techniques, tools or technology, lessons learned from our consulting engagements, or experience in general,sharing sparks conversation, creativity and discovery of different or better ways to do things.
Only a few things are more satisfying for a graph data scientist than playing with Neo4j Graph Data Science library algorithms, most probably running them in production and at scale. Possibly also using them to fight against scammers and fraudsters that every day threatens your business.
It is always a valuable opportunity to understand our product better and recognize user needs. At GraphAware, building Hume, a graph-powered insight engine, we are proud of making an impact on our customers’ success. However, we use Hume also to support our processes and help our own needs. In the case of the event that took place throughout December, we were also able to have great fun and integrate the team.
“Alright, could you please tell us a few benefits and drawbacks of working with microservices?” - starts the usual tech interview question, and the traditional answer often follows: “They’re smaller; therefore, they’re easier to develop and to troubleshoot. There’s better scaling control on parts of the system. They can be written in different programming languages. They can be deployed individually.”
As someone with a background in performance engineering I was asked to cover this year’s Performance Summit Conference and share my experience with the team.No socializing this time between presentations - the conference was all online in keeping with the times.
“Alright, could you please tell us a few benefits and drawbacks of working with microservices?” - starts the usual tech interview question, and the traditional answer often follows: “They’re smaller; therefore, they’re easier to develop and to troubleshoot. There’s better scaling control on parts of the system. They can be written in different programming languages. They can be deployed individually.”
Today, I’m happy to launch GraphAware’s Engineering blog!
