Cloud Foundry: Design and Architecture
Derek Collison discusses the goals, the design premises and patterns employed in creating the architecture of Cloud Foundry, VMware’s open source PaaS, unveiling internal architectural details.
The content has been bookmarked!
There was an error bookmarking this content! Please retry.
Posted by Jenni Konrad on Aug 04, 2011
Microsoft has released Visual Studio LightSwitch 2011, a simplified development tool intended to speed up the creation of custom business applications. It includes pre-built components, templates, and predefined data types for the most common business needs, and allows developers to produce form-driven applications for either desktop use or deployment to the cloud.
As Jason Zander explains,
...it starts with the premise that most business applications consist of data and the screens that users interact with. LightSwitch simplifies attaching to data with data source wizards or creating data tables with table designers. It also includes screen templates for common tasks so you can create clean interfaces for your applications without being a designer. Basic applications can be written without a line of code.
LightSwitch attempts to speed up development by making architecture choices for the developer, leaving them to focus on the business logic. It includes several starter kits to help create some of the most common business applications, such as:
These starter kits can be downloaded and used as templates for development in either C# or Visual Basic. LightSwitch also supports the use of third-party extensions that can be integrated into a business application for functionality like interactive reporting, document viewing, and rich editing. In addition, there are extensions for a variety of data providers including Google, QuickBooks, Facebook, Twitter, Salesforce, and SharePoint.
A typical three-tier LightSwitch application will involve the following:
The logic tier can be hosted locally, on Windows Azure, or on IIS. Deployment to the desktop or a hosted environment is a matter of selecting that option, rather than changing architecture. Because LightSwitch uses the same kind of project templates, it also integrates with Visual Studio Professional, Premium, and Ultimate (though LightSwitch must be installed in order to work with its projects within Visual Studio).
Visual Studio LightSwitch 2011 retails at $299; a free 90-day trial is available from Microsoft.
Troubleshoot Java/.NET performance while getting full visibility in production
Visual Studio vNext: ALM features for Agile Planning, Team Collaboration
Adopting Git for the Enterprise: Risks and Considerations
Branching & Merging Efficiently: A Guide to Using Process-Based Promotional Patterns
In today’s hyper-competitive world, later may be too late to adopt Agile development and this Roadmap for Success will help you get started. Download "Agile Development: A Manager's Roadmap for Success" now!
Derek Collison discusses the goals, the design premises and patterns employed in creating the architecture of Cloud Foundry, VMware’s open source PaaS, unveiling internal architectural details.
Andrew Watson talks about the work of the OMG, where CORBA is alive and well (hint: in your car), UML and UML Profiles vs. custom Modeling languages, DDS and other middleware, and much more.
Sohil Shah discusses creating iPhone and Android enterprise mobile applications based on cloud services using the open source platform OpenMobster.
Paul Sanford presents the transformations supported by data throughout its life cycle, and how that can be better done with Splunk, an engine for monitoring and analyzing machine-generated data.
A common “best practice” for unit tests is to only write a one assertion in each test. I intend to question this advice by showing that multiple assertions per test are both necessary and beneficial.
John Rauser presents the architectural and technological evolution of Amazon retail websites starting with 1994 and ending with adopting Amazon Web Services.
Michael Stal discusses system architecture quality, how to avoid architectural erosion, how to deal with refactoring, and design principles for architecture evolution.
Every developer has had to integrate with another system, API or component. Tis article provides strategies to handle the change and for he separating system boundaries.
No comments
Watch Thread Reply