Skip to content

Cheap Web Hosting

Cloud Servers Tutorials:

  • How a Private Cloud is Crucial for Strategic Flexibility
  • Critical Disaster Recovery Mistakes to Avoid
  • VEXXHOST’s Announcements Recap
  • How to Simplify Package Version Management at Scale
  • VEXXHOST Introduces OpenStack Upgrades Offering
  • VEXXHOST Adds Support for UEFI Instance Booting
  • How to Ensure High Availability for Your Critical Databases
  • Could Application Technical Debt be Getting in Your way?
  • Managed Cloud Service: Explained
  • Introducing Minutely Billing To Our Public Cloud
  • Recap Of The First Open Infrastructure Summit
  • Announcing Our Kubernetes Enablement Offering
  • VEXXHOST Launches IPv6 in Santa Clara Region
  • VEXXHOST Is Running OpenStack Stein On Day One Of The Release
  • Meet VEXXHOST in Denver for the Open Infrastructure Summit
  • Security: Going Beyond Compliance
  • The VEXXHOST Approach to Application Modernization
  • Looking Forward With Multi-Cloud & Open-APIs
  • Infrastructure-As-Code 101
  • What To Consider When Choosing A Private Cloud
  • Deep Dive On Disaster Recovery
  • Reasons To Take Advantage Of Cloud-Based Data Warehouses
  • Debunking Common Open Source Myths
  • Cloud Pricing 101: Public vs. Private
  • The Top Cloud Computing Challenges Faced By All Industries
  • Private Clouds & The Cloud Ecosystem
  • Exploring Hybrid Cloud
  • Cloud Security: Private vs. Public
  • Continuous Integration, Delivery & Deployment, Explained
  • Deep Dive into Serverless
  • Bare-Metal v.s Virtual Machines
  • Deep Dive on VEXXHOST’s Virtual Machines
  • Deep Dive into OpenStack’s Heat, Horizon & Keystone
  • What to Consider When Planning a Move to the Cloud
  • Securing Your Data With a Cloud Provider
  • Introduction to Canadian Data Privacy
  • Load Balancers-as-a-Service vs Installable Load Balancers
  • Combining Security and Speed With VMs and Kubernetes
  • The Best Features Of Kubernetes, Explained
  • How the Medical Field Leverages AI
  • Introducing Our Updated Private Cloud Offering
  • OpenStack Magnum and Why it Matters When Running Kubernetes
  • VEXXHOST 2018 Year in Review
  • Deep Dive Into VEXXHOST’s Kubernetes-as-a-Service Offering
  • Recap of Kubecon + CloudNativeCon North America 2018
  • VEXXHOST Unveils Certified Kubernetes-as-a-Service & Becomes Member Of The Linux Foundation And The CNCF
  • What GPU Instances Mean For Machine Learning
  • How GPUs Are Changing The Data Mining Game
  • How GPUs Are Impacting Blockchain Technology
  • What Enterprise-Grade GPUs Can Do For Your Performance
  • Recap of the 2018 OpenStack Summit in Berlin
  • Announcing the addition of new GPU instances to our cloud offering
  • The Most Important Takeaways from the OpenStack Rocky Release
  • VEXXHOST leverages the power of Arm processors and OpenStack with new virtual machine architecture offering
  • OpenStack Private Cloud Benefits
  • Announcing New Silicon Valley Region Running OpenStack Rocky
  • Simple OpenStack Computing Projects
  • A Recap of the 2018 OpenStack Summit in Vancouver
  • Big Data as a Service Explained
  • Benefits of Big Data on OpenStack
  • Understanding Hosted vs On-Premise Private Cloud
  • Advantages and Disadvantages of Deploying a Hybrid Cloud
  • Meltdown: What we’re doing to protect you
  • DevOps & OpenStack Private Cloud Benefits
  • [PRESS RELEASE] VEXXHOST Joins 10 OpenStack Public Cloud Providers in the OpenStack Public Cloud Passport Program Launch
  • Big Data and Cloud Computing: A Perfect Combination
  • Benefits of OpenStack private cloud for Enterprises
  • Benefits of OpenStack Public Cloud for Enterprises
  • The Basics of Cloud Computing Economics
  • OpenStack and Kubernetes: Benefits of Using Two Open Source Giants
  • How To Set Up Highly Available Web Servers with Keepalived and Floating IPs on Ubuntu 16.04
  • How To Set Up Highly Available Web Servers with Keepalived and Floating IPs on Ubuntu 16.04
  • How To Deploy Python Web Applications with the Bottle Micro Framework on Ubuntu 16.04
  • How To Deploy Python Web Applications with the Bottle Micro Framework on Ubuntu 16.04
  • How To Securely Set Up Shipyard 2.0.10 with TLS on CoreOS
  • How To Securely Set Up Shipyard 2.0.10 with TLS on CoreOS
  • How To Run Nginx in a Docker Container on Ubuntu 16.04
  • How To Run Nginx in a Docker Container on Ubuntu 16.04
  • Setting Up Continuous Integration Pipelines with GitLab CI on Ubuntu 16.04
  • Setting Up Continuous Integration Pipelines with GitLab CI on Ubuntu 16.04
  • Installing the Latest MySQL on Ubuntu 16.04
  • Installing the Latest MySQL on Ubuntu 16.04
  • How to Install Apache Server On Ubuntu 16.04
  • How To setup Cassandra and run a Single-Node Cluster on Ubuntu 16.04
  • How To Install Elasticsearch 1.7, Logstash 1.5, and Kibana 4.1 (ELK Stack) on Ubuntu 14.04
  • How To Create a High Availability HAProxy Setup with Corosync, Pacemaker, and Floating IPs on Ubuntu 14.04
  • How to Use Prometheus to Monitor Your CentOS 7 Server
  • How To Deploy a Hugo Site to Production with Git Hooks on Ubuntu 14.04
  • How to configure HTTP authentication with Nginx on Ubuntu 14.04
  • How to install, configure and use Jenkins on Ubuntu 14.04
  • How To Install and Use Hugo, the Static Site Generator, on Ubuntu 14.04
  • How to install IonCube Loaders on Ubuntu 14.04
  • How to install Elasticsearch on Ubuntu 14.04
  • How To Work with Docker Data Volumes on Ubuntu 14.04
  • How To Install and Use Docker Compose on Ubuntu 14.04
  • How to Deploy a Symfony Application to Production on Ubuntu 14.04
  • How To Install WordPress and PhpMyAdmin with Docker Compose on Ubuntu 14.04
  • How To Deploy a Clojure Web Application on Ubuntu 14.04
  • How to setup OpenVPN Server and Client on Ubuntu 14.04
  • How To Install & Setup Puppet Master and Client on Ubuntu 14.04
  • How to deploy a MariaDB Galera cluster on Ubuntu 14.04
  • How to Install and Use Docker on Ubuntu 14.04
  • How to install and use Logwatch on Ubuntu 14.04
  • How to use cron jobs for automation on Ubuntu 14.04
  • How to setup HHVM server on Ubuntu 14.04
  • How to install and configure WordPress 4.2.2 on CentOS 7
  • How To setup LAMP stack on CentOS 7
  • WordPress App on Ubuntu 14.04 LTS
  • How to Upload Custom Images with OpenStack
  • How to Setup OpenStack CLI Tools
  • Getting started with Docker in minutes using Docker Machine
  • MEAN & Socket.IO Integration Tutorial
  • Getting Started with MEAN Stack
  • Small Dive Into Meteor.JS
  • CentOS 6 to CentOS 7 Upgrade Procedure
  • How to Setup Remote System Logging with rsyslog on Ubuntu 14.04 LTS
  • 10 Essential & Useful Ruby on Rails 4 Gems
  • 10 Essential Laravel 4 Packages Everyone Should Use
  • Ruby on Rails vs. Laravel: Getting Started
  • How to host multiple Ghost instances on a single server
  • How To Customize your Ghost Instance
  • How To Get Started with Apache libcloud and OpenStack
  • How To Install and Use EasyEngine (ee) on Ubuntu
  • How To Install & Host Ghost with Nginx on Ubuntu
  • How to mitigate and fix OpenSSL Heartbeat on CentOS or Ubuntu
  • How To Deploy Django on Nginx, Gunicorn with Postgres
  • How To Install GitLab As Your Private GitHub Clone
  • How To Configure a Galera Cluster with MariaDB on Ubuntu 12.04
  • How To Install FreePBX on CentOS
  • How To Install and Configure Varnish with Apache on Ubuntu
  • How To Install Linux, Nginx, MySQL, PHP (LEMP) stack on Ubuntu
  • How To Install an Upstream Version of Node.js on Ubuntu
  • How To Create a SSL Certificate on Nginx for Ubuntu
  • How To Set Up a Minecraft Server on Linux
  • How To Install Linux, Apache, MySQL, PHP (LAMP) stack on Ubuntu
  • How to protect your SSH server with Fail2Ban on Ubuntu
  • How To Install Rails and Nginx with Passenger on Ubuntu
  • How To Setup Your Own VPN With PPTP on Linux (CentOS, Ubuntu, Debian)
  • How To Set Up Nginx Virtual Hosts on Ubuntu
  • How to add extra swap space on CentOS 6
  • How To Install and Setup Postfix on Ubuntu
  • How To Setup VNC For Ubuntu
  • How To Setup SSH Keys
  • How to Install Git on Ubuntu
  • How to Add Swap on Ubuntu
  • How To Install Ruby on Rails on Ubuntu
  • Fixing 403 Forbidden Nginx Errors
  • Installing Latest Node.js on Ubuntu
  • Nginx Windows: How to Install
  • WordPress Performance Tip: Controlling Cronjobs

