scalability - Database security / scaling question -

-

Usually I use a database like MySQL or PostGreSQL on the same machine because the application using it, which makes it easy to access And becomes safer. I'm just building the first site in which there will be a separate physical database server (later this year). I am thinking of 3 things:

  1. (Security) What should I consider for security related initiatives to access a different machine database?
  2. (scalability) Should they consider scalability issues related to their (technology Ahnostic)?
  3. (More ServerFault ish but related) If DB is started on the same physical server (using separate VMVero VM) and later on going to a different physical server Are there unequivocal problems that I have to deal with? localhost ? Still, another VMM has not been used through

if these questions are completely ridiculous, then I apologize to you DB experts.

Easy, I'll provide you safe .. well, security with the physical location of the database server There is a lot to do.

However to get your three questions:

  1. First of all, see how you can limit access to database tables using the database server security model . That is, if your application is not required to drop a table, make sure that the user is not used to connect to it, the second does not have the ability to encrypt the connection between the database server and your application. See. Through Kerbero in windows it is very transparent and can also be implemented by group policy settings, is not certain about other platforms. Third, what are the databases in the database to encrypt the data, "in the comfort", what It basically supports the encryption of real data files?

The issue here is that your application has only one entry point on the database server. Ask yourself, what if someone could connect directly without leaving their app using your application credentials? Next, ask if they can get SQL injection issues. Also, ask yourself, if any one is able to keep track of your IP traffic going between your app and server, what information should be taken? May be. Can they see any data? Finally, ask yourself, what if they found a copy of the database?

The length you go to # 1 is going to depend on many factors such as how valuable the data is (example: what would happen to you, your company, or your customers if it was lost); And, how much time do you have to come up with an ideal solution?

  1. Scalability: This is the work of pure load. Unfortunately, the only way to measure most database applications is to scale. Which means that you can get a large database server, as needed. The heap overflow went through this very long ago. Some database types (nosql, mongodb, etc.) support a concept called shredding or comb creator, not MySQL, PostGreSql, etc. Instead you have to design the app specifically to handle it. It means that not using things like rising keys of auto, etc. It can be a royal pitcher ... That's why scaling up is a very easy possibility depending on your application.

  2. Another VM is not available through "localhost" The localhost defines access to your current server whether or not the server is a VM, it is useless. You must refer to your database server by name. Now, when moving the database from another physical server to VM, it should have zero effect because it is referencing it by name. There is no other idea than this.


Comments

Post a Comment

Popular posts from this blog

windows - Heroku throws SQLITE3 Read only exception -

-
After I deploy the app to Heroku, I have to run migration scripts and get this error message ... ITES \ padrino \ prophetmargin & gt; Heroku Rack AR: Rack mutated! SQLite3 :: ReadOnlyException: only one try to write database to read: CREATE TABLE "schema_migrations" ( "version" varchar (255) NOT NULL) /disk1/home/slugs/215264_925fd2c_65a3/mnt/.bundle/gems/gems/ padrino-core- is 0.9.11 / lib / padrino-core / cli / rake.rb: 9: in `init ' how can this be? I also tried to run Heroku dbpush SQLite: //db/my-db.db and that did not work Horoku sqlite3 but using postgres does not do. I'm not sure why you are receiving this error, however, as I have used sqlite3 in development and when pushing it into its travel, they do some magic which migrates to postgrads. I'm absolutely sure how Heroku does 'backwash' this database but it seems that this is happening to you because it's the SQLite db file which is obviously due to Heroku's
Read more

lex - Building a lexical Analyzer in Java -

-
I am currently learning lexical analysis in compiler design. To know how a lexical analyzer actually works, I am trying to build myself. I am planning to make it in Java The input to the lexical analyzer is a .tex file that is of the following format. \ section {script} {intro} \ section {Scope} arbitrary text \ section {relevance} uncontrolled text \ subdivision (profit) arbitrary text \ subsubsection {in real life} \ subdivision {Ingredient} \ end {document} The output of the lecture may be a table of contents with a page number in another file. 1 Introduction 1 1.1 Scope 1 1.2 Relevance 2 1.2.1 Benefits 2 1.2.1.1 Real life 2 1.2.2 loss 3 I hope that This problem is within the scope of Language Analysis Read the .exe file and check '\' and continue to check whether it is actually on search In the sectioning command is set to indicate whether or not a flag variable is the type of sectioning. I hope the above approach will work for the construction of Lexa
Read more

python - rename keys in a dictionary -

-
I want to change the names of keys in a dictionary which are ints, and I need them so that the inputs with key zero They can sort correctly. For example, my keys are like this: '1', '101', '11' and I may need them: '001', '101', '011' What is doing, but I know that there is a better way tmpDict = {} in the ADC for the old: t MpDict ['% 04d'% int (olden)] = addict [oldkey] New controlled = tmpDict You are going wrong about this if you want to draw entries on a line in a specific way, then you have to sort on the extraction. for sorted (D, key = int): print '% s:% R'% (k, d [k]) < / Div>
Read more