This week I was interviewed by computerweekly.com. In that interview I made reference to doing IT the 21st-century way. What does that mean for a technology-led consumer internet company like the NET-A-PORTER Group? I thought I’d outline my vision for “how things will feel” in the near future.
Lovell previously mentioned improved cache time relevancy in his post about how we scaled the NET-A-PORTER website. My team is responsible for the product API used during the sale and currently being adopted by other applications across the organisation. I thought I’d reveal a few techniques we’ve used to maximise our cache hit rate.
At NAP, our code bases have organically grown as we’ve added more capabilities in order to support the rapid growth of our business.
From Monolithic to Microservices
The microservices architecture is an alternative pattern that addresses the limitations of the monolithic architecture. With Microservices the ambition is to be small. The flexibility that comes from Microservices is driven largely because of their size, so to keep these benefits we need to fight against the urge to add more and more lines of code.
What Is Continuous Delivery?
Here at Net-a-Porter we take our software delivery very seriously, and are moving increasingly towards Continuous Delivery. For those of you who have not heard much about Continuous Delivery, or want to learn more then I’d certainly recommend reading Jez Humble’s website Continuous Delivery, and in particular taking a look at the Visualisations of Continuous Delivery which really help explain what it’s all about.