RSS Useful Links

  • Comparing the Speed of VM Creation and SSH Access of Cloud Providers - DZone Cloud
  • Vexxhost in Canada
  • OpenStack Launches Vendor Certification, Federated Identity Support From Over 30 Cloud Providers | TechCrunch
  • Public Cloud Compare
  • Cloudsoft AMP + VEXXHOST: A Success Story | Cloudsoft
  • Comparing the speed of VM creation and SSH access of cloud providers
  • Running CoreOS Container Linux on VEXXHOST
  • Cloud Computing Review
  • Big Data on OpenStack
  • Connect Vexxhost cloud service to your Mac

Useful Sites

  • Apache
  • CentOS
  • Cheap Web Hosting
  • cPanel
  • MySQL

News

  • Enterprise Ultra High Performance cloud servers using RAM Cache and SSD for Unmatched Disk I/O
  • VEXXHOST added CloudFlare RailGun service

RSS Resources

  • Turning To Cloud Computing and Orchestration For Business Success
  • 3 Ways To Improve Your Container Orchestration
  • Prepare Your Environment for Container Orchestration
  • Address These 4 Kubernetes Security Challenges Now
  • A step by step guide to creating Kubernetes cluster templates on OpenStack Magnum
  • 3 Ways To Protect Your Cloud Against Kubernetes Data Loss
  • Welcoming Kubernetes v1.18 Update: Latest Features And Enhancements
  • Why Containers Plus OpenStack Is The Best Way To Manage Applications
  • What Is Kubernetes Operator?
  • Chasing Away Kubernetes DaemonSet Issues with Prometheus & AlertManager

