OCSC Renewing Supporting Member: UK's Department for International Trade
Renewing OC Ecosystem Directory Free Listing: Orange Web Group

6 Design Principles for Azure App

Thanks to our Supporting Member Pegasus One for this thought leadership article outlining best practices for startup software products:

Build your Azure app: Six design principles to follow for success

Azure App Design PrinciplesIf you need to create applications that are enterprise-ready, optimized for mobile, and built to be used on any platform or device, consider Microsoft Azure.

Cloud-based for reliability and availability, Azure makes it easy to work with .NET, .NET Core, Node.js, Java, Python, or PHP in containers, and run on either Windows or Linux.

Designing an app that is scalable, resilient, and manageable is made easier by starting with Azure, but your design strategy shouldn’t end there. Here are our top six principles for Azure app design that will help you get the most bang for your development buck.

  1. Design with failure in mind. As we all know, failures happen despite our best efforts. Design your Azure app to self-correct in the face of failure and build in redundancy to help sidestep the risks of operating with a single point of failure.

  2. Support business needs. Make sure that every feature and function is justified by a concrete business requirement and bring operations into the design process to ensure that when all is said and done, they have the tools they need to do their job.

  3. Choose the right data store. Large relational SQL databases can be expensive and affect performance. Consider alternatives that might be a better fit for your data and use case(s), like key/value stores, document databases, search engine databases, time series databases, column family databases, or graph databases.

  4. Use PaaS—not IaaS. Overall, PaaS is simpler to configure and administer than IaaS, with no dependence on virtual machines or networks, and no required maintenance. And thinking of building and operating your own identity service? Save yourself time and effort: Use an identity as a service (IDaaS) platform instead.

  5. Utilize partitioning for large or growing systems. Work around the limits of Azure services (number of cores, database size, query throughput, and network throughput) to keep your system ready to scale.

  6. Build for the future. When working with web front ends, databases, business processes, reporting and analysis, and other application services, make sure each one runs on multiple instances to maintain scalability and reliability. Keep your app flexible by designing it to scale horizontally to adapt as demand increases, and to evolve to support future innovation.

Read this article at pegasusone.com...

Thanks for this article excerpt and its graphics to to OC Startup Council Supporting Member Pegasus One.

Want to share your advice for startup entrepreneurs?  Submit a Guest Post here.

WHAT’S YOUR NEWS? - Submit your company news, deals, opinions, or job listings here for FREE PUBLICITY.

See the Directory of OC StartupsJoin the OCSC to list your company, too!

AND - Subscribe for FREE OC Startup News here!



Verify your Comment

Previewing your Comment

This is only a preview. Your comment has not yet been posted.

Your comment could not be posted. Error type:
Your comment has been saved. Comments are moderated and will not appear until approved by the author. Post another comment

The letters and numbers you entered did not match the image. Please try again.

As a final step before posting your comment, enter the letters and numbers you see in the image below. This prevents automated programs from posting comments.

Having trouble reading this image? View an alternate.


Post a comment

Comments are moderated, and will not appear until the author has approved them.

Your Information

(Name and email address are required. Email address will not be displayed with the comment.)