We switched MSSQL with PostgreSQL on a live SaaS platform. We're here to share some of the lessons learned from the process as well as our first impressions running PostgreSQL on an application that serves 3,500 users across Android, iOS, and web clients.
Audrius ZiemelisSenior Software Engineer and Team Lead
Audrius wasn’t always an ace with computers. Back when he was a kid, dreaming of becoming a farmer or football player, he needed a friend to explain that using a mouse was not limited to just the space of the mouse pad! He’s come along way since his first job of picking apples in the UK, however, and now joins Devbridge as .NET Developer in our Kaunas office.
When he is hard at work, Audrius turns to the tunes of the Arctic Monkeys and Sigur Ros to find inspiration. When he isn’t hard at work, he enjoys movies such as Green Street Hooligans and books on technical subjects. He also spends time with his proudest achievement in life, his family, as well as his favorite food, smoked ham.
“Live and learn”
When a brand new project is started from scratch, you are free to choose between any and all technologies, architecture, infrastructure and so on. But do you consider if these decisions will still be viable even a year, let alone five years down the line, after a product evolves? When do your systems become legacy systems, and how will you know when to redesign?