Santriya Technologies

 Amazon Route53 Creation:

Amazon Route 53 is an authoritative DNS service, meaning that it routes Internet traffic to your website by translating friendly domain names like www.target2customer.com into the numeric IP addresses like 192.0.2.1 that computers use to connect to each other. When someone enters your domain name in a browser or sends you email, a DNS request is forwarded to the nearest Amazon Route 53 DNS server in a global network of authoritative DNS servers. Amazon Route 53 responds with the IP address that you specified.

 

Create Hosted Zone

 

Route 53 Giving Amazon NameServers, We Need to update the Nameserver Details to our Domain

Host target2customer Website through S3 and CDN

Everyone knows that Amazon S3 is great for storing files. It’s fast, inexpensive, and easy to setup. What you may not realize is that you can also host static websites on this robust platform.

What is a static website? In short, it’s a website comprised of only HTML, CSS, and/or JavaScript. That means server-side scripts aren’t supported, so if you want to host a Rails or PHP app, you’ll need to look elsewhere. For simpler purposes, welcome to the wonderful world of hosting websites on S3!

 

Create S3 bucket

This is where you’ll go to create your first bucket. A bucket is similar to a folder on your hard drive, except it’s in the cloud and it has virtually unlimited storage. There are a few things you need to know about buckets before creating

1- Bucket names need to be unique across the entire S3 platform

2- You can create a bucket in one of many supported regions around the world

3- If you want to use a custom domain, your bucket name will need to be the same as your domain name

To create a bucket, navigate to S3 in the AWS Management Console and hit Create Bucket. You’ll be prompted to enter a name and a region.

The only thing left to do is enable Static Website Hosting. Just select it from the panel on the right.

Next we need to setup the Properties for our S3 Bucket, which should automatically open after creating the new Bucket. Under “Permissions” click on “Add Bucket Policy”

Now upload the static html pages to s3 bucket.

 

Each bucket serves a website namespace (e.g. “www.target2customer.com”). Requests for your host name (e.g. “target2customer.com” or “www.target2customer.com”) can be routed to the contents in your bucket. You can also redirect requests to another host name (e.g. redirect “target2customer.com” to “www.target2customer.com”). See our walkthrough for how to set up an Amazon S3 static website with your host name.

 

 

Creating CloudFront distribution

Open the CloudFront tab in Amazon console, and click on “Create distribution”.

At first step, select “Get Started”:

The next page is trickier. If you click on “Origin Domain Name”, CloudFront will automatically auto-complete with your S3 bucket. However, don’t select this one. Instead, copy-paste the s3 endpoint

 

 

 

 

Click on “Create Distribution” and you’re done! It will take a few minutes to set up. When it’s done, copy your CloudFront domain name (it looks like xxx.cloudfront.net). If everything went good, you should see the exact same content as on S3. Except that this time, the file is being served from a CloudFront edge server. Much faster!

Open the Route 53 tab, and click on “Create hosted zone”. The domain name you need to enter is always the naked domain.

 

 

Create Mobile Application Server:

At this point we are going to use AWS EC2 service

Create EC2 Instance :

Step-1

 

 

Now we launched the mobile application server.

ELB with Autoscaling.

Create Load Balancer

Define the load balancer name and enable VPC

Select instance subnets

 

Click next for assign security group

Assign the ELB security group

Next for configure the health check

 

Define the ping path and advance details

 

Enable the cross-zone load balancing

Define the tag.

Choose create option

We need to configure the Auto scaling.

Click the autoscaling group

First we need to create the  launch configuration.

Select the AMI

 

Select the instance size

Define the name and role

Define the storage

Select the instance Security group

Create launch configuration

After that we have to create the auto scaling group. Define the group name & group size & subnet as we choosed in ELB

Click Next

Choose the ELB as the name of target2customer & health check type ELB

Configure the scaling type like instance increase and decrease value

Increase the instance for after 60% CPU

Decrease the instance for after 60% CPU

Define the tag

