NoSQL




"Structured storage" redirects here. For the Microsoft technology also known as structured storage, see COM Structured Storage.

A NoSQL (originally referring to "non SQL" or "non relational")[1]database provides a mechanism for storage and retrieval of data that is modeled in means other than the tabular relations used in relational databases. Such databases have existed since the late 1960s, but did not obtain the "NoSQL" moniker until a surge of popularity in the early 21st century,[2] triggered by the needs of Web 2.0 companies.[3][4][5] NoSQL databases are increasingly used in big data and real-time web applications.[6] NoSQL systems are also sometimes called "Not only SQL" to emphasize that they may support SQL-like query languages, or sit alongside SQL database in a polyglot persistence architecture.[7][8]


Motivations for this approach include: simplicity of design, simpler "horizontal" scaling to clusters of machines (which is a problem for relational databases),[2] and finer control over availability. The data structures used by NoSQL databases (e.g. key-value, wide column, graph, or document) are different from those used by default in relational databases, making some operations faster in NoSQL. The particular suitability of a given NoSQL database depends on the problem it must solve. Sometimes the data structures used by NoSQL databases are also viewed as "more flexible" than relational database tables.[9]


Many NoSQL stores compromise consistency (in the sense of the CAP theorem) in favor of availability, partition tolerance, and speed. Barriers to the greater adoption of NoSQL stores include the use of low-level query languages (instead of SQL, for instance the lack of ability to perform ad-hoc joins across tables), lack of standardized interfaces, and huge previous investments in existing relational databases.[10] Most NoSQL stores lack true ACID transactions, although a few databases have made them central to their designs.


Instead, most NoSQL databases offer a concept of "eventual consistency" in which database changes are propagated to all nodes "eventually" (typically within milliseconds) so queries for data might not return updated data immediately or might result in reading data that is not accurate, a problem known as stale reads.[11] Additionally, some NoSQL systems may exhibit lost writes and other forms of data loss.[12] Some NoSQL systems provide concepts such as write-ahead logging to avoid data loss.[13] For distributed transaction processing across multiple databases, data consistency is an even bigger challenge that is difficult for both NoSQL and relational databases. Even current relational databases "do not allow referential integrity constraints to span databases."[14] There are few systems that maintain both ACID transactions and X/Open XA standards for distributed transaction processing.




Contents






  • 1 History


  • 2 Types and examples


    • 2.1 Key-value store


    • 2.2 Document store


    • 2.3 Graph


    • 2.4 Object database


    • 2.5 Tabular


    • 2.6 Tuple store


    • 2.7 Triple/quad store (RDF) database


    • 2.8 Hosted


    • 2.9 Multivalue databases


    • 2.10 Multimodel database




  • 3 Performance


  • 4 Handling relational data


    • 4.1 Multiple queries


    • 4.2 Caching, replication and non-normalized data


    • 4.3 Nesting data




  • 5 ACID and join support


  • 6 See also


  • 7 References


  • 8 Further reading


  • 9 External links





History


The term NoSQL was used by Carlo Strozzi in 1998 to name his lightweight Strozzi NoSQL open-source relational database that did not expose the standard Structured Query Language (SQL) interface, but was still relational.[15] His NoSQL RDBMS is distinct from the circa-2009 general concept of NoSQL databases. Strozzi suggests that, because the current NoSQL movement "departs from the relational model altogether, it should therefore have been called more appropriately 'NoREL',[16] referring to 'No Relational'.


Johan Oskarsson, then a developer at Last.fm, reintroduced the term NoSQL in early 2009 when he organized an event to discuss "open source distributed, non relational databases".[17] The name attempted to label the emergence of an increasing number of non-relational, distributed data stores, including open source clones of Google's Bigtable/MapReduce and Amazon's DynamoDB. Most of the early NoSQL systems did not attempt to provide atomicity, consistency, isolation and durability guarantees, contrary to the prevailing practice among relational database systems.[18]



Types and examples


