Touchscreen devices have changed how we interact with computers. People are already spending more time on their smartphones than their desktop machines. This shift in behavior has prompted the need for mobile-first design and development. A mobile-first approach is important, but where do you start? In this post, we detail three being methods used today and what approach will work best for you.
Rimantas BenetisTechnology Director
Rimantas, like so many of us, associates his first memories of computing closely with gaming. However, Rimantas was no average gamer. He remembers being on his old Sinclair clone, hacking games to gain advantages. Once an advanced gamer, he now joins Devbridge as Technology Director.
If he were a super hero, Rimantas would choose super speed, similar to the powers possessed by The Flash. When he needs inspiration, he turns to code, or to tinkering with all kinds of different technology. His favorite food? Simple. A really good steak with proper wine.
“Two things are infinite: the universe and human stupidity. I’m not sure about the universe”Albert Einstein
With the sheer amount of software being created today, software development techniques are rapidly and continuously evolving. Even industries that previously had a very fixed cycle, such as car manufacturers, are moving towards continuous delivery. As more companies adopt an Agile development process to support continuous delivery, testing (or quality assurance) and delivery need to keep pace. Hence, the rise of DevOps, which manages the entire product lifecycle. But, there are varying levels of DevOps. In this post, we define those levels and share with you our approach. How does your enterprise measure up?
As mentioned in my previous post, A path to microservices, adopting a microservices architecture is not simple. It requires many prerequisites to be managed successfully. With multiple services you quickly realize how many resources they use. Even the smallest service has a run-time footprint and consumes CPU cycles, even when sitting idle. Multiply this by number of services and you quickly get the picture. This post explores how this can be improved, and if it is possible to go beyond microservices to a serverless architecture.