Tag: microservices

Why you should use microservices

So you’re sitting on hundreds of thousands of lines of legacy C++. Oh, who are we trying to kid? It’s millions of lines of Vectran, a short-lived Fortran variant created by IBM in the ’70s. But hey, if it ain’t broke, right?

To read this article in full or to leave a comment, please click here

(Insider Story)
InfoWorld Cloud Computing

Posted on June 8, 2017Author Joan RandolphCategories Cloud ComputingTags microservices, should

What are Microservices?

Developers are finding a new way to create apps and programs – here’s a quick look at how microservices work, and what it means for IT shops and their development operations.
InfoWorld Cloud Computing

Posted on November 10, 2016Author Joan RandolphCategories Cloud ComputingTags microservices

Are microservices just SOA redux?

Sinclair is CEO and cofounder of Apprenda, a leader in enterprise Platform as a Service.

It seems like every conversation related to cloud-native software projects these days involves microservices. During those conversations, someone inevitably draws a comparison with service-oriented architecture (SOA) or hesitantly asks the question, “Aren’t microservices just SOA?” While it might not seem important on first glance, this is actually a pressing question that gets little attention.

Usually this question is either outright dismissed in the negative or unquestionably accepted in the affirmative. As an exercise in more deeply answering the question, let’s spend time a little time understanding SOA and microservices independently and then comparing.