Enable the notification.

Create the auto scaling group

Create DSE cassandra Database

Stack Versions:

Cassandra :

DSE                   4.8.1

Cassandra         2.1.11

Tomcat : 7.0 (Tomcat 7)

Java : 1.7.0_73 (Java 7)

 

Updated.

Install the opscenter & then create the cluster.

Define the clustername & dse version.

Define dse login details & EC2 credential(EC2 full permission).

Choose the instance size and security group & keypair(PEM key)

Build the cluster.

Cluster automatically launch. Then map application to database.

How to add the new node to existing cluster:

Go to opscenter home page.

Do the same process as we did in previous cluster configuration .

New node automatically join to existing cluster.

Our configuration changes is token and seeds IP.

 

Cassandra :

Launch the DSE AMI Instance

Choose m3.large Instances

Now Cassandra Database also installed.

 

At Santriya Technologies, we offer a variety of services to build identity, empower life style for our customers like small, medium and enterprise businesses across the globe. We have a pool of people with expert skills on any various technologies, open source technologies and database systems. We can help your company to overcome business challenges by building custom-made IT solutions.

Do your business need assessment of business process; feel free to contact Santriya Technologies to request free consultation 02087315286…

 

 

 

 

Devops for the .Net Platform

Continuous Integration and Continuous Deployment is simple and easy for small simple single developer projects directly from the Visual Studio IDE. But when it comes to large complex enterprise grade projects that are following an agile methodology Continuous Integration and Continuous Deployment become a complex task by itself.

But why use a Build Server?

Machine independence.

Scripted Builds.

Scripted tests.

Daily and Weekly builds.

Continuous Integration.

Automated releases.

Building in multiple environments.

Static and Dynamic Analysis.

 

This is where a Devops Team / Process comes into play it allows the development / product team  to concentrate on their core skills which is design / code / writing test cases / bug fixes and committing their code to the Source Code Repository and not having to worry about the build / automation testing / deployment.

My personal preference is to use TeamCity as the Build / Deployment Server. It integrates well with the .NET environment, Windows and the Visual Studio IDE. It has a host of plugins that integrate the Build Server with the Windows environment and the Visual Studio IDE. It notifies the developer and the team that is configured to receive updates and alerts on success or failures of the Build Server not only through emails but right in their windows environment or Visual Studio IDE.

TeamCity integrates well with TFS / VSTS and other popular repositories like Git. GitHub, BitBucket, etc.

While this may look like an endorsement for TeamCity over other Build Servers I promise you it is not I have not affiliation to TeamCity. This is totally based on experiences setting up and running devops for .NET projects. The integration is a lot more closely coupled and easier to manage.

The ability to manage Nuget Packages for the project on a whole and have it as a dependency for the whole project. The ability to have separate build tasks for sub projects or components and have them all linked in the order of dependency can be visually managed and made to build in that order. Multiple build agents across multiple VM’s or physical servers and run build tasks concurrently. All the dependencies can be collated and the final build and deployment can be run.

All build errors will trigger alerts to the configured list of users. TeamCity integrates well with Jira so that your agile user stories are integrated into your development and build. It has an inbuilt NUnit test runner. There are many important .NET tools integrated and included with TeamCity, such as code coverage analysis, several .NET testing frameworks, and static code analysis.

At Santriya Technologies, we offer a variety of services to build identity, empower life style for our customers like small, medium and enterprise businesses across the globe. We have a pool of people with expert skills on any various technologies, open source technologies and database systems. We can help your company to overcome business challenges by building custom-made IT solutions.

Do your business need assessment of business process; feel free to contact Santriya Technologies to request free consultation 02087315286…

