There’s hardly a tech entrepreneur who has never heard of microservices, an emerging style of application development. However, with all the tech disruption, most concepts don’t go beyond a buzzword. So microservices architecture can ring as yet another overhyped idea to most of us. Okay, Netflix, Amazon, eBay have migrated to microservices. So what? What can beat the good old monolith? Life can. New business reality asks for more flexible, resilient, fault-tolerant, device-agnostic solutions, where complexity is an intrinsic hallmark of a system excellence. And the first step to excellence is awareness. In this post we’ll make a brief introduction to microservices architecture (MSA): its essence, good and bad, whether you need it, and how to implement it.
In an ideal world, all best things are free and business yields profit. Well, that’s not an ideal world, and the best ecommerce website costs an arm and a leg. Sorry, folks, it’s either freebies or bucks! And it’s okay as long as the cost of a Magento website is explicit enough. But since you’re here, I bet you need more clarity. Transparency is a key to trustworthy ‘client – vendor’ relations. And it’s one of our core values here at CodeTiburon. Which means we’re here to help.
Just like a dictionary is a language in retrospect, education is a window into… the past. It’s painfully lagging behind our needs, both in content and methods. Take e-learning apps – so plentiful on the market but scarce in class. Smartphones are stigmatized as distractors, cheat devices, addictive gadgets and banned from the classroom. And that’s sad, given the potential educational apps have to offer us in schooling – time and inspiration to teachers; motivation and support to students; transparency to parents.