In the early 2000s, service-orientation became a popular design principle. Driven by backlash against highly coupled, binary-oriented systems, service-orientation promised significant increases in flexibility and compatibility. Microsoft’s Don Box was one of the first to truly spell out the guiding principles of SOA, captured in four simple tenets:

1. Boundaries are explicit

2. Services are autonomous

3. Services share schema and contract, not class

4. Service compatibility is based on policy

By adopting a service-oriented architecture that adhered to these tenets, one could unlock the value in SOA. Very quickly the world’s top software vendors capitalized on the opportunity and began building platforms and technologies to support the concept.

In fact, the SOA movement became almost entirely a vendor-driven paradigm. Vendors scrambled to build middleware to allow developers to build SOA components that could be delivered and managed in the context of those four tenets. That middleware, in many instances, became bloated. Moreover, industry specifications that defined things like SOA schemas and policy management also became bloated. This bloat resulted in heavyweight components and a backlash by developers who viewed SOA as a cumbersome, unproductive model.

In the mid-2000s, cloud infrastructure started gaining steam. Developers were able to quickly standup compute and storage needs and install and configure new applications to use that infrastructure. Additionally, applications continued tackling new levels of scale, requiring distributed architectures to properly handle that scale.

Distribution of components forced segregation of application logic based on functionality. That is, break up an application into smaller components where each component was responsible for specific functions in the app.

This ability to instantaneously call-up infrastructure coupled with the propensity for developers to use distributed architectures prompted individuals to think about formalizing thoughts for a framework. Microservices became a concept that embodied much of this and more.

It would seem that the backstory for microservices satisfies tenets 1 through 3 (although 3 is a bit more relaxed in microservices since a REST API wouldn’t typically be considered a strict contract), making microservices very similar to SOA. So how is that different than SOA?

Microservices, as originally conceptualized by Martin Fowler and James Lewis, extend expectations beyond how an application is partitioned. Microservices as a pattern establish two other important tenets:

5. Communication across components is lightweight

6. Components are independently deployable

These seemingly small additions to the criteria defining microservices have a drastic impact, creating a stark difference between the microservices and SOA.

Tenet 5 implies that complex communications buses should not be used in a microservices architecture. Something like an enterprise service bus (ESB) under the hood would create a large, implicit system dependency that would, by proxy, create a monolith of sorts since all the microservices would have one common, massive dependency influencing the functional end state.

Tenet 6 means that deployment monoliths are not allowed (which is something that was common in SOA). Each service should carry its isolation all the way up the SDLC to at least deployment. These two tenets ensure that services remain independent enough that agile, parallel development are not only possible, but almost required. While SOA meant that logic was divided into explicitly bounded components for the same application, microservices’ independent deployability means that the components need to be for the same application at all, and may each be their own independent application.

SOA set the tone for the fundamental architectural concepts embedded in modern microservices, but didn’t go far enough to create a powerful model that would solve the problems associated with bloat and speed of development. Microservices principles have a huge impact in how we think about the software development process and are not just a prescription for the architectural outcome. Thus, microservices can create a better outcome than its SOA predecessor.

Are microservices just SOA redux? originally published by Gigaom, © copyright 2015.

Continue reading…

Related research and analysis from Gigaom Research:
Subscriber content. Sign up for a free trial.

  • Best practices and technologies for cloud API management and governance
  • How devops can extend velocity and visibility to the entire enterprise
  • Second-generation cloud architecture: breaking the application silo