There are various ways to classify NoSQL databases, with different categories and subcategories, some of which overlap. What follows is a basic classification by data model, with examples:




  • Column: Accumulo, Cassandra, Scylla, Apache Druid, HBase, Vertica.


  • Document: Apache CouchDB, ArangoDB, BaseX, Clusterpoint, Couchbase, Cosmos DB, IBM Domino, MarkLogic, MongoDB, OrientDB, Qizx, RethinkDB


  • Key-value: Aerospike, Apache Ignite, ArangoDB, Berkeley DB, Couchbase, Dynamo, FoundationDB, InfinityDB, MemcacheDB, MUMPS, Oracle NoSQL Database, OrientDB, Redis, Riak, SciDB, SDBM/Flat File dbm, ZooKeeper


  • Graph: AllegroGraph, ArangoDB, InfiniteGraph, Apache Giraph, MarkLogic, Neo4J, OrientDB, Virtuoso


A more detailed classification is the following, based on one from Stephen Yen:[19][20]















































Type Notable examples of this type
Key-Value Cache
Apache Ignite, Coherence, eXtreme Scale, Hazelcast, Infinispan, Memcached, Velocity
Key-Value Store
ArangoDB, Aerospike
Key-Value Store (Eventually-Consistent)
Oracle NoSQL Database, Dynamo, Riak, Voldemort
Key-Value Store (Ordered)
FoundationDB, InfinityDB, LMDB, MemcacheDB
Data-Structures Server
Redis
Tuple Store
Apache River, GigaSpaces
Object Database
Objectivity/DB, Perst, ZopeDB
Document Store
ArangoDB, BaseX, Clusterpoint, Couchbase, CouchDB, DocumentDB, IBM Domino, MarkLogic, MongoDB, Qizx, RethinkDB
Wide Column Store
Amazon DynamoDB, Bigtable, Cassandra, Scylla, Apache Druid, HBase, Hypertable
Native Multi-model Database
ArangoDB, Cosmos DB, OrientDB, MarkLogic

Correlation databases are model-independent, and instead of row-based or column-based storage, use value-based storage.



Key-value store


Main article: Key-value database

Key-value (KV) stores use the associative array (also known as a map or dictionary) as their fundamental data model. In this model, data is represented as a collection of key-value pairs, such that each possible key appears at most once in the collection.[21][22]


The key-value model is one of the simplest non-trivial data models, and richer data models are often implemented as an extension of it. The key-value model can be extended to a discretely ordered model that maintains keys in lexicographic order. This extension is computationally powerful, in that it can efficiently retrieve selective key ranges.[23]


Key-value stores can use consistency models ranging from eventual consistency to serializability. Some databases support ordering of keys. There are various hardware implementations, and some users maintain data in memory (RAM), while others employ solid-state drives (SSD) or rotating disks (aka Hard Disk Drive (HDD)).



Document store


Main articles: Document-oriented database and XML database

The central concept of a document store is the notion of a "document". While each document-oriented database implementation differs on the details of this definition, in general, they all assume that documents encapsulate and encode data (or information) in some standard formats or encodings. Encodings in use include XML, YAML, and JSON as well as binary forms like BSON. Documents are addressed in the database via a unique key that represents that document. One of the other defining characteristics of a document-oriented database is that in addition to the key lookup performed by a key-value store, the database also offers an API or query language that retrieves documents based on their contents.


Different implementations offer different ways of organizing and/or grouping documents:



  • Collections

  • Tags

  • Non-visible metadata

  • Directory hierarchies


Compared to relational databases, for example, collections could be considered analogous to tables and documents analogous to records. But they are different: every record in a table has the same sequence of fields, while documents in a collection may have fields that are completely different.



Graph


Main article: Graph database

This kind of database is designed for data whose relations are well represented as a graph consisting of elements interconnected with a finite number of relations between them. The type of data could be social relations, public transport links, road maps, network topologies, etc.


Graph databases and their query language













































































Name Language(s) Notes
AllegroGraph SPARQL
RDF triple store
ArangoDB AQL, JavaScript, GraphQL
 Multi-model DBMS Document, Graph database and Key-value store
DEX/Sparksee
C++, Java, .NET, Python
Graph database
FlockDB Scala
Graph database
IBM DB2 SPARQL
RDF triple store added in DB2 10
InfiniteGraph Java
Graph database
MarkLogic
Java, JavaScript, SPARQL, XQuery
 Multi-model document database and RDF triple store
Neo4j Cypher
Graph database
OpenLink Virtuoso
C++, C#, Java, SPARQL
Middleware and database engine hybrid
Oracle SPARQL 1.1
RDF triple store added in 11g
OrientDB
Java, SQL		 Multi-model document and graph database
OWLIM
Java, SPARQL 1.1
RDF triple store
Profium Sense
Java, SPARQL
RDF triple store
Sqrrl Enterprise Java
Graph database


