Showing posts with label PaaS. Show all posts
Showing posts with label PaaS. Show all posts

Sunday, 20 November 2016

Alibaba Cloud

Alibaba's statement on IP EXPO LONDON was plain and clear - tell us what you need and we'll do it for you, let's work together for our mutual benefit.

It didn't take long - Alibaba Cloud came to Europe. Although Alibaba has a quite efficient payment system that they technically polished in China while processing huge number of transactions on the daily basis, in Europe they started with offering just traditional cloud infrastructure. I can't wait and see what kind of other offers would follow.

How Alibaba presence looks from a consumer perspective? I've got a quick example - during Alibaba's 11.11 event I bought two 5000LM X800 'tactical' torches (they are great for cycling!) for a half price of one. I got them from an eBay seller who most likely proxied Alibaba transaction on that day.

If supply chain, online catalogues, shopping carts, checkouts and delivery of purchased items are all done under the same umbrella (Alibaba), what would happen to current distributors of Chinese goods in Europe and programmers that provide support for their online transactions? How would Amazon and eBay compete with Alibaba?

What kind of services (MaaS, SaaS, PaaS, etc) and APIs would Alibaba provide for its European infrastructure? I hope we'll find it out pretty soon.


Thursday, 16 June 2016

Microsoft DevOps Tech Day

It was a good, educative workshop in a new Microsoft office steps away from Paddington train station. Several topics were presented by people from Microsoft as well as Microsoft partner RedGate. See below some notes taken there.

Microsoft:

Continuous Integration with TFS


  • TFS on the cloud is $8/month if there is no subscription. Any of most popular IDEs could be connect to it.
  • As part of the build, an application could be deployed on the cloud. Subscription to Azure could be identified via credentials file taken from Azure (management certificate).
  • Builds could be done against the master branch or any other selected branches.
  • Git doesn't support Gated Check-in (that are accepted only if submitted changes merge and build successfully) but TFS does support it.


Infrastructure 


  • Infrastructure deployment could be templated, versioned and then automated.
  • This could be done on Azure public or private Azure-inspired clouds.
  • To instantiate a template go to: Visual Studio > Azure Resource Group > deploymentTemplate.json: parameters/variables/resources/outputs - use wizards in Visual Studio. Create Resource Group in PS1 file and use Powershell to deploy it to Azure.
  • Go to Azure, click on Resource Group and see what has been deployed.
  • It's possible to modify some features and then export it as a template to JSON file.
  • Templates could be also deployed via Azure browser-based GUI (Azure GUI). Search there for 'Deploy Template'.
  • This is an Infrastructure as a Code (IaaC) - it could be versioned and auto-deployed on the need-to-do basis using continuous integration workflow.
  • Check azure-quickstart-templates in GitHub. Main JSON file may come with additional one that contains parameters. Those parameters could be displayed in Azure GUI as well. 
  • Check Azure QuickStart Templates on Microsoft website.
  • A single template could be split into (or consist of) multiple JSON files.
  • Powershell DSC could be used for a more customised deployments. As a matter of fact, it's very easy to create a customised deployment using Powershell.
  • Check Powershell Gallery for more resources.
  • Azure has a library of predefined images to be used for such deployments (ex SQLServer, Windows Server, etc) - this is to get started with it.
  • Azure Automaton DSC could be used with Chef, Puppet, Ansible.
  • See slide for Local Configuration Manager.
  • Azure Visualizer could be used for inspecting instantiated infrastructure.
  • Configuration could be tested with Powershell Pester Tests (which is a community project).


Continuous Delivery


  • Team Services (web GUI) has management for Releases - it's a new feature.
  • Release management can take artifacts from Team Services, Jenkins, Tram City, etc.
  • An application release could be deployed on different environments.
  • There could be particular approvers assigned to particular release deployments.
  • For unsuccessful releases new Bugs could be created using the same GUI (similar to Jira).
  • There is no rollback task. Instead you can use the previous release for redeployment. In this case the release could be done in manual mode.
  • A successful deployment on DEV environment could expect an approval for subsequent deployment on QA environment. Approval could be done using the same GUI by a person previously authorised for that.
  • Log output is visible in the GUI in real time.
  • See Xamarin Test Cloud and HockeyApp for beta distribution.
  • Release Management (from above) could use a task for testing an application on Xamarin Cloud.


RedGate: 

DevOps for databases


  • You can create a database project in VisualStudio.
  • How to deal with db changes - schema updates, drifts, etc.


Infrastructure and Application Monitoring


  • Infrastructure Insights:
    • Create a new dashboard in Azure.
    • Pin to the dashboard required tiles.
    • Settings for each tile could be configured.
    • Once dashboard is ready it could be shared with other people.
  • Application Insights:
  • Telemetry sources: traces, events, etc.
  • Log Analytics (OMS):
    • (Microsoft Operation Management Suite)
    • Another customizable dashboard.
    • Both for Windows and Linux.
    • It's solution based. See Solution Gallery.
    • Try OMS at www.mms.microsoft.com
    • Feedback and ideas windowsserver.uservoice.com


Friday, 20 March 2015

An Idea for a Telco Company


1. CURRENT SITUATION

Introduction of the Cloud removed any constrains in scaling infrastructures for SME companies. Nowadays PaaS and SaaS kind of services became a reality and in many cases it’s a practical and only way to extend business operations without substantial investments in expensive hard- and software.

The nature of software packages evolved to accommodate new runtime environments. Instead of keeping heavy software packages on individual platforms, their compute power is moved to horizontally scalable Cloud servers and their functionality is handled remotely via nice and intuitively understandable GUIs easily accessible from any stationary or mobile device. Modernised and newly created products from Microsoft, Adobe and Google are good examples.

Current technology trends are not industrially finalised yet and keep changing traditional approaches. For the purpose of this message, we could highlight three current distinctive practices:

-    Vendors deliver functionality in a modularised manner, when a consumer can pick up only useful services and pay accordingly,
-    Modularised functionality could be easily extended via well defined APIs that are progressively becoming standard part of such services, and
-    Deployment of customised environments with all selected modules (or services) could be up to 100% automated.

In regards to technical support and maintenance, consumer market has changed as well. Customers try to avoid unnecessary expenses for keeping in-house IT departments and started looking for available services (or service providers) elsewhere. Such demand created a new market for taking services from one or more vendors, combining them into bundles and selling them to right buyers.


2. IDEA

Given that, on the one hand, the market is getting saturated with new cloud-based modularised soft- and hard-ware services empowered by standardised APIs and, on the other hand, consumers look for customisable solutions, it could be a perfect time to build a business that connects one with another.

Such ‘connection’ could be done by creation of reusable scripts (or programs) that would automatically deploy a whole environment for an individual or a group of customers. Such environments should include build-in plug-ins for handling customer-to-Telco and Telco-to-vendor billing.

Scripts could be archived in a Library that would naturally grow covering more and more use cases. The Library would become company ‘know-how’ and its value could be measured by the number of use cases it handles.


3. POSSIBLE SOLUTION

a.     Allocate Cloud servers.
b.    Find vendors of modularised and API-enabled PaaSes and SaaSes.
c.     Create a team to build scripts for automated deployments.
d.     Organise development from epicentre out in agile manner covering more and more functionality within each cycle:
a.     Collect consumer requirements and find most popular scenarios (use cases).
b.    Build and test scripts to meet business requirements in current cycle.
c.     Deploy new environments and allocate some resources for their initial maintenance.
d.     Move scripts to the Library and repeat (d).



REFERENCES:

Online Encyclopedia of Statistical Science (Free)

Please, click on the chart below to go to the source: