10-step program to SOA success
Across all of these situations, and there have been many, I have noted a consistent set of themes which I have rolled up into what I will call the 10-step program to SOA success.
Short an precise.
Tag: soa
RubyForge: Starling: Project Info
Starling is a light-weight persistent queue server that speaks the MemCache protocol. It was built to drive Twitter’s backend, and is in production across Twitter’s cluster.
zeromq: Fastest. Messaging. Ever.
Our mission with ØMQ (“ZeroMQ”) is to build the fastest messaging ever. The way to get performance is to optimise the whole software and hardware stack together. So, we are developing ØMQ closely with major hardware firms.
MogileFS is a open source distributed filesystem. Its properties and features include:
* No single point of failure – storage nodes, trackers, and the tracker’s databases can be run on multiple machines. A minimum of 2 machines is recommended.
* Automatic file replication – files are automatically replicated between several different storage nodes.
* Flat Namespace – Files are identified by named keys in a flat, global namespace. You can create as many namespaces as you’d like, so multiple applications with potentially conflicting keys can run on the same MogileFS installation.
* Shared-Nothing — MogileFS doesn’t depend on a pricey SAN with shared disks. Every machine maintains its own local disks.
This little beauty is an open source distributed filesystem from the author of the excellent memcached.
It features functionalities available only in very expensive commercial grids.
You can build something the size of Flickr with this.
Google AppEngine – A First Look
Everything that could have tied you to a machine is tossed. No disk access, no threads, no sockets, no root, no system calls, no nothing but service based access. Services are king because they are easily made scalable by load balancing and other tricks of the trade that are easily turned behind the scenes, without any application awareness or involvement.
Software Architecture Document Guidelines – Coding the Architecture
Regardless of the development process that you use, a description of the software architecture can be essential for any project, big or small. If software architecture is about the structure of a system and is the vehicle for satisfying the requirements, then the software architecture document is a written description of this.
In this article, I will try to address 10 of the most common doubts people have about REST when they start exploring it, especially if they have a strong background in the architectural approach behind SOAP/WSDL-based Web services.
Two data streams for a happy website
One of the most important architectural decisions that must be done early on in a scalable web site project is splitting the data flow into two streams: one that is user specific and one that is generic. If this is done properly, the system will be able to grow easily.
Memcachedb is a distributed storage system designed for persistent. We simplely hacked from memcached and tugela. But neither of them. Memcachedb is not a cache solution, it is a persistent solution for high-frequency writing and reading. It conforms to memcache protocol(not completed, see below), so any memcached client can have connectivity with it. Memcachedb uses Berkeley DB as a storing backend, so lots of features including transaction and replication are supported
Might be potentially useful when it comes to age
Project SAM – Simple Asynchronous Messaging
Many enterprises rely on asynchronous messaging and queuing infrastructures to connect the various pieces of their business systems. Currently connecting PHP scripts to this infrastructure is not simple or convenient.
The aim of the SAM extension is to open up the messaging infrastructure to the PHP scripting environment by providing an API that allows the most common and simple messaging operations to be accomplished with the minimum of fuss.
MySQL Multi-Master Replication
A good, illustrated step by step how-to on MySQL multi-master replication with two circular masters and some satellite read only slaves
Implementing Tag Cloud – The Nasty Way (Part 2)
Very interesting architecture for dealing with huge tagclouds.
Defining SOA as an architectural style
Discover how to define SOA as an architectural style to promote business-aligned enterprise services as the fundamental unit for designing and building solutions. Learn why it\’s important to align services with your business model, and then explore a pattern language that can be used to implement this architectural style.
To help develop a shared language and collective body of knowledge about SOA, a group of SOA practitioners created this SOA Practitioners’ Guide series of documents. In it, these SOA experts describe and document best practices and key learnings relating to SOA, to help other companies address the challenges of SOA. The SOA Practitioners’ Guide is envisioned as a multi-part collection of publications that can act as a standard reference encyclopedia for all SOA stakeholders.
As large MediaWiki deployments may gain performance using Memcached, at some level cost of RAM to store all objects becomes too high. In order to balance resource usage and make more use of our Apache server disks, Tugela, the distributed cached on-disk hash database, has arrived.
A file based, drop-in replacement for memcached
WSO2 Web Services Framework/PHP | WSO2 Oxygen Tank
WSO2 Web Services Framework/PHP (WSO2 WSF/PHP), a binding of WSO2 WSF/C into PHP is a PHP extension based on Apache Axis2/C for providing and consuming Web Services in PHP.
WSO2 WSF/PHP supports both SOAP 1.2 and SOAP 1.1, WS-Security UsernameToken, REST style invocation and WS-* stack specifications: SOAP MTOM, WS-Addressing version 1.0 and submission.
Available as an external extension, WSO2 WSF/PHP is released under Apache License, Version 2.0
In order to communicate over networks we need standardized data formats and protocols. But how do we move forward toward this goal? One popular debate centers around the best way to define new data formats. XML dominates this area and so the primary question left is how and whether to use schemas and if so, what schema language to use. This paper will address a different question: How will we standardize the protocols used to transport the XML documents? This paper will describe three different strategies and attempt to summarize their strengths and weaknesses from the point of view of a partisan.
Getting RDF data on the web can be hard to convince people to do, or to do correctly (see RSS). This service helps convert formats as need be and lets you access embedded RDF via GRDDL (such as microformats when they have a transformation) without the need to pre-process it yourself.
Everything that Triplr generates is available via a simple GET at a URI, so you can cut and paste them, ‘wget’ or ‘curl’ them and thus easily get the data into into your own web application without additional code.
PragDave: The RADAR Architecture: RESTful Application, Dumb-Ass Recipient
Put the main application logic into a RESTful server. This is where all the CRUD-style access to resources takes place.
Then, write a second proxy server. This is an HTTP filter, sitting between dumb browsers and your core resources. When browser-based users need to interact with your resources, they actually connect to this proxy. It then talks REST to your main server, and interprets the RESTful responses back into a form that’s useful on the browser. And this filter doesn’t have to be a dumb presentation layer—there’s nothing to say that it can’t handle additional functionality as well. Things like menus, user preferences, and so on could all sit here.
Advanced MySQL Replication Techniques
There are some cases where the MySQL Cluster is the perfect solution, but for the vast majority, replication is still the best choice.
Replication, too, has its problems, though:
* There is a fastidious distinction between master and slaves. Your applications must be replication-aware, so that they will write on the master and read from the slaves. It would be so nice to have a replication array where you could use all the nodes in the same way, and every node could be at the same time master and slave.
* There is the fail-over problem. When the master fails, it’s true that you have the slaves ready to replace it, but the process of detecting the failure and acting upon it requires the administrator’s intervention.Fixing these two misfeatures is exactly the purpose of this article. Using features introduced in MySQL 5.0 and 5.1, it is possible to build a replication system where all nodes act as master and slave at the same time, with a built-in fail-over mechanism.
Load More