Object database


Main article: Object database


  • db4o

  • GemStone/S

  • InterSystems Caché

  • JADE

  • ObjectDatabase++

  • ObjectDB

  • Objectivity/DB

  • ObjectStore

  • ODABA

  • Perst

  • OpenLink Virtuoso

  • Versant Object Database

  • ZODB



Tabular



  • Apache Accumulo

  • Bigtable

  • Apache Hbase

  • Hypertable

  • Mnesia

  • OpenLink Virtuoso



Tuple store



  • Apache River

  • GigaSpaces

  • Tarantool


  • TIBCO ActiveSpaces

  • OpenLink Virtuoso



Triple/quad store (RDF) database


Main articles: Triplestore and Named graph


  • AllegroGraph


  • Apache JENA (It is a framework, not a database)

  • MarkLogic

  • Ontotext-OWLIM

  • Oracle NoSQL database

  • Profium Sense

  • Virtuoso Universal Server



Hosted



  • Amazon DynamoDB

  • Amazon SimpleDB

  • Datastore on Google Appengine

  • Clusterpoint database

  • Cloudant Data Layer (CouchDB)

  • Freebase

  • Microsoft Azure Tables

  • Microsoft Azure DocumentDB

  • OpenLink Virtuoso



Multivalue databases



  • D3 Pick database


  • Extensible Storage Engine (ESE/NT)

  • InfinityDB

  • InterSystems Caché

  • jBASE Pick database

  • mvBase Rocket Software

  • mvEnterprise Rocket Software


  • Northgate Information Solutions Reality, the original Pick/MV Database

  • OpenQM

  • Revelation Software's OpenInsight

  • UniData Rocket U2

  • UniVerse Rocket U2



Multimodel database




  • Apache Ignite[24][25]

  • ArangoDB

  • Couchbase

  • FoundationDB

  • MarkLogic

  • OrientDB

  • Cosmos DB



Performance


Ben Scofield rated different categories of NoSQL databases as follows:[26]



















































Data model Performance Scalability Flexibility Complexity Functionality
Key–value store high high high none variable (none)
Column-oriented store high high moderate low minimal
Document-oriented store high variable (high) high low variable (low)
Graph database variable variable high high
graph theory
Relational database variable variable low moderate
relational algebra

Performance and scalability comparisons are sometimes done with the YCSB benchmark.



Handling relational data


Since most NoSQL databases lack ability for joins in queries, the database schema generally needs to be designed differently. There are three main techniques for handling relational data in a NoSQL database. (See table Join and ACID Support for NoSQL databases that support joins.)



Multiple queries


Instead of retrieving all the data with one query, it is common to do several queries to get the desired data. NoSQL queries are often faster than traditional SQL queries so the cost of having to do additional queries may be acceptable. If an excessive number of queries would be necessary, one of the other two approaches is more appropriate.



Caching, replication and non-normalized data


Instead of only storing foreign keys, it is common to store actual foreign values along with the model's data. For example, each blog comment might include the username in addition to a user id, thus providing easy access to the username without requiring another lookup. When a username changes however, this will now need to be changed in many places in the database. Thus this approach works better when reads are much more common than writes.[27]



Nesting data


With document databases like MongoDB it is common to put more data in a smaller number of collections. For example, in a blogging application, one might choose to store comments within the blog post document so that with a single retrieval one gets all the comments. Thus in this approach a single document contains all the data you need for a specific task.



ACID and join support


A database is marked as supporting ACID properties (Atomicity, Consistency, Isolation, Durability) or join operations if the documentation for the database makes that claim. The degree to which the capability is fully supported in a manner similar to most SQL databases or the degree to which it meets the needs of a specific application is left up to the reader to assess.


























































Database ACID Joins
Aerospike Yes No
Apache Ignite Yes Yes
ArangoDB Yes Yes
CouchDB Yes Yes
Db2 Yes Yes
InfinityDB Yes No
LMDB Yes No
MarkLogic Yes Yes[nb 1]
MongoDB Yes Yes
OrientDB Yes Yes[nb 2]




  1. ^ Joins do not necessarily apply to document databases, but MarkLogic can do joins using semantics.[28]


  2. ^ OrientDB can resolve 1:1 joins using links by storing direct links to foreign records.[29]




