I'm new to the topic of webdesign and servers so maybe I just don't know the keywords to look for but here is my question:
I'd like to create an amazon.com like website. Basically a couple of filters and a huge amount of products. Then I want to use AWS to both store all my products and search for the best product matches for the given filters.
If anyone could direct me to a tutorial or guide or any reference at all I'd be very glad.
PS: I'm really new to all of this so I'd much appreciate a simple explanation!
Depending on your technology choice, there are broadly two ways to host dynamic websites in AWS e.g. Shopping Cart, Marketplace, CRM, CMS solutions:
Using servers i.e. EC2 instances
Serverless using S3, Lambda, DynamoDB, RDS.
Both solutions have advantages and limitations and purely depends on your control over technology.
Related
I am currently developing a full-stack web application for the first time. It is a store that needs to give users the ability to upload "books", edit, delete, and manage them. As of now, I have a React front-end, that calls an Express API using Axios that queries a MySQL database. This currently can manage the product details, titles, and simple labels and relations.
However, I now need to store images and .json files dynamically as well. So, I have researched and need to use Azure Storage to store these images and allow access to them by the end-user. I have researched it and the client would like to use Azure storage as well.
I have gotten quite overwhelmed looking into the Azure documentation for Javascript image uploading, and every "tutorial" starts with create a web application, storage account, and app service.
All I would like to do is store images from the user in Azure storage, so that when I eventually deploy the website, the data is available to be accessed and then my front end or API can call Azure to get the images for the user. I apologize if the question is confusing or vague, I am really just overwhelmed by Azure's documentation and it seems like such a simple and common problem. Any guidance or references would be greatly appreciated.
Yes, it's quite possible. You simply create an Azure Storage account and upload your files as blobs via that account. Then they will be available publicly on the Internet, and your web application can reference them from wherever it is hosted.
It is possible as I believe it is quite a common practice to have a Content Delivery Network to deliver the images. I am not very familiar with Azure but I am with AWS and I can tell you that you can use an AWS S3 bucket to store the images and JSON. It comes with many different configuration options to allow content to be protected or open to the general internet.
I'm developing an intranet for a company under MEAN.js. I was wondering if there's a way to use MySQL along with MEAN.js and keep using MongoDB. Primarily I'll use mongo for heavy data, such as pdf's, videos, music, etc. I'll use MySQL for structured data such as users, profiles, statistics info, etc.
The main question is how to do it, and also would like some advices.
Searching i've found this example but it supplants MongoDB for MySQL, and i want to use both.
At first, this question appeared to be too trivial to me to actually require a Stackoverflow post. However, after executing many Google searches for the information, I am at a lost when trying to figure this out about Couchbase.
In Couchbase (I am using the 2.2 Community version), how do I share views among developers? Is there some sort if import/export functionality available? If not, then how does Couchbase intend for developers to share the views that they are using without needing to do manual copying/pasting? It is obvious that the code that a development team would write for querying Couchbase will require accurate view names. Without having a way to send a developer a view file, to accurately setup a Couchbase DB, how can it even be possible to develop with Couchbase locally as a team?
I'm sorry if I sound a little desperate or harsh here, but if it isn't possible to share views among multiple developers, then I don't see how Couchbase can be a viable DB solution for a team of developers trying to share database configuration, similar to how a team using an SQL DB would share schema files to set up the DB.
Several ways you can approach this:
1) Create views programmatically as demonstrated here in java:
http://tugdualgrall.blogspot.com.es/2012/12/couchbase-101-create-views-mapreduce.html
or here in node.js:
http://www.tuicool.com/articles/RvYbQn
2) Store all your views in your version control system (This is the option I use). If you are developing locally then only you need your personal view code, once they are working and your tests are all passing then you can check them in.
I assume you'd then be developing on an testing environment so yes sadly here you'd have to update the views either by hand or by using option 1.
You could also take a look at perhaps using this tool but only for views: http://www.couchbase.com/communities/q-and-a/how-bulk-import-design-docs-and-views-couchbase-server
This functionality currently is not available in the admin UI.
There is a defect/enhancement open Ability to import/export views MB-8436. You can leave there your feedback and vote for it so it will be included in the next release.
In the meantime you can use Design Document REST API
Also there is a workaround blog
One of my sites is a social networking site running on MySQL. I use postal code and country information to geolocate users using a webservice. This webservice also allows you to download all their many tables of information so that you can access it locally. My site has gotten big enough that I wish to do this now.
My question is, should I create a new database on my site for all of this postal code and country information and all its tables, or should I incorporate those tables into my existing database for my social networking site?
What are the pros/cons either way?
When you're talking about scaling and want to know about other databases like NOSQL, you might find this article interesting: http://highscalability.com/blog/2010/12/6/what-the-heck-are-you-actually-using-nosql-for.html
I'd vote in favor of a separate database if you planned to use the data as read-only and put a web service in front of it to access it. Users would search it based on a small handful of parameters (e.g. address info to get lat/lon data).
I'd say put it in the existing database if you planned to JOIN it with other information in your current schema.
it will live on the same disk probably.
so disk space is not an issue.
if you query the tables in a completely separate manner, then no impact on the existing site.
if you query things together, then easier when all in one database.
overall administration of one database vs 2 is easier.
i think it's a no brainer... they go in one db.
How does a good e-commerce search work?
I don't have hard coded categories and sub-categories to start with. People are not forced to categorize them.
Tag based system will mean creation of manual tags by people. I mean for a deal of Apple Macbook it has to be classified as a laptop. So, a simple text tag based system doesnot work.Does it?
Can we possibly customize Sphinx to work? If yes, How?
Is it a possibility to create a tag tree based system where a subtree can be classified as a category or Subtree?
Usually it's the job of the merchant to classify his products in different sections. The way you could store tags in tightly related to the tool you are using to display / store them you are not going to manage it the same way if your are using a CMS like Drupal or if you are creating an application from scratch.
What you could do is categorize yourself the products and add the tags as an additional classification tool. Tags are not really reliables.
Sphinx and Apache Solr are customizable, again it depends on the tool that you are using but it's common to tweak the storage of the items that you are indexing.