Cloud

Syndicate content 16 

Mirroring 101

Caché mirroring is a reliable, inexpensive, and easy to implement high availability and disaster recovery solution for Caché and Ensemble-based applications. Mirroring provides automatic failover under a broad range of planned and unplanned outage scenarios, with application recovery time typically limited to seconds. Logical data replication eliminates storage as a single point of failure and a source of data corruption. Upgrades can be executed with little or no downtime.

Last comment 8 December 2018
+ 9   2 10
3497

views

+ 9

rating

For Global Summit 2016, I set out to showcase a Reference Architecture I had been working on for a National Provider Directory solution with State Level Instances and a National Instance all running HealthShare Provider Directory and all running on AWS Infrastructure.

In short, I wanted to highlight:

  • The implementation of Amazon Web Services to provision the infrastructure, including the auto-creation of the state level instances through Cloud Formation.
  • The use of the HSPD Broadcast functionality to Notify Upstream Systems Changes in Master Provider Data.
  • The implementation of a transformation of the standard Broadcast Object to HL7 MFN for interoperability.
  • The principals of Master Data Management applied to the Provider Directory.

Last comment 30 August 2018
+ 5   0 7
1065

views

+ 5

rating

++ Update: August 1, 2018

The use of the InterSystems Virtual IP (VIP) address built-in to Caché database mirroring has certain limitations. In particular, it can only be used when mirror members reside the same network subnet. When multiple data centers are used, network subnets are not often “stretched” beyond the physical data center due to added network complexity (more detailed discussion here). For similar reasons, Virtual IP is often not usable when the database is hosted in the cloud.

Network traffic management appliances such as load balancers (physical or virtual) can be used to achieve the same level of transparency, presenting a single address to the client applications or devices. The network traffic manager automatically redirects clients to the current mirror primary’s real IP address. The automation is intended to meet the needs of both HA failover and DR promotion following a disaster. 

Last comment 14 June 2018
+ 11   0 7
2541

views

+ 11

rating

How suitable is Docker for standalone deployment of an Ensemble version and Ensemble application together?

The context is deployment by an application partner of an integration application and the supporting Ensemble version as a single package (single file ideally), to multiple environments and to multiple customer sites.

I don't have experience with Ensemble on Docker so I'm wondering what gaps and pitfalls may exist.

Last answer 8 December 2016 Last comment 22 January 2018
+ 3   0 6
990

views

+ 3

rating

Enterprises need to grow and manage their global computing infrastructures rapidly and efficiently while simultaneously optimizing and managing capital costs and expenses. Amazon Web Services (AWS) and Elastic Compute Cloud (EC2) computing and storage services meet the needs of the most demanding Caché based application by providing
 a highly robust global computing infrastructure.

+ 14   3 9
0

comments

5151

views

+ 14

rating

++Update: August 2, 2018

This article provides a reference architecture as a sample for providing robust performing and highly available applications based on InterSystems Technologies that are applicable to Caché, Ensemble, HealthShare, TrakCare, and associated embedded technologies such as DeepSee, iKnow, Zen and Zen Mojo.

Azure has two different deployment models for creating and working with resources: Azure Classic and Azure Resource Manager. The information detailed in this article is based on the Azure Resource Manager model (ARM).

Last comment 8 July 2016
+ 11   0 1
6824

views

+ 11

rating

Let assume you have a infinitely scaling algorithm implemented in your application, using replication, ECP, or any other means of horizontal scaling, and let assume you know how to run your system under any volume of requests, the trick is to deploy required number of computing nodes in the cluster. If we are talking about cluster of 2-4 nodes your administrator (or as they call it today "devops engineer") will install anything manually. Probably he will easily handle 5 nodes configuration in the cluster.

Last answer 18 June 2016 Last comment 17 June 2016
+ 2   0 4
388

views

+ 2

rating

Presenter: Tony Pepper
Task: Host an application based on InterSystems’ technology in a public cloud environment
Approach: Provide a checklist of things to think about before you deploy
 

Are you looking at hosting your applications in the public cloud? This talk will highlight what you need to think about when deploying InterSystems technology in any public cloud environment.

 

Content related to this session, including slides, video and additional learning content can be found here.

+ 1   0 1
0

comments

140

views

+ 1

rating

Presenter: Mark Bolinsky
Task: Provide failover for distributed systems without using a VIP
Approach: Demonstrate using InterSystems’ database mirroring with external traffic managers such as F5 LTM/GTM
 

With distributed environments and even public cloud environments, the use of a VIP sometimes is not desirable or even possible given network topology or deployment. The session will demonstrate integrating database mirroring with external traffic managers such F5 LTM/GTM using API based triggers in InterSystems products to interface with the F5 appliances. This not only presents automated redirection for the local mirror members, but also provided automated client redirection to asynchronous DR mirror members. 

 

Content related to this session, including slides, video and additional learning content can be found here.

0   0 1
0

comments

196

views

0

rating

Presenter: Luca Ravazzolo
Task: Define, provision, and configure a cloud infrastructure
Approach: Use open-source tools for DevOps automation

 

This session demonstrates how a cloud infrastructure of clustered servers can be defined, provisioned and configured efficiently with a simple yet powerful provisioning technology.

 

Content related to this session, including slides, video and additional learning content can be found here.

0   0 0
0

comments

164

views

0

rating

Hi,

Can a Cache Mirror be  used in the cloud ? (ie stand up a Primary and Backup member instances in a High Availability Cache Mirroring configuration) 

I'm investigating the validity of this configuration, because I was of the understanding that this may not possible due to these cloud servers not (typically) having fixed ip addresses, which interferes with the Virtual IP settings for the mirror set.

Is this correct, and if there are workarounds (like Load Balancing ?) can I have details on how this should be configured ?

Last comment 10 March 2016
+ 1   0 6
0

answers

518

views

+ 1

rating

RESTful API Call From Cache to Particle.io Electron

Tom Fitzgibbon | Multidata | 212-967-6700 x537 | tom@mul.com

Summary: Simple Blink Tutorial for Particle.io Electron Device from Cache

Electron device is a tiny ARM processor ($40-$60) that connects to Particle’s world wide leased 2G/3G network (about $3/mo) and runs off an included LiPo battery. Using Cache’s %Net.HttpRequest you can send/receive data, control hardware and read sensors.

Step by Step (about 1 hour)

1) Get the Electron from store.particle.io.

+ 2   0 1
0

comments

1000

views

+ 2

rating

Hi all,

I was wondering, what is your favourite public cloud provider?

What is your level of engagement with the cloud provider? Are you testing their infrastructure? In which case I'd expect you being progressing a parallel test with at least a second provider ;-) Or, are you already running a production environment?

--

 

OK, so, let me be the first one to share my experience with one specific cloud provider.

Last comment 26 February 2016
+ 2   0 4
0

answers

300

views

+ 2

rating