See also



  • CAP theorem

  • Comparison of object database management systems

  • Comparison of structured storage software

  • Correlation database

  • Distributed cache

  • Faceted search


  • MultiValue database

  • Multi-model database

  • Triplestore

  • Schema-agnostic databases



References





  1. ^ http://nosql-database.org/ "NoSQL DEFINITION: Next Generation Databases mostly addressing some of the points: being non-relational, distributed, open-source and horizontally scalable"


  2. ^ ab Leavitt, Neal (2010). "Will NoSQL Databases Live Up to Their Promise?" (PDF). IEEE Computer..mw-parser-output cite.citation{font-style:inherit}.mw-parser-output .citation q{quotes:"""""""'""'"}.mw-parser-output .citation .cs1-lock-free a{background:url("//upload.wikimedia.org/wikipedia/commons/thumb/6/65/Lock-green.svg/9px-Lock-green.svg.png")no-repeat;background-position:right .1em center}.mw-parser-output .citation .cs1-lock-limited a,.mw-parser-output .citation .cs1-lock-registration a{background:url("//upload.wikimedia.org/wikipedia/commons/thumb/d/d6/Lock-gray-alt-2.svg/9px-Lock-gray-alt-2.svg.png")no-repeat;background-position:right .1em center}.mw-parser-output .citation .cs1-lock-subscription a{background:url("//upload.wikimedia.org/wikipedia/commons/thumb/a/aa/Lock-red-alt-2.svg/9px-Lock-red-alt-2.svg.png")no-repeat;background-position:right .1em center}.mw-parser-output .cs1-subscription,.mw-parser-output .cs1-registration{color:#555}.mw-parser-output .cs1-subscription span,.mw-parser-output .cs1-registration span{border-bottom:1px dotted;cursor:help}.mw-parser-output .cs1-ws-icon a{background:url("//upload.wikimedia.org/wikipedia/commons/thumb/4/4c/Wikisource-logo.svg/12px-Wikisource-logo.svg.png")no-repeat;background-position:right .1em center}.mw-parser-output code.cs1-code{color:inherit;background:inherit;border:inherit;padding:inherit}.mw-parser-output .cs1-hidden-error{display:none;font-size:100%}.mw-parser-output .cs1-visible-error{font-size:100%}.mw-parser-output .cs1-maint{display:none;color:#33aa33;margin-left:0.3em}.mw-parser-output .cs1-subscription,.mw-parser-output .cs1-registration,.mw-parser-output .cs1-format{font-size:95%}.mw-parser-output .cs1-kern-left,.mw-parser-output .cs1-kern-wl-left{padding-left:0.2em}.mw-parser-output .cs1-kern-right,.mw-parser-output .cs1-kern-wl-right{padding-right:0.2em}


  3. ^ Mohan, C. (2013). History Repeats Itself: Sensible and NonsenSQL Aspects of the NoSQL Hoopla (PDF). Proc. 16th Int'l Conf. on Extending Database Technology.


  4. ^ "NOSQL meetup Tickets, Thu, Jun 11, 2009 at 10:00 AM". Eventbrite.com. Retrieved 2017-03-06.


  5. ^ "Amazon Goes Back to the Future With 'NoSQL' Database". WIRED. 2012-01-19. Retrieved 2017-03-06.


  6. ^ "RDBMS dominate the database market, but NoSQL systems are catching up". DB-Engines.com. 21 Nov 2013. Retrieved 24 Nov 2013.


  7. ^ "NoSQL (Not Only SQL)". NoSQL database, also called Not Only SQL


  8. ^ Fowler, Martin. "NosqlDefinition". many advocates of NoSQL say that it does not mean a "no" to SQL, rather it means Not Only SQL


  9. ^ Vogels, Werner (2012-01-18). "Amazon DynamoDB – a Fast and Scalable NoSQL Database Service Designed for Internet Scale Applications". All Things Distributed. Retrieved 2017-03-06.


  10. ^ Grolinger, K.; Higashino, W. A.; Tiwari, A.; Capretz, M. A. M. (2013). "Data management in cloud environments: NoSQL and NewSQL data stores" (PDF). Aira, Springer. Retrieved 8 Jan 2014.


  11. ^ "Jepsen: MongoDB stale reads". Aphyr.com. 2015-04-20. Retrieved 2017-03-06.


  12. ^ "Large volume data analysis on the Typesafe Reactive Platform". Slideshare.net. Retrieved 2017-03-06.


  13. ^ Fowler, Adam. "10 NoSQL Misconceptions". Dummies.com. Retrieved 2017-03-06.


  14. ^ "No! to SQL and No! to NoSQL | So Many Oracle Manuals, So Little Time". Iggyfernandez.wordpress.com. Retrieved 2017-03-06.


  15. ^ Lith, Adam; Mattson, Jakob (2010). "Investigating storage solutions for large data: A comparison of well performing and scalable data storage solutions for real time extraction and batch insertion of data" (PDF). Göteborg: Department of Computer Science and Engineering, Chalmers University of Technology. p. 70. Retrieved 12 May 2011. Carlo Strozzi first used the term NoSQL in 1998 as a name for his open source relational database that did not offer a SQL interface[...]


  16. ^ "NoSQL Relational Database Management System: Home Page". Strozzi.it. 2 October 2007. Retrieved 29 March 2010.


  17. ^ "NoSQL 2009". Blog.sym-link.com. 12 May 2009. Retrieved 29 March 2010.


  18. ^ Chapple, Mike. "The ACID Model".


  19. ^ Yen, Stephen. "NoSQL is a Horseless Carriage" (PDF). NorthScale. Retrieved 2014-06-26.
    [dead link]


  20. ^ Strauch, Christof. "NoSQL Databases" (PDF). pp. 23–24. Retrieved 2017-08-27.


  21. ^ Sandy (14 January 2011). "Key Value stores and the NoSQL movement". http://dba.stackexchange.com/questions/607/what-is-a-key-value-store-database: Stackexchange. Retrieved 1 January 2012. Key-value stores allow the application developer to store schema-less data. This data usually consists of a string that represents the key, and the actual data that is considered the value in the "key-value" relationship. The data itself is usually some kind of primitive of the programming language (a string, an integer, or an array) or an object that is being marshaled by the programming language's bindings to the key-value store. This structure replaces the need for a fixed data model and allows proper formatting.


  22. ^ Seeger, Marc (21 September 2009). "Key-Value Stores: a practical overview" (PDF). http://blog.marc-seeger.de/2009/09/21/key-value-stores-a-practical-overview/: Marc Seeger. Retrieved 1 January 2012. Key-value stores provide a high-performance alternative to relational database systems with respect to storing and accessing data. This paper provides a short overview of some of the currently available key-value stores and their interface to the Ruby programming language.


  23. ^ Katsov, Ilya (1 March 2012). "NoSQL Data Modeling Techniques". Ilya Katsov. Retrieved 8 May 2014.


  24. ^ https://apacheignite.readme.io/docs Ignite Documentation


  25. ^ https://www.infoworld.com/article/3135070/data-center/fire-up-big-data-processing-with-apache-ignite.html fire-up-big-data-processing-with-apache-ignite


  26. ^ Scofield, Ben (2010-01-14). "NoSQL - Death to Relational Databases(?)". Retrieved 2014-06-26.


  27. ^ "Making the Shift from Relational to NoSQL" (PDF). Couchbase.com. Retrieved December 5, 2014.


  28. ^ "Can't do joins with MarkLogic? It's just a matter of Semantics! - General Networks". Gennet.com. Retrieved 2017-03-06.


  29. ^ "SQL Reference · OrientDB Manual". OrientDB.com. Retrieved 2017-04-24.




Further reading




  • Sadalage, Pramod; Fowler, Martin (2012). NoSQL Distilled: A Brief Guide to the Emerging World of Polyglot Persistence. Addison-Wesley. ISBN 0-321-82662-0.


  • McCreary, Dan; Kelly, Ann (2013). Making Sense of NoSQL: A guide for managers and the rest of us. ISBN 9781617291074.


  • Wiese, Lena (2015). Advanced Data Management for SQL, NoSQL, Cloud and Distributed Databases. DeGruyter/Oldenbourg. ISBN 978-3-11-044140-6.


  • Strauch, Christof (2012). "NoSQL Databases" (PDF).


  • Moniruzzaman, A. B.; Hossain, S. A. (2013). "NoSQL Database: New Era of Databases for Big data Analytics - Classification, Characteristics and Comparison". arXiv:1307.0191. Bibcode:2013arXiv1307.0191M.


  • Orend, Kai (2013). "Analysis and Classification of NoSQL Databases and Evaluation of their Ability to Replace an Object-relational Persistence Layer". CiteSeerX 10.1.1.184.483.


  • Krishnan, Ganesh; Kulkarni, Sarang; Dadbhawala, Dharmesh Kirit. "Method and system for versioned sharing, consolidating and reporting information".



External links




  • Strauch, Christoph. "NoSQL whitepaper" (PDF). Stuttgart: Hochschule der Medien.


  • Edlich, Stefan. "NoSQL database List".


  • Neubauer, Peter (2010). "Graph Databases, NOSQL and Neo4j".


  • Bushik, Sergey (2012). "A vendor-independent comparison of NoSQL databases: Cassandra, HBase, MongoDB, Riak". NetworkWorld.


  • Zicari, Roberto V. (2014). "NoSQL Data Stores – Articles, Papers, Presentations". odbms.org.










-

這個網誌中的熱門文章

12.7 cm/40 Type 89 naval gun

圖片
12.7 cm/40 Type 89 naval gun Type 89 gun mounted on Chitose Type Naval gun anti-aircraft gun Place of origin Japan Service history In service 1932–45 Used by Imperial Japanese Navy Wars World War II Production history Designed 1928–32 Produced 1932–45 No.  built ~1500 Variants Type 88 Specifications Mass 3,100 kilograms (6,834 lb) Barrel length 5,080 millimeters (16 ft 8 in) (bore length) Shell Fixed Shell weight 20.9–23.45 kilograms (46.1–51.7 lb) Caliber 12.7-centimeter (5.0 in) Breech horizontal breech block Elevation -8° to +90° [1] Rate of fire 8-14 rounds per minute Muzzle velocity 720–725 meters per second (2,360–2,380 ft/s) Maximum firing range 9,440 meters (30,970 ft) at 90° (AA ceiling) 14,800 meters (48,600 ft) at 45° The 12.7 cm/40 Type 89 naval gun was a Japanese anti-aircraft (AA) gun introduced before World War II. It was the Imperial Japanese Navy's standard heavy AA...
閱讀完整內容

Rikitea

圖片
Town in French Polynesia, France Rikitea Town Rikitea Location in French Polynesia Coordinates: 23°7′13″S 134°58′9″W  /  23.12028°S 134.96917°W  / -23.12028; -134.96917 Coordinates: 23°7′13″S 134°58′9″W  /  23.12028°S 134.96917°W  / -23.12028; -134.96917 Country   France Overseas collectivity   French Polynesia Territory Gambier Islands Island Mangareva Rikitea is a small town on Mangareva, which is part of the Gambier Islands in French Polynesia. A majority of the islanders live in Rikitea. [1] [2] The island was a protectorate of France in 1871 and was annexed in 1881. [3] Contents 1 History 2 Geography 3 Economy 4 Landmarks 5 Transportation 6 References 7 Bibliography 8 External links History The town's history dates to the era when the island was first settled with people from the Marquesas Islands in 1100 AD. Captain James Wilson of the London Missionary Society arrived in 1797 on Du...
閱讀完整內容

University of Vienna

圖片
"Vienna University" redirects here. For Vienna University of Economics and Business, see Vienna University of Economics and Business. University of Vienna Universität Wien Type Public Established 1365 Budget € 544 million [1] Rector Heinz Engl Academic staff 6,765 Administrative staff 3,106 Students 94,000 [2] Postgraduates 16,490 Doctoral students 8,945 Location Main building, Vienna , Austria 48°12′47″N 16°21′35″E  /  48.21306°N 16.35972°E  / 48.21306; 16.35972 Coordinates: 48°12′47″N 16°21′35″E  /  48.21306°N 16.35972°E  / 48.21306; 16.35972 Campus Urban Colors Blue and White           Affiliations Campus Europae, EUA, UNICA Website www.univie.ac.at/en Data as of 2016 [update] The University of Vienna (German: Universität Wien ) is a public university located in Vienna, Austria. It was founded by Duke Rudolph IV in 1365 and is one of the oldest universities in the Ge...
閱讀完整內容