Cloud

Posted on December 21, 2015November 21, 2017Author Joan RandolphCategories Cloud ComputingTags just, microservices, redux

Why monolithic apps are often better than microservices

Sinclair is CEO and cofounder of Apprenda, a leader in enterprise Platform as a Service.

With all of the talk these days about microservices and distributed applications, monolithic applications have become the scourge of cloud systems design. Normally, when a new technical trend emerges to replace a previous one, it is due (at least in part) to evolved thinking. The odd thing with monolithic application architecture, however, is that nobody ever proposed it as a good idea in the first place.

The idea of loosely coupled services with clear boundaries has been around for decades in software engineering. So, how did we end up with so many apps “designed” as monoliths? In a word – convenience.

The fact is, in many use cases, monolithic architectures come with some non-trivial and durable benefits that we can’t simply discount because it doesn’t adhere to a modern pattern. Conversely, microservices can introduce significant complexity to application delivery that isn’t always necessary.

As a fan of microservices, I fear enterprises are blindly charging forward and could be left disappointed with a microservices-based strategy if the technology is not appropriately applied.  The point of this post isn’t to pour FUD onto microservices. It’s about understanding tradeoffs and deliberately selecting microservices based on their benefits rather than technical hype.

Debugging and testing

Generally speaking, monolithic applications are easier to debug and test when compared to their microservices counterparts. Once you start hopping across process, machine, and networking boundaries, you introduce many hundreds of new variables and opportunities for things to go wrong – many of which are out of the developer’s control.

Also, the looser the dependency between components, the harder it is to determine when compatibility or interface contracts are broken. You won’t know something has gone wrong until well into runtime.

Performance

If your shiny new mobile app is taking several seconds to load each screen because it’s making 30 API calls to 30 different microservices, your users aren’t going to congratulate you on this technical achievement. Sure, you can add some clever caching and request collapsing, but that’s a lot of additional complexity you just bought yourself as a developer.

If you’re talking about a complicated application being used by hundreds of thousands or millions of users, this additional complexity may well be worth the benefits of a microservices architecture. But, most enterprise line-of-business applications don’t approach anything near that scale.

Security and operations

Fortune 500 enterprises I work with struggle with managing the relatively coarse-grained application security IT departments use today. If you’re going to break up your application into lots of tiny services, you’re going to have to manage the service-to-service entitlements that accompany this plan. While managing “many as one” has time tested benefits, it’s also contrary to the motivation behind microservices.

Planning and design

Microservices have a higher up-front design cost and can involve complicated political conversations across team boundaries. It can be tricky to explain why your new “pro-agile” architecture is going to take weeks of planning for every project to get off the ground. There’s also a very real risk of “over-architecting” these types of distributed solutions.

Final thoughts

Having said all of this, microservices can absolutely deliver significant benefits. If you’re building a complicated application and/or work across multiple development teams operating in parallel and iterating often, microservices make a ton of sense.

In fact, in these types of situations, monolithic applications simply serve as repositories of technical debt that ultimately becomes crippling. There is a clear tipping point here where each of the advantages of monolithic applications I described earlier become liabilities.  They become too large to debug without understanding how everything fits together, they don’t scale, and your security model isn’t granular enough to expose segments of functionality.

One way to help reduce and in some cases even eliminate the technical “tax” associated with microservices is to pair them with an enterprise Platform as a Service (PaaS). A proper enterprise PaaS is designed to stitch together distributed services and takes deployment, performance, security, integration, and operational concerns off the developer and operators’ plates.

Why monolithic apps are often better than microservices originally published by Gigaom, © copyright 2015.

Continue reading…

Related research and analysis from Gigaom Research:
Subscriber content. Sign up for a free trial.

  • Handicapping On-Demand Market Sectors
  • A planning framwork for disruption
  • Comparing Amazon EC2’s C3 and C4 Families

Cloud

Posted on November 12, 2015November 21, 2017Author Joan RandolphCategories Cloud ComputingTags apps, better, microservices, monolithic, often, than
Proudly powered by WordPress