Everyday we engage in a business process often times without thinking about it. A business process is just the way things are done for example when you buy a cup of coffee: First the cashier asks your order, you then tell them your order, they put that through to the person making the coffee, that person makes the coffee, the coffee gets handed to the cashier, the cashier takes your money and gives you the coffee. No business process is perfect there is always somewhere it can go wrong. A good business process will simply have the least margin for error. From the example given above there is a larger margin for error than there has to be. The way in which I would change it is to have both of the people behind the counter trained to make coffee (we will call them employee a and employee b) employee a will take an order and make the coffee from start to finish seeing that customers order through to the end and during this employee b is doing the same thing for the next customer. you see how when you make this change you reduce the chances of a miss-communication as well as being able to handle twice the amount of customers in the same time frame.

On our CEO’s adventure to Scotland he encountered what we here at Santriya Technologies consider a bad business process. This journey starts on the way to Gatwick airport via rail travel. Rail travel has a reputation for being late, delayed etc. and this journey did very little to challenge these  stereotypes, as the train was delayed in Clapham junction for over an hour. Not only did this induce a case of boredom challenging a great aunts lecture on stamps and how expensive they are these days, but it also meant he was heading late towards a meeting. With the meeting getting nearer and nearer with a sense of urgency he was searching for the right entrance in Gatwick when  British Airways staff member asked if he wanted to check in his baggage. Now his ticket was a hand luggage only ticket (note there was no kind of checklist to see if his ticket met the requirements to check in luggage) and upon checking his baggage without realizing due to the stress of time constraints that he wasn’t eligible for this. This was the first hiccup created by a system with no fail safe for this scenario.

Upon reaching Edinburgh he discovered that his luggage didn’t make it there with him as he wasn’t eligible for check in luggage. The British Airways staff had collected information in order to get the luggage forwarded and British Airways would cover minor expenses due to the inconvenience.

Whilst stopping for a coffee a message from BA read that the baggage could be collected at 9:30 am  although tight this was do-able if he left early. Upon embarking on this quest to reclaim his luggage another text was received saying that the baggage had been collected a week prior and the journey had been a waste as the wrong information was given and the baggage was not there. At his wits end being out of pocket as only minor expenses like toiletries were being covered missing the event he had to cancel his return and take another flight back home. The flight home went a lot smoother than the original flight.

My Conclusion

Given all the occurrences, it would be easy to assume that the fault lies at the people in charge of such duties. And when living through the experience, it’s easy to become frustrated with those representing the company. But the real failure actually lies within the systems being used.

Services need to be adapted with end-user analytics, so any problematic trends can be dealt with sooner rather than later.

There needs to be better customer service as a whole, with more departments talking to each other in order to deliver a truly seamless customer service experience.

A more robust solution needs to be instilled to ensure that verification processes being used are the best they can be.

Considering a few factors could determine as to how a customer feels at the end of their experience, and whether they’re likely to employ the services of that particular brand in the future.

At Santriya Technologies, we offer a variety of services to build identity, empower life style for our customers like small, medium and enterprise businesses across the globe. We have a pool of people with expert skills on any various technologies, open source technologies and database systems. We can help your company to overcome business challenges by building custom-made IT solutions.

Do your business need assessment of business process; feel free to contact Santriya Technologies to request free consultation 02087315286…

Contrary to what common sense may say that staying together is good for all. There are cases where breaking up is good for all. This is one case where it benefits all when the front end and the CMS are decoupled. This is the current rage and is spreading like wild fire.

What it offers is that the front end design is completely free of the CMS and the designers can unshackle them selves and design and build the latest modern looking website and not be constrained by what the CMS has to offer. In Enterprise circles this could also be termed separation of concerns. The CMS does its own job and the right technology and tools for the front end do their own job. Design changes do not affect the CMS and the CMS administrators need not worry about the front end design. Its a win win for all.

This also offers the possibility to build out mobile applications getting their feed directly from the CMS.

 

At Santriya Technologies, we offer a variety of services to build identity, empower life style for our customers like small, medium and enterprise businesses across the globe. We have a pool of people with expert skills on any various technologies, open source technologies and database systems. We can help your company to overcome business challenges by building custom-made IT solutions.

Do your business need assessment of business process; feel free to contact Santriya Technologies to request free consultation 02087315286…