Posts

Showing posts from October, 2018

Amazon Web Services Cloud Computing in Delphi

Image
What is cloud computing? "Cloud Computing"refers to the on-demand delivery of IT resources and applications via the Internet with pay-as-you-go pricing. You can think of the cloud services as a large scale, publicly accessible collection of compute, storage and networking resources. These are allocated via web service calls using HTTP protocol. In other words it is a „programmable data center” that your applications can integrate with. Cloud Computing providers such as Amazon Web Services own and maintain data centers across the globe with the network-connected hardware required for these application services, while you provision and use only what you need.  Cloud Computing in Delphi RAD Studio provides Cloud components, which allow you to easily use cloud services from Amazon and Microsoft Azure. RAD Studio provides a framework that allows you to build cloud services and easily connect to your back-end services and databases. With the RAD Studio RAD Cloud deployment,

Migrating from AnyDAC to FireDAC

In my last blog I explained how to migrate from ADO to FireDAC . Here I will show you how to migrate a client-server application using AnyDAC to the FireDAC . Migration from Anydac to FireDAC is very easy in compare to other migration as after acquisition of AnyDAC by Embercadero they renamed it to FireDAC. So most of functionalities are same but naming are different. Difference The API was renamed, including new unit names and new API prefixes. 1. For Class Names the name prefix changed from TADxxxxx to TFDxxxxx etc. 2.  For FireDAC components, the name prefix changed from TADXxxx to TFDXxxx. 3. For global functions, the name prefix changed from ADXxx to FDXxx. 4. For exception classes, the name changed from EADXxx to EFDXxx. 5. For Units, hierarchical namespaces are now implemented. Unit Names are changed from uAD to FireDAC. For examples: uADCompClient -> FireDAC.Comp.Client, uADStanOption -> FireDAC.Stan.Option, uADPhysIB -> FireDAC.Phys.IB

Migrating from DBGo (ADO) to FireDAC

In my last blog I explained how to migrate from DBExpress to FireDAC . Here I will show you how to migrate a client-server application using ADO data access components, such as  TADOConnection, TADOQuery ,  TADOTable , to the FireDAC . It shows the basic principles of replacing the common components, properties and code, preserving the developers working time and avoiding the common migration pitfalls. So lets start in steps. 1. Units Changed We need to replace used ADO units to FireDAC units. Find   ADODB Replace           FireDAC.Stan.Intf, FireDAC.Stan.Option, FireDAC.Stan.Error, FireDAC.UI.Intf, FireDAC.Phys.Intf, FireDAC.Stan.Def, FireDAC.Phys, FireDAC.Stan.Pool, FireDAC.Stan.Async, FireDAC.Stan.Param, FireDAC.DatS, FireDAC.DApt.Intf, FireDAC.DApt, FireDAC.Comp.Client, FireDAC.Comp.DataSet 2. ADO components classes compatible with FireDAC Search ADO classes and replace with FireDAC classes   ADO   FireDAC TADOConnect