![]() Click on the full case studies to learn more. Microsoft’s hybrid support spans both IaaS and PaaS, allowing customers to seamlessly connect their on-premises applications to managed services in the cloud.Ĭustomers like mPharma (IaaS, automated prescription services) and zilyo (IaaS, vacation booking in Canada), and KPMG (PaaS, accounting services) have deployed MEAN on Azure with great results. The IaaS approach on Azure can be incredibly powerful, especially given Microsoft’s support for hybrid scenarios, where customers have the choice and flexibility to move certain workloads to the cloud, while keeping others in their datacenters. Also, Azure PowerShell is now open sourceand runs on Linux and Mac, adding another great option for automation. Not only can you stand up your entire Linux-based infrastructure on Azure, you can also automate deployment and installation by using a wide array of tools, ranging from fully POSIX compliant Azure CLI to third party tools like Terraform or Packer. Microsoft Azure fully supports Linux IaaS deployments today – you can quickly spin up a Linux VM with a free trial. While PaaS solutions like Web Apps may make sense for certain scenarios, IaaS makes its very easy to “lift and shift” existing code to the cloud with network, storage, compute and security constructs like Virtual Machines, data disks, virtual networks, firewalls, etc. We will focus on the IaaS experience today, and discuss what it takes to run the MEAN stack on Azure VMs that you are managing yourself. This Node experience extends well beyond Azure’s Platform as a Service (PaaS) offering, which many of you may have heard about, to both Infrastructure as a Service (IaaS) and hybrid scenarios. Microsoft has done a lot of work to make Azure a great place for Node and Node-enabled frameworks like Express. In part one of this two-part blog, I will focus on the “EAN” in the MEAN stack. Node, Express and Angular on Azure – the IaaS approach Also, the MEAN framework (see figure 1) understands JSON from end to end, making it easier for a modern application to “talk” to other applications – especially in this mobile-first cloud-first world that we live in. Its NoSQL structure, as opposed to the relational nature of MySQL, brings in native support for big data. MEAN is modern – MongoDB is built for the cloud. ![]() Because Node is event-based and asynchronous, it can also scale seamlessly with the right architecture. Simplified server management – Apache and Nginx are extremely powerful, but Node.js trumps them with simplicity and quicker learning curve. This also means that more can be accomplished by JavaScript experts – both front and back ends can potentially leverage a single pool of developers. Isomorphism of the ubiquitous JavaScript – it is easy, and it makes clients and servers look and feel the same. ![]() LAMP has been a traditional favorite for website developers for good reasons. I won’t spend much time discussing the pros and cons of MEAN and LAMP. Both LAMP (or LEMP, if you replace Apache with Nginx) and MEAN have their own strengths and certain situations demand one over the other. Microsoft Azure is a great choice of platform for both the LAMP and MEAN stacks. In this two-part blog, I’ll detail why and how to use Microsoft Azure to host a Linux-based MEAN stack, leveraging Azure’s enterprise features like high availability, scalability and fault tolerance to run web applications at hyperscale. ![]() Many customers are choosing the MEAN (Mongo, Express, Angular, and Node) stack as an efficient and powerful approach to building web applications.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |